|
|
| Line 70: |
Line 70: |
| | '''OPEN ISSUES / QUESTIONS''' | | '''OPEN ISSUES / QUESTIONS''' |
| | (Add details here) | | (Add details here) |
| − |
| |
| − | ===GAP ANALYSIS===
| |
| − | 12/11/2010 1:28 PM (EDT)
| |
| − | {| class="grey" border="1" cellpadding="2"
| |
| − | |-
| |
| − | |
| |
| − | '''Test Procedure ID'''
| |
| − |
| |
| − | |
| |
| − | '''VistA Functions'''
| |
| − |
| |
| − | |
| |
| − | '''Captured'''
| |
| − |
| |
| − | |
| |
| − | '''Comments'''
| |
| − |
| |
| − | |
| |
| − | '''Questions'''
| |
| − |
| |
| − | |
| |
| − | '''Testing Notes'''
| |
| − |
| |
| − | |-
| |
| − | |
| |
| − | VE170.306.d.1 – 1.01
| |
| − |
| |
| − | |
| |
| − | Create all five sample patients in advance using:
| |
| − |
| |
| − | - patient demographics (PIMS = JoAnne Brougham)
| |
| − |
| |
| − | - problem list (CPRS = CAC, Nedi Parks or Patti Henderson)
| |
| − |
| |
| − | - prescriptions (inpatient or outpatient? = Marv Friedman)
| |
| − |
| |
| − | - medication allergy (CPRS = Marv Friedman)
| |
| − |
| |
| − | - - need a Snomed code for the allergy type
| |
| − |
| |
| − | - - need to link RxNorm code to allergen
| |
| − |
| |
| − | - lab (enter, accession, verify = Dan Gray)
| |
| − |
| |
| − | - - need to link Lab tests to LOINC codes
| |
| − |
| |
| − | - procedures (CPRS, TIU = CAC again)
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |
| |
| − | Tester shall select one test data set from TD170.306.d.1 (Note contradiction with Required vendor information, which claims the vendor gets to pick the patient).
| |
| − |
| |
| − | - We need to document how to do all of these things and train our lead tester and backup testers to be able to do all of this.
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |-
| |
| − | |
| |
| − | VE170.306.d.1 – 1.01
| |
| − |
| |
| − | |
| |
| − | Have Marv Friedman review drug requirements:
| |
| − |
| |
| − | - are these inpatient pharmacy or outpatient
| |
| − |
| |
| − | - if outpatient, can we use non-VA drugs to cover this
| |
| − |
| |
| − | - if not, then we need to develop the CCR to handle inpatient Rx
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |-
| |
| − | |
| |
| − | TE170.306.d.1 – 1.02
| |
| − |
| |
| − | |
| |
| − | We need package experts to review how to do each of these things
| |
| − |
| |
| − | We need to document how to do each of these things
| |
| − |
| |
| − | We need to train the lead tester and backup testers in doing this
| |
| − |
| |
| − | During the test, the lead tester needs to perform these actions
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |
| |
| − | Vendor shall enter Vendor-supplied test data and/or NIST-supplied test data/examples into the patient record based on the data set selected by the Tester from TD170.306.d.1, including
| |
| − |
| |
| − | - Diagnostic test results
| |
| − |
| |
| − | - Problem list
| |
| − |
| |
| − | - Medication list
| |
| − |
| |
| − | - Medication allergy list
| |
| − |
| |
| − | - Procedure list
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |-
| |
| − | |
| |
| − | TE170.306.d.1 – 1.03
| |
| − |
| |
| − | |
| |
| − | need to create UI to generate a CCR for a patient (EWD) (who?)
| |
| − |
| |
| − | - we'll need an EWD team to develop this
| |
| − |
| |
| − | - Rob Tweed, plus others to be determined
| |
| − |
| |
| − | need a CPRS client mod to launch the VISTA Comm EWD app
| |
| − |
| |
| − | - Steve Shreeve
| |
| − |
| |
| − | These are almost the same requirements as for core 7 EP
| |
| − |
| |
| − | - so solving it for one will solve it for both
| |
| − |
| |
| − | - except core 7 EP has the tester running this code during test
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |
| |
| − | Using the Vendor-supplied test data and/or NIST-supplied test data/examples and the EHR function(s) identified by the Vendor, the Tester shall create a copy of the patient’s clinical information on electronic media or other electronic means in the Vendor-selected HL7 CCD format or ASTM CCR format, including
| |
| − |
| |
| − | - Diagnostic test results
| |
| − |
| |
| − | - Problem list
| |
| − |
| |
| − | - Medication list
| |
| − |
| |
| − | - Medication allergy list
| |
| − |
| |
| − | - Procedure list
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |-
| |
| − | |
| |
| − | TE170.306.d.1 – 1.03
| |
| − |
| |
| − | |
| |
| − | We need to confirm whether CCR handles all these data elements
| |
| − |
| |
| − | Develop CCR further to handle any missing elements:
| |
| − |
| |
| − | - Snomed code with allergy type
| |
| − |
| |
| − | - RxNorm code with allergen
| |
| − |
| |
| − | - LOINC code with lab test result
| |
| − |
| |
| − | - possibly inpatient pharmacy data, which would be big development
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |-
| |
| − | |
| |
| − | TE170.306.d.1 – 1.03
| |
| − |
| |
| − | |
| |
| − | Given NIST's preference for CCDs and their choice of an unreliable CCR conformance testing tool, it may be essential for us to finish our CCD development so we can test with a CCD if need be.
| |
| − |
| |
| − | What's left to be done?
| |
| − |
| |
| − | - we need to resolve the reduced list of errors remaining
| |
| − |
| |
| − | - it requires XSLT development talent
| |
| − |
| |
| − | - Ken Miller, Nancy Anthracite, and Dave Mishler can help finish this off
| |
| − |
| |
| − | - there are several other good people we could add
| |
| − |
| |
| − | - if we're willing to pay we can finish this off in time
| |
| − |
| |
| − | - a lot of hacking needs to be done to clean up the details
| |
| − |
| |
| − | - we need to complete the development we already started
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |-
| |
| − | |
| |
| − | TE170.306.d.1 – 1.04
| |
| − |
| |
| − | |
| |
| − | Ensure that our CCR will pass a visual inspection
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |
| |
| − | Using the NIST-supplied Inspection Test Guide, the Tester shall verify that the copy of the patient’s clinical information has been created correctly and without omission
| |
| − |
| |
| − |
| |
| − |
| |
| − | Using the Vendor-supplied test data and/or the NIST-supplied test data/examples in the TD170.306.d.1. data set selected by the Tester, Tester shall verify that all of the patient clinical information data are stored in the patient’s record, including
| |
| − |
| |
| − | - Diagnostic test results
| |
| − |
| |
| − | - Problems
| |
| − |
| |
| − | - Medications
| |
| − |
| |
| − | - Medication allergies
| |
| − |
| |
| − | - Procedures
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |-
| |
| − | |
| |
| − | TE170.306.d.1 – 1.04
| |
| − |
| |
| − | |
| |
| − | We need to test our CCR using the standard American Academy of Family Physicians and the CCR Acceleration Task Force CCR style sheet to confirm we can pass this.
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |
| |
| − | Note that NIST's test suite is silent about this, but it follows from the requirement for CCDs.
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |-
| |
| − | |
| |
| − | TE170.306.d.1 – 1.04
| |
| − |
| |
| − | |
| |
| − | If we develop a CCD, we need to test it using the standard HL7 CCD style sheet to confirm we can pass this.
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |
| |
| − | HL7 CCD style sheet – HL7 provides a style sheet to render HL7 CCD structured documents as part of the CCD specifications package. Contact HL7 directly for the specification package.
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |-
| |
| − | |
| |
| − | TE170.306.d.1 – 1.04
| |
| − |
| |
| − | |
| |
| − | We can estimate our CCR with a CCR validator
| |
| − |
| |
| − | - <nowiki>http://chit.dyndns.org/CCRValidation</nowiki>
| |
| − |
| |
| − | We then need to ensure that our CCR will pass the CCR conformance testing tool
| |
| − |
| |
| − | - NIST has selected a broken Java-based CCR conformance testing tool
| |
| − |
| |
| − | - this endangers the use of a CCR in testing
| |
| − |
| |
| − | - potentially, we could try to make the SourceForge CCR Java validator work
| |
| − |
| |
| − | - we would need someone who knows Java
| |
| − |
| |
| − | - the CCR validator source code is available at SourceForge
| |
| − |
| |
| − | - but it's not actually running successfully anywhere as a validation service
| |
| − |
| |
| − | - we would need to set it up online as a validation service so people can test with it
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |
| |
| − | Using the NIST-supplied conformance testing tool identified in the Conformance Test Tools section of this test procedure, Tester shall verify that the copy of the patient’s clinical information has been created in HL7 CCD format or ASTM CCR format, using the specified vocabularies, and in human readable form correctly and without omission, including
| |
| − |
| |
| − | - Diagnostic test results
| |
| − |
| |
| − | - Problems
| |
| − |
| |
| − | - Medications
| |
| − |
| |
| − | - Medication allergies
| |
| − |
| |
| − | - Procedures
| |
| − |
| |
| − |
| |
| − |
| |
| − | ASTM CCR – Open Health Data provides an ASTM CCR validation tool designed specifically to support this test procedure. The tool is available through the following:
| |
| − |
| |
| − | - Files can be retrieved from the SourceForge site: <nowiki>http://sourceforge.net/projects/ccrvalidator</nowiki>
| |
| − |
| |
| − | - Direct link to the file: <nowiki>http://sourceforge.net/projects/ccrvalidator/files/ValidationService/1.0/ValidationServi</nowiki> <nowiki>ce-1.0.wa</nowiki>r/download
| |
| − |
| |
| − | - Source code location: <nowiki>http://ccrvalidator.svn.sourceforge.net/viewvc/ccrvalidator/branches/</nowiki>
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |-
| |
| − | |
| |
| − | TE170.306.d.1 – 1.04
| |
| − |
| |
| − | |
| |
| − | We can estimate our CCD with a CCD validator
| |
| − |
| |
| − | - <nowiki>https://www.solventus.com/aquifer/ccrviewportcontainer.aspx</nowiki>
| |
| − |
| |
| − | We then need to ensure that our CCD will pass the CCD conformance testing tool
| |
| − |
| |
| − | - NIST has a CCD conformance testing tool
| |
| − |
| |
| − | - it is available now at <nowiki>http://xreg2.nist.gov/cda-validation/index.html</nowiki>
| |
| − |
| |
| − | - practice beforehand to prove our CCD will pass it
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |
| |
| − | HL7 CCD/HITSP C32 – NIST provides an HL7 CCD/HITSP C32 validation tool designed specifically to support this test procedure. The tool is available in two forms:
| |
| − |
| |
| − | - a downloadable package for local installation available at <nowiki>http://xreg2.nist.gov/cda-</nowiki> validation<nowiki>/mu.ht</nowiki>ml
| |
| − |
| |
| − | - a web-accessable validator which is hosted by NIST available at <nowiki>http://xreg2.nist.gov/cda-validation/mu.html</nowiki>
| |
| − |
| |
| − | Support for these tools is available by contacting:
| |
| − |
| |
| − | - Andrew McCaffrey (<nowiki>andrew.mc</nowiki>caffrey@<nowiki>nist.gov</nowiki>)
| |
| − |
| |
| − | - Computer Scientist
| |
| − |
| |
| − | - National Institute of Standards and Technology (NIST)
| |
| − |
| |
| − | - Information Technology Laboratory
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |
| |
| − |
| |
| − |
| |
| − | |}
| |
