Talk:OpenEMR QA against NIST
From Oemr
From ICSA testing lab for ONC-Meaningful use:
Kevin Brown wrote: Here are the answers to your previous questions. Sorry for the delay. Our responses are marked with ICSA>.
1. The NIST certification scripts do not define the test patient data used to certify CCR/CCD related MUOs (as far as I can see). Would it be useful to other customers to define test patient data for certification. If there were such a thing, OpenEMR developers could use ICSA defined certification test patient data in their development, the OpenEMR MU-1 development & certification timeline & effort will be reduced.
ICSA> We agree that sample files and/or test files should be created as far as CCDs and CCRs for the exchange clinical information test procedure for eligible providers and hospitals. For most of the other steps, it is probably not necessary to generate or supply a sample or test files, and that would be something the vendor would be responsible for.
2. Does ICSA use specific instances of CCR validator and CCD/CDA
validator in the certification process. If OpenEMR developers could use
the ICSA defined and hosted CCR and CCD validators in their development,
the OpenEMR MU-1 development & certification timeline & effort will be
reduced.
ICSA> AVT: NIST test procedures define the allowable test tools when a particular test tool is sanctioned. In the case of the CCR validator - the official tool can be found at: http://sourceforge.net/projects/ccrvalidator/
This is the version that testing bodies as well as those seeking certification should be using to arrive at consistent validation results.
As for hosting the tools themselves, that is something we are considering doing in the future.
3. Patient education materials. Some "experts" say that references in
the application to a good source of patient education material, such as
advancedweb or healthwise is sufficient to pass DTR170.304.e - 2:
Automatically Generate and Indicate Notifications and Care Suggestions
in an Ambulatory Setting. Is that trur or is that even more than is
needed?
ICSA> The test procedure is not overly prescriptive, and as a testing body that limits the scope and breadth of this test. Any material that could be provided to the patient - a URL, pdf, or ability to print on demand (and then shown using print preview) would suffice as the test procedure does not go into any detail as far as the source or specific type of material presented.
4. HL7 messages are used in several data exchange and reporting tools,
those same experts say that if '7Edit' can read the data it will pass.
ie: format checks only. How about that one?
ICSA> For two specific procedures - 170.302.k (immunization messages) and 170.306.g (labs to public health) - NIST has provided a validation tool. For those procedures you must be able to pass validation with zero errors (though warnings and alerts can be ignored). See the NIST site for the validation tool, and be sure to look at the documentation tab for sample messages.
http://xreg2.nist.gov:8080/HL7V2MuValidation2011/
For 170.302.l - syndromic surveillance - the test procedure is not specific as to what hl7 message profile is required, just the version - HL7 v2.3.1 or v2.5.1. A suggested message you could use would be an ADT message that included syndromic surveillance information such as a diagnoses of influenza. In this case, you would need to include all required fields and segments per the HL7 spec (V2.3.1 or V2.5.1). You could use a tool like 7edit to verify that the message you created did not trigger any errors (warnings and/or alerts would still be ok).
--Tony - www.mi-squared.com 21:52, 2 March 2011 (UTC) The links to the individual NIST tests are all wrong now, the gov't moved them to: http://healthcare.nist.gov/use_testing/effective_requirements.html
- This has been fixed --Tony - www.mi-squared.com 00:04, 4 March 2011 (UTC)
