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
|
|
|
Hello,
In NL, our provincial Medical Care Plan (MCP) office is capturing organ donor information upon renewal of an individual’s MCP card. MCP shares demographic information with our Client Registry (CR) via a nightly batch file transfer; we would like to add the organ donor data to the nightly file transfer, store this in CR and then make it available to consuming systems. The organ donor data will consist of a one char flag either "Y" for yes or "U" for unknown. We have systems connecting to our EHR and querying CR data through both HL7v2 and HL7v3 interfaces. The organ donor flag can be accommodated within the HL7v2 interface but there is not a placeholder or code set currently to transmit this data via the HL7v3 interface. CR message version: V02R02.0 (20071207). NLCHI would like to request a variance to the HL7v3 CR message spec to accommodate this organ donor flag request. Thanks, Sisira (NLCHI) |
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.