Brian Postlethwaite (Telstra Health) (chair for today)
Charles Ye (FastRiver)
Elkhan Yusubov (NewWave)
Irma Jongeneel (HL7 Netherlands)
Iryna Roy (Gevity)
Ulrike Merrick (APHL)
John Moehrke (Bi Light)
Alex de Leon (Kaiser Permanete)
Line Saele (HL7 Norway)
Key Upcoming Dates:
- Christmas & New Year!
- 2020-02: HL7 WGM Sydney!
- Da Vinci Notifications IG review
- FHIR Merge Operation - v2 mapping
- Continue drafting the Merge operation definition - walking through the Questions and Answers section
- Encounter breakdown review - attachment on this page Encounter, Condition, Procedure, Diagnosis ... (if time permits)
- Action Items
Reviewed the Da Vinci Unsolicited Notifications Implementation Guide (formerly called Alerts)
Security is in scope, but defined in an external guide.
Although the delivery and endpoint discovery/maintenance is out of scope, the details of who to deliver to is included.
Use of GraphDefinition and MessageDefinition are both used to describe use cases
Notification event valueset has the episode type in the notification types as a child type, this might be collapsed into the episode, should review during ballot.
Binding to the Notification valueset will need to be corrected, its an extensible binding, however fixes the code system.
Riki Moves to accept IG to go to the Feb 2020 Ballot, Alex seconds, motion passes 7-0-0
Continue discussing the Merge Operation documented here: Merge Operation
We need to consult with the community to determine if the v2 messages A41 (account) and A42 (encounter) are in use, and if we should be considering creating FHIR equivalents
And also A43, A44 and A45 or move should also be considered to see if they are in active use.
https://www.youtube.com/watch?v=8BOGePClMrE&t=0s (Grahame's FHIR Dev Days presentation)
FHIR Trackers (in Jira!)