Faites-nous part de vos impressions sur le Serveur terminologique, et aidez-nous à améliorer nos services! Vous avez jusqu’au 3 décembre 2024 pour répondre au sondage. Votre avis nous intéresse!
En savoir plus >
Another big thank-you to Sheridan for the detailed notes for the meeting!
Attendees
Sheridan Cook
Michael Savage
Rita Pyle
Alex Goel
Anne Belford
Igor Sirkovich
Joanie Harper
Kenneth Sinn
Randy Nonay
Shamil Nizamov
Thomas Zhou
StatusReason - MS in baseline but not in IPS - flag as one for potential relaxation but needs more input on if this is something that we expect across 80% of Canadian IGuides/Implementations
occuranceDateTime - bring String back as data type as other types of use cases (citizen access, entry, etc.) may not be constrained to only use dateTime
• May be appropriate constraint for a registry focused profile
• Keep MS flag on DateTime
• Evaluate how CanImmunize, ICON, others are using dateTime exclusively
Question: IPS supports a Data Absent Reason profile for occuranceDateTime to allow for a value to be missing when the base spec requires one be present.
• Are we missing out on anything by not having a means to not provide occurrence - data-absent-reason
primarySource - candidate for relaxation need to consider how/if it's being used by other Iguides/Implementations
- CanImmunize or ICON to see if supported item- MS / Cardinality
reportOrigin - fate is tied to primary source
Next DDR session - will continue where we left of with this review of Immunization (CA Baseline and IPS)
For the Friday Nov 20th agenda, we will begin with a review of updates from the Clinical Profiles stream, and then continue with the Due Diligence Review which is comparing the CA Baseline's Immunization Profile to its equivalent Immunization profile as defined in the International Patient Summary (IPS) FHIR iGuide.