Join a community of interest
Standards and specifications to electronically share health information consistently, safely and reliably
Support for digital health implementations
Resources and enablers to accelerate clinical interoperability
What's going on in clinical interoperability and digital health
What this site is about, future plans and how to reach us
Share this page:
Welcome,
Guest
|
|
OIDs of the CodeSystems can be found within the JSON/XML. Does this suffice?
|
The administrator has disabled public write access.
|
|
I agree - OID is required to support v2 and v3 applications communicating with FHIR applications.
|
The administrator has disabled public write access.
|
|
CodeSystem OID stil required to support existing applications using various HL7 standards (v2, v3, CDA). Also required to support applications in the context of IHE profiles using OID.
|
The administrator has disabled public write access.
|
|
I believe these 3 are still essential, the only argument is version might not be useful in situations where there is a live update rather than batch update but that is minor.
|
The administrator has disabled public write access.
|
|
Hello,
At a past HL7 Community call, there was a suggestion to have the Terminology Gateway display the CodeSystem OID along with the CodeSystem URI. Currently, information regarding a subset is tabulated with the following: 1. Name of CodeSystem 2. URI of Codesystem 3. Version Just wanted to seek the community's feedback on whether there is any impact to usage and if it indeed warrants a change. Any thoughts or suggestions are welcome. |
The administrator has disabled public write access.
|
Improving the quality of patient care through the effective sharing of clinical information among health care organizations, clinicians and their patients.