New Namespace OID request
- Joanie Harper
- Hors Ligne
- Messages : 267
il y a 1 an 5 mois #8544
par Joanie Harper
Réponse de Joanie Harper sur le sujet New Namespace OID request
Unfortunately the comment period has already expired and the OID has been registered,
From the previous messages in this thread however, it appears that the OID is for an EMR solution that is called Collaborative Health Record.
This OID already exists and Telus just wanted it registered in the HL7 OID Registry.
From the request form:
- the description of the OID is: OID to identify Collaborative Health Record as a vendor
- the Jurisdiction is CA
From the previous messages in this thread however, it appears that the OID is for an EMR solution that is called Collaborative Health Record.
This OID already exists and Telus just wanted it registered in the HL7 OID Registry.
From the request form:
- the description of the OID is: OID to identify Collaborative Health Record as a vendor
- the Jurisdiction is CA
Connexion ou Créer un compte pour participer à la conversation.
- Randy Nonay
- Hors Ligne
- Messages : 85
il y a 1 an 5 mois #8543
par Randy Nonay
Réponse de Randy Nonay sur le sujet New Namespace OID request
It would seem to me that several things are lacking in this request.
The defintion is pretty vague - "OID to identify Collaborative Health Record as a vendor"
What is a Collaborative Health Record? What is the scope (jurisdiction)? Who tracks the values in the domain? How is it used?
Also chr as a short name is not real good - there are too many similar OIDs. (eg 2.16.840.1.113883.3.90 ) Adding a scope tot he short name is recommended...
The defintion is pretty vague - "OID to identify Collaborative Health Record as a vendor"
What is a Collaborative Health Record? What is the scope (jurisdiction)? Who tracks the values in the domain? How is it used?
Also chr as a short name is not real good - there are too many similar OIDs. (eg 2.16.840.1.113883.3.90 ) Adding a scope tot he short name is recommended...
Connexion ou Créer un compte pour participer à la conversation.
- Joanie Harper
- Hors Ligne
- Messages : 267
il y a 1 an 5 mois #8542
par Joanie Harper
Réponse de Joanie Harper sur le sujet New Namespace OID request
The OID 2.16.840.1.113883.3.368.1022 has now been registered in the HL7 OID Registry.
Best Regards,
Joanie Harper
Best Regards,
Joanie Harper
Connexion ou Créer un compte pour participer à la conversation.
- sean vogel
- Auteur du sujet
- Hors Ligne
- Messages : 4
il y a 1 an 5 mois #8526
par sean vogel
Réponse de sean vogel sur le sujet New Namespace OID request
ok
Connexion ou Créer un compte pour participer à la conversation.
- Joanie Harper
- Hors Ligne
- Messages : 267
il y a 1 an 5 mois #8525
par Joanie Harper
Réponse de Joanie Harper sur le sujet New Namespace OID request
Hi Sean,
A FHIR URI is not needed and I will correct column G when I do the registration.
Could you also post this request to the FHIR Implementations work group.
Best Regards,
Joanie Harper
A FHIR URI is not needed and I will correct column G when I do the registration.
Could you also post this request to the FHIR Implementations work group.
Best Regards,
Joanie Harper
Connexion ou Créer un compte pour participer à la conversation.
- sean vogel
- Auteur du sujet
- Hors Ligne
- Messages : 4
il y a 1 an 5 mois #8524
par sean vogel
Réponse de sean vogel sur le sujet New Namespace OID request
Hi Joanie,
Yes I was looking to have 2.16.840.1.113883.3.368.1022 as a child of
2.16.840.1.113883.3.368 (which i what I have in column G)
similar to other EMR's registered to Telus HEALTH aka
2.16.840.1.113883.3.368.1021
What else is required? No I haven't requested a FHIR URI do I have to do that?
Yes I was looking to have 2.16.840.1.113883.3.368.1022 as a child of
2.16.840.1.113883.3.368 (which i what I have in column G)
similar to other EMR's registered to Telus HEALTH aka
2.16.840.1.113883.3.368.1021
What else is required? No I haven't requested a FHIR URI do I have to do that?
Connexion ou Créer un compte pour participer à la conversation.