HRM Setup:
oscar.propteries
oscar.properties needs to have some entries added in order to have the HRM module working against the new 4.1 specification provided by OMD. These details listed below are for TESTING purposes. Live or in production, each clinic will have it's on values to enter in the oscar.properties file.
...
OMD_HRM_DECRYPTION_KEY=8F597E238FC2C92CAC64F8797EB4572E
</snip>
Purpose:
This document explains two areas of testing required for HRM: 1) Conformance and 2) Functionality of Reports to be consumed by your EMR offering. It also includes information specific for you to be used during Validation Testing. The validation process will be performed in an isolated non-Production environment where no PHI data is used. You may opt to start development as soon as this letter is received, or wait until your official engagement with the OntarioMD Validation Team. Conformance testing is to be executed in sequence; functionality testing will follow. You will be engaged by OntarioMD’s Validation team at which time a walk-through of the process will be scheduled. Support prior to this engagement will be limited.
Workflow:
The Hospital Information System sends a patient report to HRM using HL7. HRM converts the patient report into the EMR standard message format, encrypts and stores the report in a sFTP folder for secure transmission to the intended funding eligible EMR Offering. The EMR polls the HRM sFTP folder to retrieve the report(s), which is integrated into the patient's record and the clinician's inbox for review and sign-off.
...
XSD and PPK
You need to have XSD and PPK files in the tomcat directory for the web application (i.e. /home/[user]/workspace/tomcat-local/webapps/OscarDocument/oscar/hrm/OMD). The XSD and PPK files needed for HRM include :
- mcmu_sk.ppk
- ontariomd_cds_dt.xsd
- report_manager_cds.xsd
- report_manager_dt.xsd