Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Support for Sample.sequencing_center #2

Open
torstees opened this issue Sep 16, 2020 · 3 comments
Open

Add Support for Sample.sequencing_center #2

torstees opened this issue Sep 16, 2020 · 3 comments

Comments

@torstees
Copy link
Collaborator

A sequencing center represents the group that performs the actual sequencing. This is not specific to a ResearchStudy, since the same center may be used by many studies and I imagine it is possible that a single study may have sequences that were generated at different centers.

@torstees
Copy link
Collaborator Author

If we use the KF approach where a Task represents the concept of genotyping, where input represents the platform and sample level information and output are the final products at an aggregate level (as opposed to individual genes or variants), they are using Task.owner to reference the organization.

@torstees
Copy link
Collaborator Author

torstees commented Sep 16, 2020

Example from Kristin's example data, FD:

  {
    "host": "http://localhost:8000",
    "type": "sequencing_center",
    "body": {
      "resourceType": "Organization",
      "id": "FD",
      "meta": {
        "profile": [
          "http://hl7.org/fhir/StructureDefinition/Organization"
        ]
      },
      "identifier": [
        {
          "system": "urn:ncpi:unique-string",
          "value": "Organization|FD"
        }
      ],
      "name": "FD",
      "active": "true"
    }
  },

@RobertJCarroll
Copy link

The Task.owner or DiagnosticReport.performer would work I expect. Setting up an organization feels right either way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants