Difference between revisions of "201809 Clinical Genomics"
| Line 22: | Line 22: | ||
==Justification== | ==Justification== | ||
| − | After getting Feedback from the first ballot of the Clinical Genomics Implementation Guide in the May 2018 ballot cycle the balloted IG and profiles should be tested in the Connectathon to get feedback from implementers using it. | + | After getting Feedback from the first ballot of the Clinical Genomics Implementation Guide in the May 2018 ballot cycle, the balloted IG and profiles should be tested in the Connectathon to get feedback from implementers using it. |
<!--Why is this an important track to include in the connectathon - include implementer need, impact on ballot, FMM readiness of the resources, etc. --> | <!--Why is this an important track to include in the connectathon - include implementer need, impact on ballot, FMM readiness of the resources, etc. --> | ||
Revision as of 08:34, 26 June 2018
Return to September 2018 Proposals
Contents
Clinical Genomics Track
This track will focus on exchanging Genetic Diagnostic Reports in FHIR R4 as described in the Clinical Genomics Reporting IG
For this track, we will be using the balloted STU4 version of FHIR.
Orientation
Clinical Genomics Reporting IG
Zulip Chat
The Zulip Chat will be used to coordinate among participants during the connectathon:
Submitting WG/Project/Implementer Group
Justification
After getting Feedback from the first ballot of the Clinical Genomics Implementation Guide in the May 2018 ballot cycle, the balloted IG and profiles should be tested in the Connectathon to get feedback from implementers using it.
Proposed Track Lead
Patrick Werner (patrick.werner@molit.eu)
See Connectathon_Track_Lead_Responsibilities
Expected participants
- Kevin P
- Bob M
- Alex M
- Joseph K (?)
- Paul Lynch (NLM)
- Ye Wang (NLM)
- Amnon Shabo (Shvo)
- Dora Finkeisen (?)
- Patrick Werner (Molit Institut)
- Joel Schneider
Roles
- Genomic Diagnostic Report producer (Lab)
- Genomic Diagnostic Report consumer(Hospital)
Scenarios
Exchange of Genetic Diagnostic Report (GDR) as single resources
A Genetic Diagnostic Report is exchanged via a persisting FHIR Server. The Creator of the GDR POSTs all the needed resources and hands over the ID of the GDR to the Consumer.
The Consumer queries all needed resources for the complete report starting with the ID of the GDR.
- Success Criteria: All resources were transferred correctly.
- Bonus point: Visual Representation of the GDR
Exchange of Genetic Diagnostic Report (GDR) as a document
A Genetic Diagnostic Report document is exchanged via a persisting FHIR Server. The Creator of the GDR POSTs a document bundle and hands over the ID of the document bundle to the Consumer.
The Consumer GETs the document and splits it up into separate resources.
- Success Criteria: All resources were extracted from the document correctly.
- Bonus point: POSTing single resources and creating the document bundle on-the-fly using the $document operation.
