Thursday 12pm EST Weekly Call re. OpenEMR CCR/CCD Integration
This week’s theme: Code & test review of the CCR/CCD module
1-213-289-0500 Access Code: 1522905
The first half of this call is for developers - please have your developers attend the 1st half of this call.
Agenda:
1. Code Review of the OpenEMR CCR/CCD module
2. NIST sample patient record for testing CCR and CCD
3. Demonstration of NIST Validators for CCR and CCD
4. Improvements needed for the CCR/CCD module
5. Assignment to CCR/CCD developers
Usual updates from OpenEMR CCR/CCD integration projects:
A web conference link will be emailed to attendees 15 minutes before the call. To recieve the web conference link, please post your name, affiliation and email address to this thread and you will be added to the list.
Thank you to Phyaura for contributing the CCR/CCD capability: “Save As XML/XSL” We need a volunteer to further develop this capability to include “Save As PDF”, and “Print PDF”
Thank you to ZH Healthcare for their offer to contribute a development resource to the CCR/CCD module.
All the CCR/CCD code is in the openemr/ccr directory.
The name of the CCR & CCD files are ccrDebug.xml and ccdDebug.xml
ccrDebug.xml and ccdDebug.xml are generated and consumed “on the fly”
OpenEMR will save a copy of ccrDebug.xml and ccdDebug.xml if the OpenEMR admin creates the directory: openemr/ccr/generatedXML.
The top level php file that creates both CCR and CCD is createCCR.php. The process to create a CCD.xml is: a CCR.xml is created and then XSLT’d by CCR-CCD.XSL to create CCD.xml
John contacted me asking for help to create a “save as” feature so users/developers/testers could see the raw xml of the CCD and CCR reports within OpenEMR. This was really minimal work, so contributed this feature to the official sourceforge codebase last night (so is in the ‘master’ branch). Here’s the details of the commit:
CCR/CCD reporting module: added option to see the raw xml
1. Note need to enable ‘Activate CCR/CCD Reporting’ in
Administration=>Globals=>Features for these reports
to show up.
2. Reports can be viewed in Patient Summary Screen =>
Report. Note the ‘Formatted Report’ creates nice
looking formatted output while the ‘Raw Report’
simply shows the xml output.
Guidance and information for OpenEMR CCR.xml development
The file “ccrDebugJD-2.xml” has no health data in it but does have the proper CCR.xml structure for Medications, Procedures, and Result. I.e., this file ran through the CCR validator with no errors other than content errors. So this file will inform you of which Results elements the CCR Validator wants to see, and the XML structure that the validator wants to see. (try running this file through the CCR validator – all errors should have to do with missing content, not invalid XML structure.)
In the OpenEMR CCR/CCD Module there is a program by the name of CreateCCR.php, which calls subprograms for each section of the CCR. E.g., CreateCCRmedications.php, and CreateCCRresults.php.
Use CreateCCRmedications.php as a reference for how to create the SQL statement(s) in CreateCCRresults.php to read the individual lab test data elements, as indicated as required by ccrDebugJD-2.xml, from the OpenEMR database.
Then use CreateCCR medications.php as a reference for how to program the output of XML structure and data elements in createCRRresults.php, as indicated is required by ccrDebugJD-2.xml.
To test your CCR, run it through the validator (hosted by ViSolve – thanks Selvi!):