Attendees
Michael Savage
Igor Sirkovich
Sheridan Cook
Lloyd McKenzie
Paul Knapp
Russ Buchanan
Abdullah Khan
Harsh Sharma
Kunj Joshi
Shamhad Abdi
Maria Hu
Discussion
• Group discussed the way(s) ‘Must Support’ needs to be defined in the Canadian Core; need to have clear expectations
• Sheridan walked the group through her chart which proposes 4 main configurations, each of which deal with 2 scenarios: Query & Create/Update
• Client = requester, server = responder
• Good amount of back and forth re: sending a data element with no value (as opposed to just not using that element at all)
• Some reviewers feel it would be odd to have a 1..1 cardinality and not also have a must support flag
• Topic raised of eliminating the data absent reason extension; relevant discussion are being had in other groups like HL7 Conformance Group, will want to ensure the efforts between these groups are consistent
• Hoping the approach of not using ‘data absent reason’ sees international adoption
• Should add some wording on dealing with modifier elements when an element is must support + 1..1, i.e. does the requester have to consume a modifier element no matter what because it fundamentally impacts the interpretation of the information coming back
• The focus of the must support flag in the query scenario is really the server; we shouldn’t set expectations on that the receiving client had to do with the data it receives
• Current Version of the Must Support Definitions, configurations, and scenarios can be found here:
infocentral.infoway-inforoute.ca/en/resources/docs/hl7/canadian-core-profiles