- Forum
- Working Groups
- FHIR® Implementations
- Canadian FHIR Baseline Profiles - Profiling Stream Meeting - July 19th, 2-3pm EST
Canadian FHIR Baseline Profiles - Profiling Stream Meeting - July 19th, 2-3pm EST
- Ken Sinn
- Hors Ligne
- Messages : 84
il y a 5 ans 4 mois #5168
par Ken Sinn
Réponse de Ken Sinn sur le sujet Canadian FHIR Baseline Profiles - Profiling Stream Meeting - July 19th, 2-3pm EST
Additional attendees captured in my notes:
- Alex Goel
- Joe Wall
- Alex Goel
- Joe Wall
Connexion ou Créer un compte pour participer à la conversation.
- Michael Savage
- Auteur du sujet
- Hors Ligne
- Messages : 453
il y a 5 ans 4 mois #5167
par Michael Savage
Réponse de Michael Savage sur le sujet Canadian FHIR Baseline Profiles - Profiling Stream Meeting - July 19th, 2-3pm EST
Attendees
Russ Buchanan
Scott Prior
Finnie Flores
Raman Dhanoa
Sheridan Cook
Andrea MacLean
Francis Lau
Harsh Sharma
Igor Sirkovich
James Mitchell
Ken Sinn
Michel Boivin
Philip Alcaidinho
Smita Kachroo
Review of Patient Profile
Item #5: Patient_Suggestion_extension.race, extension.ethnicity
• (Suggestion is to add extensions for patient’s race and ethnicity)
• Number of non-clinical use cases capture this data
• Can also be captured through admissions
• Some clinical uses of this data as well; can have lab values that require race / ethnicity in order to be interpreted properly
• Other suggestion is to capture this info through the Observation profile
• Could be useful in CIHI context for these extensions
• Item #5 parked for now for others to weigh in on
Item #7: Patient, Practitioner_Extension_HumanName.given
• (Suggestion is to add an extension for a ‘qualifier’ which designates what ‘type’ a given name is [first vs middle, etc.])
• Currently, FHIR standard dictates you would just repeat this element for every given name you are supporting (i.e. you would use it 3 times for a first name and two middle names)
• This suggestion would be useful when performing patient matching functionality
• In Ontario’s provincial client registry (PCR) they distinguish the given name types
• Item #7 parked for now for others to weigh in on
Item #22: Patient_Cardinality_birthsex
• (Suggestion is to make birthsex’s cardinality mandatory [i.e. 1..1])
• Lots of systems do not have these values for patients; will cause interoperability issues
• Does the gender value cover these use cases?
• As a value that (at present) is not maintained by everyone, it is difficult to expect everyone to start maintaining it
•Item #22 parked for now for others to weigh in on
Summary of Experience discussing proposed changes on call
• The 3 items discussed are all still open for review / commenting on GitHub; there are about 20 other Patient profile items / proposed changes not discussed on the call
• Good experience and test of how much can be expected to be accomplished during these profiling stream calls; good material to bake into terms of reference material
• Is the plan to leave these ticketed items open? Yes. No need to close out these ambiguities on the call; having them open for subsequent discussion doesn’t hurt us.
• Working toward a connectathon (where profiles would be tested) is a good milestone because it helps us decide which issues we need to lock down versus leave open: “Do we need to force a decision on this item in time for a connectathon?”
• Action Item: Attendees on the call are asked to send Michael an email (Cette adresse courriel est protégée contre les robots spammeurs. Vous devez activer le JavaScript pour la visualiser.) if they have any feedback for how we can best move through the active items / proposed changes (e.g. is it best to have a short set of standard questions which can be used to help us work through the items in a consistent manner, etc.)
Russ Buchanan
Scott Prior
Finnie Flores
Raman Dhanoa
Sheridan Cook
Andrea MacLean
Francis Lau
Harsh Sharma
Igor Sirkovich
James Mitchell
Ken Sinn
Michel Boivin
Philip Alcaidinho
Smita Kachroo
Review of Patient Profile
Item #5: Patient_Suggestion_extension.race, extension.ethnicity
• (Suggestion is to add extensions for patient’s race and ethnicity)
• Number of non-clinical use cases capture this data
• Can also be captured through admissions
• Some clinical uses of this data as well; can have lab values that require race / ethnicity in order to be interpreted properly
• Other suggestion is to capture this info through the Observation profile
• Could be useful in CIHI context for these extensions
• Item #5 parked for now for others to weigh in on
Item #7: Patient, Practitioner_Extension_HumanName.given
• (Suggestion is to add an extension for a ‘qualifier’ which designates what ‘type’ a given name is [first vs middle, etc.])
• Currently, FHIR standard dictates you would just repeat this element for every given name you are supporting (i.e. you would use it 3 times for a first name and two middle names)
• This suggestion would be useful when performing patient matching functionality
• In Ontario’s provincial client registry (PCR) they distinguish the given name types
• Item #7 parked for now for others to weigh in on
Item #22: Patient_Cardinality_birthsex
• (Suggestion is to make birthsex’s cardinality mandatory [i.e. 1..1])
• Lots of systems do not have these values for patients; will cause interoperability issues
• Does the gender value cover these use cases?
• As a value that (at present) is not maintained by everyone, it is difficult to expect everyone to start maintaining it
•Item #22 parked for now for others to weigh in on
Summary of Experience discussing proposed changes on call
• The 3 items discussed are all still open for review / commenting on GitHub; there are about 20 other Patient profile items / proposed changes not discussed on the call
• Good experience and test of how much can be expected to be accomplished during these profiling stream calls; good material to bake into terms of reference material
• Is the plan to leave these ticketed items open? Yes. No need to close out these ambiguities on the call; having them open for subsequent discussion doesn’t hurt us.
• Working toward a connectathon (where profiles would be tested) is a good milestone because it helps us decide which issues we need to lock down versus leave open: “Do we need to force a decision on this item in time for a connectathon?”
• Action Item: Attendees on the call are asked to send Michael an email (Cette adresse courriel est protégée contre les robots spammeurs. Vous devez activer le JavaScript pour la visualiser.) if they have any feedback for how we can best move through the active items / proposed changes (e.g. is it best to have a short set of standard questions which can be used to help us work through the items in a consistent manner, etc.)
Connexion ou Créer un compte pour participer à la conversation.
- Michael Savage
- Auteur du sujet
- Hors Ligne
- Messages : 453
il y a 5 ans 4 mois #5162
par Michael Savage
Réponse de Michael Savage sur le sujet Canadian FHIR Baseline Profiles - Profiling Stream Meeting - July 19th, 2-3pm EST
Hi all,
In advance of tomorrow's call, if interested Community members can consult the current list of Patient profile proposed changes in the GitHub issue log (github.com/scratch-fhir-profiles/CA-Core/issues) and indicate their support / disagreement with the proposed changes by giving either a thumbs-up or thumbs-down emoticon for the issue (it's pretty straightforward, but email me if you're unclear how to do this), that would be great. This will really help us demonstrate how we can prioritize which proposed changes get discussed in meetings.
A side-note, if you choose to give a thumbs-down for a proposed change it is expected that you provide a comment which explains why.
Thank you!
In advance of tomorrow's call, if interested Community members can consult the current list of Patient profile proposed changes in the GitHub issue log (github.com/scratch-fhir-profiles/CA-Core/issues) and indicate their support / disagreement with the proposed changes by giving either a thumbs-up or thumbs-down emoticon for the issue (it's pretty straightforward, but email me if you're unclear how to do this), that would be great. This will really help us demonstrate how we can prioritize which proposed changes get discussed in meetings.
A side-note, if you choose to give a thumbs-down for a proposed change it is expected that you provide a comment which explains why.
Thank you!
Connexion ou Créer un compte pour participer à la conversation.
- Michael Savage
- Auteur du sujet
- Hors Ligne
- Messages : 453
il y a 5 ans 4 mois #5156
par Michael Savage
Canadian FHIR Baseline Profiles - Profiling Stream Meeting - July 19th, 2-3pm EST a été créé par Michael Savage
Hi all,
For this Friday's Profiling Stream Meeting (Friday July 19th, 2-3pm EST) the draft agenda is to look at the proposed changes that have been submitted by reviewers for the current draft of the Canadian Core Patient Profile. The issue log can be found here:
github.com/scratch-fhir-profiles/CA-Core/issues
Just to set expectations for the call, we will not be able to go through every proposed change for the Patient Profile during the call (there are around 20 of them); we will have to look at managing the volume of proposed changes (i.e. how to vote on all of them) as a work-in-progress.
Please keep in mind that, rather than waiting for the calls, you are always welcome and encouraged to email me at Cette adresse courriel est protégée contre les robots spammeurs. Vous devez activer le JavaScript pour la visualiser. if you have any questions.
Thank you!
The Zoom meeting details for joining the meeting can be found on the relevant calendar invite here:
infocentral.infoway-inforoute.ca/en/monthly-calendar/month.calendar/2019/07/16/1268
For this Friday's Profiling Stream Meeting (Friday July 19th, 2-3pm EST) the draft agenda is to look at the proposed changes that have been submitted by reviewers for the current draft of the Canadian Core Patient Profile. The issue log can be found here:
github.com/scratch-fhir-profiles/CA-Core/issues
Just to set expectations for the call, we will not be able to go through every proposed change for the Patient Profile during the call (there are around 20 of them); we will have to look at managing the volume of proposed changes (i.e. how to vote on all of them) as a work-in-progress.
Please keep in mind that, rather than waiting for the calls, you are always welcome and encouraged to email me at Cette adresse courriel est protégée contre les robots spammeurs. Vous devez activer le JavaScript pour la visualiser. if you have any questions.
Thank you!
The Zoom meeting details for joining the meeting can be found on the relevant calendar invite here:
infocentral.infoway-inforoute.ca/en/monthly-calendar/month.calendar/2019/07/16/1268
Connexion ou Créer un compte pour participer à la conversation.