New Namespace OID request
- Joanie Harper
- Offline
- Posts: 266
1 year 3 months ago #8544
by Joanie Harper
Replied by Joanie Harper on topic 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
Please Log in or Create an account to join the conversation.
- Randy Nonay
- Offline
- Posts: 85
1 year 3 months ago #8543
by Randy Nonay
Replied by Randy Nonay on topic 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...
Please Log in or Create an account to join the conversation.
- Joanie Harper
- Offline
- Posts: 266
1 year 3 months ago #8542
by Joanie Harper
Replied by Joanie Harper on topic 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
Please Log in or Create an account to join the conversation.
- sean vogel
- Topic Author
- Offline
- Posts: 4
1 year 4 months ago #8526
by sean vogel
Replied by sean vogel on topic New Namespace OID request
ok
Please Log in or Create an account to join the conversation.
- Joanie Harper
- Offline
- Posts: 266
1 year 4 months ago #8525
by Joanie Harper
Replied by Joanie Harper on topic 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
Please Log in or Create an account to join the conversation.
- sean vogel
- Topic Author
- Offline
- Posts: 4
1 year 4 months ago #8524
by sean vogel
Replied by sean vogel on topic 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?
Please Log in or Create an account to join the conversation.