This wiki has undergone a migration to Confluence found Here
Difference between revisions of "201809 Clinical Genomics"
Jump to navigation
Jump to search
| Line 23: | Line 23: | ||
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 22:31, 25 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
Roles
Scenarios
- Precondition: -
- Success Criteria: -
- Bonus point: -
