A validation channel is available on the OpenHIM interoperality layer for testing and validating transactions for the Connectathon Conformance Tests
1. Summary doc with explanation of how to connect
2. Messaging specification - to be updated
https://jembiprojects.jira.com/wiki/display/NPRE/Save+Registration+Encounter
Message specification - CDA template
3. Online support by Jembi available at
http://www.hipchat.com/ to be set up / updated
See the box folder for miscellaneous scripts and utilities
4. TestingTransactions take the form of a MIME multipart HTTP message over a RESTful interface.
The MIME content consists of 1) MHD metadata and 2) a CDA document.
POST transaction to
https://npr-him.jembi.org:5000/ws/rest/v1/registration/validate (update end points?)
The channel uses 'Basic auth' with
user: test
password: test
Response of 200 OK - anything else indicates an error with descriptions of the errors.
Plain HTTP channel available on port 5001
5. HIM Console
http://npr-him.jembi.org:8081/
user: test
password: test
Scenarios and Technical Design
Scenario 1 (Plan A) MomConnect Use Case
Save Registration Encounter using MHD and CDA
Scenario 2 (Plan B) Query / retrieve demographic data
Retrieve Patient Encounters using the MHD profile
Recent space activity
| Recent updates | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Space contributors
Standards used
CDA
The HL7 Clinical Document Architecture (CDA) is an XML-based markup standard intended to specify the encoding, structure and semantics of clinical documents for exchange. CDA is part of the HL7 version 3 standard. CDA documents are persistent in nature. The CDA specifies that the content of the document consists of a mandatory textual part (which ensures human interpretation of the document contents) and optional structured parts (for software processing). The structured part relies on coding systems (such as from SNOMED and LOINC) to represent concepts.
IHE (Integrating the Healthcare Enterprise) Profiles describe specific solutions to integration problems across various categories or domains (such as IT Infrastructure or Patient Care Coordination) and the CDA Section Content Modules define the sections that may appear in a medical document. The following IHE profiles we are proposing to use are:
MHD
The IHE Mobile access to Health Documents profile provides a RESTful interface to Document Sharing including XDS.
http://wiki.ihe.net/index.php?title=Mobile_access_to_Health_Documents_(MHD) defines interfaces for sending and retrieving documents. See http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_Suppl_MHD.pdf for full details around this.
PIX
The Patient Identifier Cross Referencing (PIX) Integration Profile supports the cross-referencing of patient identifiers from multiple Patient Identifier domains.
http://wiki.ihe.net/index.php?title=Patient_Identifier_Cross_Referencing
PDQ
The Patient Demographics Query for HL7v3 (PDQv3) Integration Profile lets applications query a central patient information server and retrieve a patient’s demographic and visit information.
http://wiki.ihe.net/index.php?title=Patient_Demographics_Query_HL7_v3