Solution Architecture work stream
- Alexander Goel
- Hors Ligne
- Messages : 21
il y a 5 ans 2 mois #5258
par Alexander Goel
Réponse de Alexander Goel sur le sujet Solution Architecture work stream
Hi, is there a solution Architecture call Friday?
Alex
Alex
Connexion ou Créer un compte pour participer à la conversation.
- Igor Sirkovich
- Hors Ligne
- Messages : 181
il y a 5 ans 3 mois #5234
par Igor Sirkovich
Réponse de Igor Sirkovich sur le sujet FHIR Implementation Community - Solution Architecture Call (2019-07-12 2pm-3pm EST) Minutes
At our meeting on August 23rd, Dr. Marion Lyver will talk about the ISO TC215 work on Intelligent EHRs.
She will also be seeking information about Canadian Initiatives for Intelligent EHRs in preparation to the ISO TC215 meeting in South Korea in November.
She will also be seeking information about Canadian Initiatives for Intelligent EHRs in preparation to the ISO TC215 meeting in South Korea in November.
Connexion ou Créer un compte pour participer à la conversation.
- Ken Sinn
- Hors Ligne
- Messages : 84
il y a 5 ans 4 mois #5155
par Ken Sinn
Réponse de Ken Sinn sur le sujet FHIR Implementation Community - Solution Architecture Call (2019-07-12 2pm-3pm EST) Minutes
Thanks to Joel for reaching out to Firely regarding our request for project key/name/description recommendation. While Firely has no recommended approaches and suggest that organizations develop their own nomenclature, they did suggest taking a look at FHIR package naming conventions as documented at wiki.hl7.org/index.php?title=FHIR_NPM_Package_Spec#Package_name for ideas and considerations.
We will follow up in the next few days, giving people in this workgroup some time to review the content at the link above.
We will follow up in the next few days, giving people in this workgroup some time to review the content at the link above.
Connexion ou Créer un compte pour participer à la conversation.
- Ken Sinn
- Hors Ligne
- Messages : 84
il y a 5 ans 4 mois #5143
par Ken Sinn
Réponse de Ken Sinn sur le sujet FHIR Implementation Community - Solution Architecture Call (2019-07-12 2pm-3pm EST) Minutes
Attendees:
Agenda:
Review/Confirm proposal for Simplifier project naming conventions
* Alex Goel asked about the scope of the naming convention and the Canadian FHIR Registry, e.g whether all Canadian FHIR-related projects needed to adhere to these conventions. The scope of the naming convention is limited to the projects published using the Canadian FHIR Registry.
* Finnie Flores suggested asking Firely for project naming recommendations. Action Item for Joel Francis: Joel to ask Firely and provide update to the group.
* Joel Francis noted that consistency in project key is helpful, particular as other FHIR publication content will be referencing projects via their project key.
* Anne Belford wanted to know if the scope for the Canadian FHIR Registry is limited to public sector, e.g. whether a FHIR eClaims specification from Telus would be appropriate for publication in the Canadian FHIR Registry. Joel Francis stated that the Canadian FHIR Registry is intended to be used for all Canadian projects, and to contact Cette adresse courriel est protégée contre les robots spammeurs. Vous devez activer le JavaScript pour la visualiser. to publish on the Canadian FHIR Registry.
* Pending any conflicting project naming recommendations from Firely, we will start adopting the proposed naming conventions for Project Name, Project Description, and Project Key (Project Key only for new projects, Project Name and Project Description for new and existing/retroactive projects).
Answer any questions on the URI Registry Process
* Joel Francis described the URI Registry Process, which was adapted the OIDs process for URI requests. Three Actors: Requester, Canadian Jurisdiction, URI Owner/Responsible Body (e.g. Health Canada, if there was a URI requested related to Health Canada - Active Ingredient Codes, but this is more applicable to OIDs and OIDs domain ownership).
* Finnie Flores suggested that the final documentation provide a link to the URI registry (referenced in Step 1), as well as contact information for each jurisdiction.
* Randy Nonay and Finnie Flores suggested that in additional to Canadian URI Registry, Step 1 should also check in Jurisdictional URI Registry and International URI Registry (www.hl7.org/fhir/terminologies-systems.html), and also recognize that each HL7 FHIR release may have slightly different lists of URIs.
* There were no objects to the proposed Five Business Days for responses.
Update on FHIR CA-Core (Canadian Baseline)
* Ken Sinn provided updates from the last CA-Core Profiling call and CA-Core Governance call.
* Anne Belford asked for some context around the CA-Core goals and parameters, some of which is available at github.com/scratch-fhir-profiles/CA-Core/blob/master/README.md and build.fhir.org/ig/scratch-fhir-profiles/CA-Core/
- Ken Sinn
- Joel Francis
- Anne Belford
- Natalya Pogrebetsky
- Randy Nonay (Alberta)
- Alex Goel
- Rita Pyle
- Thomas Zhou
- Finnie Flores
- Janice Spence
- Iryna Roy
- Sisira De Silva (NLCHI)
Agenda:
- Review/Confirm proposal for Simplifier project naming conventions
- Answer any questions on the URI Registry Process
- Update on FHIR CA-Core (Canadian Baseline)
Review/Confirm proposal for Simplifier project naming conventions
* Alex Goel asked about the scope of the naming convention and the Canadian FHIR Registry, e.g whether all Canadian FHIR-related projects needed to adhere to these conventions. The scope of the naming convention is limited to the projects published using the Canadian FHIR Registry.
* Finnie Flores suggested asking Firely for project naming recommendations. Action Item for Joel Francis: Joel to ask Firely and provide update to the group.
* Joel Francis noted that consistency in project key is helpful, particular as other FHIR publication content will be referencing projects via their project key.
* Anne Belford wanted to know if the scope for the Canadian FHIR Registry is limited to public sector, e.g. whether a FHIR eClaims specification from Telus would be appropriate for publication in the Canadian FHIR Registry. Joel Francis stated that the Canadian FHIR Registry is intended to be used for all Canadian projects, and to contact Cette adresse courriel est protégée contre les robots spammeurs. Vous devez activer le JavaScript pour la visualiser. to publish on the Canadian FHIR Registry.
* Pending any conflicting project naming recommendations from Firely, we will start adopting the proposed naming conventions for Project Name, Project Description, and Project Key (Project Key only for new projects, Project Name and Project Description for new and existing/retroactive projects).
Answer any questions on the URI Registry Process
* Joel Francis described the URI Registry Process, which was adapted the OIDs process for URI requests. Three Actors: Requester, Canadian Jurisdiction, URI Owner/Responsible Body (e.g. Health Canada, if there was a URI requested related to Health Canada - Active Ingredient Codes, but this is more applicable to OIDs and OIDs domain ownership).
* Finnie Flores suggested that the final documentation provide a link to the URI registry (referenced in Step 1), as well as contact information for each jurisdiction.
* Randy Nonay and Finnie Flores suggested that in additional to Canadian URI Registry, Step 1 should also check in Jurisdictional URI Registry and International URI Registry (www.hl7.org/fhir/terminologies-systems.html), and also recognize that each HL7 FHIR release may have slightly different lists of URIs.
* There were no objects to the proposed Five Business Days for responses.
Update on FHIR CA-Core (Canadian Baseline)
* Ken Sinn provided updates from the last CA-Core Profiling call and CA-Core Governance call.
* Anne Belford asked for some context around the CA-Core goals and parameters, some of which is available at github.com/scratch-fhir-profiles/CA-Core/blob/master/README.md and build.fhir.org/ig/scratch-fhir-profiles/CA-Core/
Connexion ou Créer un compte pour participer à la conversation.
- Ken Sinn
- Hors Ligne
- Messages : 84
il y a 5 ans 4 mois #5136
par Ken Sinn
Réponse de Ken Sinn sur le sujet FHIR Implementation Community - Solution Architecture Call (2019-06-14 2pm-3pm EST)
I can chair the meeting for July 12th, and run through the agenda.
Current Agenda Items:
* Review/Confirm proposal for Simplifier project naming conventions
* Answer any questions on the URI Registry Process
* Update on FHIR CA-Core (Canadian Baseline)
Any other Agenda Items?
Current Agenda Items:
* Review/Confirm proposal for Simplifier project naming conventions
* Answer any questions on the URI Registry Process
* Update on FHIR CA-Core (Canadian Baseline)
Any other Agenda Items?
Connexion ou Créer un compte pour participer à la conversation.
- Joel Francis
- Hors Ligne
- Messages : 169
il y a 5 ans 4 mois #5134
par Joel Francis
Réponse de Joel Francis sur le sujet FHIR Implementation Community - Solution Architecture Call (2019-06-14 2pm-3pm EST)
The meeting scheduled for today July 12th is cancelled? I wanted to add the URI Registry process discussed on the HL7 call to the agenda in case they were any pending questions.
Connexion ou Créer un compte pour participer à la conversation.