- Forum
- Working Groups
- FHIR® Implementations
- Canadian FHIR Baseline Profiles - Profiling Updates + DDR Pilot - August 14th, 2-3pm
Canadian FHIR Baseline Profiles - Profiling Updates + DDR Pilot - August 14th, 2-3pm
- Tim Berezny
- Hors Ligne
- Messages : 84
il y a 4 ans 3 mois #6225
par Tim Berezny
Réponse de Tim Berezny sur le sujet Canadian FHIR Baseline Profiles - Profiling Updates + DDR Pilot - August 14th, 2-3pm
For reference, here is what eReferral come up with for PractitionerRole
simplifier.net/ereferral-ontario/ereferralpractitionerrole
simplifier.net/ereferral-ontario/ereferralpractitionerrole
Connexion ou Créer un compte pour participer à la conversation.
- Tim Berezny
- Hors Ligne
- Messages : 84
il y a 4 ans 3 mois #6224
par Tim Berezny
Réponse de Tim Berezny sur le sujet Canadian FHIR Baseline Profiles - Profiling Updates + DDR Pilot - August 14th, 2-3pm
- .practitioner - eReferral has 0..1. That being said, a practitionerRole is pretty meaningless without a practitioner...
- .specialty - should NOT be 1..1. The concept of a practitioner goes beyond physician specialists, like case managers or even clerks. (I don't follow the comment about alternatively using the "general CA PractitionerRole..."
- . telecom - CA Baseline = 0..* MS vs PPR = 0..* <--- these are the same, was it written correctly? It should be 0..*. It's better to put a telecom on the role than the practitioner, but it doesn't need to be mandatory in practitionerRole.
- .specialty - should NOT be 1..1. The concept of a practitioner goes beyond physician specialists, like case managers or even clerks. (I don't follow the comment about alternatively using the "general CA PractitionerRole..."
- . telecom - CA Baseline = 0..* MS vs PPR = 0..* <--- these are the same, was it written correctly? It should be 0..*. It's better to put a telecom on the role than the practitioner, but it doesn't need to be mandatory in practitionerRole.
Connexion ou Créer un compte pour participer à la conversation.
- Michael Savage
- Auteur du sujet
- Hors Ligne
- Messages : 453
il y a 4 ans 3 mois #6223
par Michael Savage
Réponse de Michael Savage sur le sujet Canadian FHIR Baseline Profiles - Profiling Updates + DDR Pilot - August 14th, 2-3pm
Attendees
Michael Savage
Sheridan Cook
Rita Pyle
Shamil Nizamov
Kenneth Sinn
Randy Nonay
• Group compared CA Baseline – PractitionerRole (Registry) with Ontario PPR – PractitionerRole (Response)
• .identifier.type
o PPR has the element bound to a value set; not a conformance issue, but worth noting that PPR includes different codes, & these will be used frequently
• .practitioner (reference)
o Discrepancy: CA Baseline = 1..1 MS vs PPR = 0..1 MS
o Flagged to keep on radar, and see if other iGuides have the same discrepancy
• .specialty
o Discrepancy: CA Baseline = 1..1 MS vs PPR = 0..* MS
o In Alberta context, provider role has a specialty associated with it
o One option is if the implementer can’t comply with the 1..1 constraint, they can use the general PractitionerRole CA Baseline Profile, which doesn’t have the 1..1 constraint
o Flagged to keep on radar, will look at this element in other specs to see what their constraints (or lack thereof) are
• .telecom
o Discrepancy: CA Baseline = 0..* MS vs PPR = 0..*
o The CA’s MS is inherited from the general PractitionerRole Profile
o Alberta has the telecom attached to the role
o Flagged as a discrepancy and will continue to see if other IGs are flagging .telecom as MS
Michael Savage
Sheridan Cook
Rita Pyle
Shamil Nizamov
Kenneth Sinn
Randy Nonay
• Group compared CA Baseline – PractitionerRole (Registry) with Ontario PPR – PractitionerRole (Response)
• .identifier.type
o PPR has the element bound to a value set; not a conformance issue, but worth noting that PPR includes different codes, & these will be used frequently
• .practitioner (reference)
o Discrepancy: CA Baseline = 1..1 MS vs PPR = 0..1 MS
o Flagged to keep on radar, and see if other iGuides have the same discrepancy
• .specialty
o Discrepancy: CA Baseline = 1..1 MS vs PPR = 0..* MS
o In Alberta context, provider role has a specialty associated with it
o One option is if the implementer can’t comply with the 1..1 constraint, they can use the general PractitionerRole CA Baseline Profile, which doesn’t have the 1..1 constraint
o Flagged to keep on radar, will look at this element in other specs to see what their constraints (or lack thereof) are
• .telecom
o Discrepancy: CA Baseline = 0..* MS vs PPR = 0..*
o The CA’s MS is inherited from the general PractitionerRole Profile
o Alberta has the telecom attached to the role
o Flagged as a discrepancy and will continue to see if other IGs are flagging .telecom as MS
Connexion ou Créer un compte pour participer à la conversation.
- Michael Savage
- Auteur du sujet
- Hors Ligne
- Messages : 453
il y a 4 ans 3 mois #6211
par Michael Savage
Canadian FHIR Baseline Profiles - Profiling Updates + DDR Pilot - August 14th, 2-3pm a été créé par Michael Savage
Hi all!
A reminder that this Friday we will be sharing the 2-3pm EST timeslot for the routine clinical profile updates to provide a timeslot for the due diligence review process wherein we will compare the CA Baseline to Ontario's Provincial Provider Registry iGuide (will focus on the profiles common to both profile sets).
2 - 2:30pm: Clinical Stream updates
2:30 - 3pm: Due Diligence Review: CA Baseline <> Ontario Provincial Provider Registry
A reminder that this Friday we will be sharing the 2-3pm EST timeslot for the routine clinical profile updates to provide a timeslot for the due diligence review process wherein we will compare the CA Baseline to Ontario's Provincial Provider Registry iGuide (will focus on the profiles common to both profile sets).
2 - 2:30pm: Clinical Stream updates
2:30 - 3pm: Due Diligence Review: CA Baseline <> Ontario Provincial Provider Registry
Connexion ou Créer un compte pour participer à la conversation.