Solution Architecture work stream
- Thomas Zhou
- Hors Ligne
- Messages : 25
il y a 5 ans 5 mois #4988
par Thomas Zhou
Réponse de Thomas Zhou sur le sujet setup FHIR URI registry of Alberta Jurisdiction
Hi Joel and Igor,
Alberta is looking to set up a FHIR URI registry based on the Infoway model.
We have noticed that BC has created a “BC Core” URI registry, and are looking for guidance if this is the preferred way for jurisdictional URI registries on simplifier.net.
Or should we not be posting our jurisdictional URIs on simplifier?
We believe that any URIs (and OIDs) we register at a national level should appear in the Canadian FHIR URI Registry. For compatibility, we intend to have both OIDs and URIs for all domains we register until such time as one of them is no longer used.
If this is the recommended approach, how do we go about getting accounts for the Alberta team on simplifier, and have those accounts able to update/maintain Alberta URIs on both the Infoway list as well as the Alberta list? Also, how to create an Alberta URI Registry project?
Finally, we also propose that the URI for jurisdiction level URIs be modified to the general form of:
fhir.jurisdiction.ca/NamingSystem/ca-??-*
Example for Alberta: fhir.alberta.ca/NamingSystem/ca-ab-*
This would allow implementers to easily identify if a URI is for Canada (fhir.infoway-inforoute.ca) or a jurisdiction target domain. With the current BC Core URIs using the same root as the national URIs, it is not easy to identify that they are jurisdictional. This problem will get much worse if all provinces are using the Infoway root to create their own jurisdictional URIs.
Thomas Zhou and Randy Nonay
Alberta is looking to set up a FHIR URI registry based on the Infoway model.
We have noticed that BC has created a “BC Core” URI registry, and are looking for guidance if this is the preferred way for jurisdictional URI registries on simplifier.net.
Or should we not be posting our jurisdictional URIs on simplifier?
We believe that any URIs (and OIDs) we register at a national level should appear in the Canadian FHIR URI Registry. For compatibility, we intend to have both OIDs and URIs for all domains we register until such time as one of them is no longer used.
If this is the recommended approach, how do we go about getting accounts for the Alberta team on simplifier, and have those accounts able to update/maintain Alberta URIs on both the Infoway list as well as the Alberta list? Also, how to create an Alberta URI Registry project?
Finally, we also propose that the URI for jurisdiction level URIs be modified to the general form of:
fhir.jurisdiction.ca/NamingSystem/ca-??-*
Example for Alberta: fhir.alberta.ca/NamingSystem/ca-ab-*
This would allow implementers to easily identify if a URI is for Canada (fhir.infoway-inforoute.ca) or a jurisdiction target domain. With the current BC Core URIs using the same root as the national URIs, it is not easy to identify that they are jurisdictional. This problem will get much worse if all provinces are using the Infoway root to create their own jurisdictional URIs.
Thomas Zhou and Randy Nonay
Connexion ou Créer un compte pour participer à la conversation.
- Igor Sirkovich
- Hors Ligne
- Messages : 181
il y a 5 ans 7 mois #4899
par Igor Sirkovich
Réponse de Igor Sirkovich sur le sujet Solution Architecture work stream
I just wanted to remind that there is no meeting on April 19 as this is a public holiday.
Connexion ou Créer un compte pour participer à la conversation.
- Igor Sirkovich
- Hors Ligne
- Messages : 181
il y a 5 ans 8 mois #4800
par Igor Sirkovich
Réponse de Igor Sirkovich sur le sujet Solution Architecture work stream
Please note that the meeting on Friday, March 22 is cancelled.
Apologies for the last minute notice.
Apologies for the last minute notice.
Connexion ou Créer un compte pour participer à la conversation.
- Igor Sirkovich
- Hors Ligne
- Messages : 181
il y a 5 ans 8 mois #4770
par Igor Sirkovich
Réponse de Igor Sirkovich sur le sujet Solution Architecture work stream
Hello,
As pre our discussion last Friday, below is a list of the new URIs we are going to add to the Canadian Registry.
As pre our discussion last Friday, below is a list of the new URIs we are going to add to the Canadian Registry.
- Manitoba, Canada, Physician License Number (assigned by College of Physicians and Surgeons of Manitoba): fhir.infoway-inforoute.ca/NamingSystem/ca-mb-license-physician
- Quebec, Canada, Physician License Number (assigned by College des Medecins du Quebec): fhir.infoway-inforoute.ca/NamingSystem/ca-qc-license-physician
- Ontario, Canada Osteopath Registration Number: fhir.infoway-inforoute.ca/NamingSystem/ca-on-registration-osteopath
Connexion ou Créer un compte pour participer à la conversation.
- Igor Sirkovich
- Hors Ligne
- Messages : 181
il y a 5 ans 9 mois #4624
par Igor Sirkovich
Réponse de Igor Sirkovich sur le sujet Solution Architecture work stream
Hello, this is a reminder about our meeting today at 2 pm eastern time.
At our next meeting, we will have an exciting presentations: Alexander Henket from Nictiz will be talking to us about his experience with building national FHIR profiles in the Netherlands.
Please download the new iCal file for our 2019 meetings and add it to your calendar.
At our next meeting, we will have an exciting presentations: Alexander Henket from Nictiz will be talking to us about his experience with building national FHIR profiles in the Netherlands.
Please download the new iCal file for our 2019 meetings and add it to your calendar.
Connexion ou Créer un compte pour participer à la conversation.
- Igor Sirkovich
- Hors Ligne
- Messages : 181
il y a 5 ans 10 mois #4572
par Igor Sirkovich
Réponse de Igor Sirkovich sur le sujet Solution Architecture work stream
Happy New Year Everyone,
Our meeting series had ended in December. Please download the new iCal file for our 2019 meetings and add it to your calendar.
Our meeting series had ended in December. Please download the new iCal file for our 2019 meetings and add it to your calendar.
Connexion ou Créer un compte pour participer à la conversation.