- Forum
- Working Groups
- FHIR® Implementations
- Canadian FHIR Baseline Profiles - Profiling Stream Meeting - August 16th, 2-3pm EST
Canadian FHIR Baseline Profiles - Profiling Stream Meeting - August 16th, 2-3pm EST
- Michael Savage
- Topic Author
- Away
- Posts: 453
5 years 3 months ago #5219
by Michael Savage
Replied by Michael Savage on topic Canadian FHIR Baseline Profiles - Profiling Stream Meeting - August 16th, 2-3pm EST
Hi all,
Please see below for minutes from last Friday the 16th's Profiling Meeting. A big thank-you to Russ for chairing the call and to Ken for the fantastic documentation!
Attendees
Ken Sinn
Russ Buchanan
Philip Alcaidinho (meditech)
Smita Kachroo (infoway)
Jorge Pichardo / 1-250-519-7700 (IslandHealth/BC)
Scott Prior (BC)
Andrea MacLean
Shamil Nizamov
Harsh Sharma
Ramon Dhanoa
1-778-890-2100
Reviewed timelines.
Discussed the following issues on GitHub:
Issue #9
• Modeling changes relaxed Address.state binding from required to extensible, and changing binding from PostalCode to Postal+State for Patient address. Ken's feedback that the binding should be to a pan-Canadian URI not eHeatlh Ontario; Andrea suggests looking at ISO (Ken: also Canada Post + USPS)
• Action: Research and update binding in Patient profile
• Can this be applied to Practitioner/Organization/Location? No objections, so change/update will be expanded to all three resources.
• Action: Update all 4 profiles with change and close issue.
Issue #10
• Modelling changes to Address.postalcode
• Smita: Any guidance to the format of the Postal Code? Space/No-Space, case of letters?
• May have been looked at via Ontario (Ken) and PrescribeIT (Smita) and Access2022 (Smita/Joel)
• Action: Infoway and Jurisdictions to research whether formatting requirements are specified in other profiles and respond to this issue with examples.
Issue #8
• Address extensions
• Looking for additional feedback from jurisdictions, implementers.
• Intention is to allow discrete processing of these fields, as opposed to leaving them in address lines.
• Action: Meditech and Jurisdictions are asked to research and respond to the issue on GitHub. github.com/scratch-fhir-profiles/CA-Core/issues/10
Issue #53
• Location.identifier cardinality
• Harsh - Alberta, with local physicians, difficult to track. Logical approach and agree w/ proposal. Situations where private practitioners, clinics may have unique identifier, and may have multiple doctors at a Location.
• Smita - Agreement, w example of Shoppers Drug Mart w/ Organization. Should go with 0..* and no MustSupport. Can reassess in future if there are new use-cases or requirements
• Agreement to loosen constraint.
• Action: Update profile Location.identitifier cardinality 0.. , remove MustSupport
Issue #50
• Practitioner.identifier slicing …
• Initial plan was slice on Patient (particularly for Juridictional health numbers), and then apply similar to logic to practitioner/organization/location.
• Scott: each province approaches differently. Alberta - provider number is the billing number, which is diff from the licence number. These would be meaningful distinctions in jurisdictions.
• Russ: no significant difference in how slicing would impact the implementions -- doesn't add anything.
• Jorge: BC, identified via billing number. Also have college ID, part of college of physicians.
• Harsh - Should be a guiding document from federal level?
• Smita - Some of the billing and licence may be captured under Practitioner vs PractitionerRole, and may need use-case specific determination.
• Action: Update profile, remove slicing from Patient.identifier
• Also applies to Issue #52 (Location) and Issue #58 (Organization)
• Action: Update profiles, remove slicing from Organization.identifier , Location.identifier
Final remarks:
• Ken: Number of resources for review are challenging time-wise/schedule-wise. May need to slow down pace some.
• Action: Russ to pass feedback along to Mike.
• Smita: What is status of the Patient resource review, as well as the related Terminology content? Are they finalized for the Patient resource?
• Action: Russ to pass along suggestion to add this to discussion at next meeting.
• Smita: Where will guide and guidance be published.
• Russ: Profiles are currently generating to simplifier and build.fhir.org. Narrative only going to latter … this is a config item in simplifier that needs to set and tested.
• Action: Russ to pass along suggestion to include this in the topic above.
Please see below for minutes from last Friday the 16th's Profiling Meeting. A big thank-you to Russ for chairing the call and to Ken for the fantastic documentation!
Attendees
Ken Sinn
Russ Buchanan
Philip Alcaidinho (meditech)
Smita Kachroo (infoway)
Jorge Pichardo / 1-250-519-7700 (IslandHealth/BC)
Scott Prior (BC)
Andrea MacLean
Shamil Nizamov
Harsh Sharma
Ramon Dhanoa
1-778-890-2100
Reviewed timelines.
Discussed the following issues on GitHub:
Issue #9
• Modeling changes relaxed Address.state binding from required to extensible, and changing binding from PostalCode to Postal+State for Patient address. Ken's feedback that the binding should be to a pan-Canadian URI not eHeatlh Ontario; Andrea suggests looking at ISO (Ken: also Canada Post + USPS)
• Action: Research and update binding in Patient profile
• Can this be applied to Practitioner/Organization/Location? No objections, so change/update will be expanded to all three resources.
• Action: Update all 4 profiles with change and close issue.
Issue #10
• Modelling changes to Address.postalcode
• Smita: Any guidance to the format of the Postal Code? Space/No-Space, case of letters?
• May have been looked at via Ontario (Ken) and PrescribeIT (Smita) and Access2022 (Smita/Joel)
• Action: Infoway and Jurisdictions to research whether formatting requirements are specified in other profiles and respond to this issue with examples.
Issue #8
• Address extensions
• Looking for additional feedback from jurisdictions, implementers.
• Intention is to allow discrete processing of these fields, as opposed to leaving them in address lines.
• Action: Meditech and Jurisdictions are asked to research and respond to the issue on GitHub. github.com/scratch-fhir-profiles/CA-Core/issues/10
Issue #53
• Location.identifier cardinality
• Harsh - Alberta, with local physicians, difficult to track. Logical approach and agree w/ proposal. Situations where private practitioners, clinics may have unique identifier, and may have multiple doctors at a Location.
• Smita - Agreement, w example of Shoppers Drug Mart w/ Organization. Should go with 0..* and no MustSupport. Can reassess in future if there are new use-cases or requirements
• Agreement to loosen constraint.
• Action: Update profile Location.identitifier cardinality 0.. , remove MustSupport
Issue #50
• Practitioner.identifier slicing …
• Initial plan was slice on Patient (particularly for Juridictional health numbers), and then apply similar to logic to practitioner/organization/location.
• Scott: each province approaches differently. Alberta - provider number is the billing number, which is diff from the licence number. These would be meaningful distinctions in jurisdictions.
• Russ: no significant difference in how slicing would impact the implementions -- doesn't add anything.
• Jorge: BC, identified via billing number. Also have college ID, part of college of physicians.
• Harsh - Should be a guiding document from federal level?
• Smita - Some of the billing and licence may be captured under Practitioner vs PractitionerRole, and may need use-case specific determination.
• Action: Update profile, remove slicing from Patient.identifier
• Also applies to Issue #52 (Location) and Issue #58 (Organization)
• Action: Update profiles, remove slicing from Organization.identifier , Location.identifier
Final remarks:
• Ken: Number of resources for review are challenging time-wise/schedule-wise. May need to slow down pace some.
• Action: Russ to pass feedback along to Mike.
• Smita: What is status of the Patient resource review, as well as the related Terminology content? Are they finalized for the Patient resource?
• Action: Russ to pass along suggestion to add this to discussion at next meeting.
• Smita: Where will guide and guidance be published.
• Russ: Profiles are currently generating to simplifier and build.fhir.org. Narrative only going to latter … this is a config item in simplifier that needs to set and tested.
• Action: Russ to pass along suggestion to include this in the topic above.
Please Log in or Create an account to join the conversation.
- Michael Savage
- Topic Author
- Away
- Posts: 453
5 years 3 months ago #5197
by Michael Savage
Canadian FHIR Baseline Profiles - Profiling Stream Meeting - August 16th, 2-3pm EST was created by Michael Savage
Hi all,
For the Profiling Call taking place on Friday August 16th, 2-3pm ET, the planned agenda is to discuss a selection of the proposed changes submitted for the current batch of draft Canadian Core Profiles: Practitioner, Organization, Location, ProviderRole, OrganizationAffiliation. Please feel free to review the relevant proposed changes (posted as issues in GitHub) in advance of the meeting. github.com/scratch-fhir-profiles/CA-Core/issues
In terms of correspondence, I will be unavailable from the evening of Tues the 13th to the evening of Sunday the 18th. A big thank-you to Russ Buchanan who will be chairing the call and facilitating the discussion!
-Mike
For the Profiling Call taking place on Friday August 16th, 2-3pm ET, the planned agenda is to discuss a selection of the proposed changes submitted for the current batch of draft Canadian Core Profiles: Practitioner, Organization, Location, ProviderRole, OrganizationAffiliation. Please feel free to review the relevant proposed changes (posted as issues in GitHub) in advance of the meeting. github.com/scratch-fhir-profiles/CA-Core/issues
In terms of correspondence, I will be unavailable from the evening of Tues the 13th to the evening of Sunday the 18th. A big thank-you to Russ Buchanan who will be chairing the call and facilitating the discussion!
-Mike
Please Log in or Create an account to join the conversation.