Diagnostic Imaging Report (DIR) – Radiology Report (text) CCD Results Section Initially C62, then as C-CDA Discharge Summary CCD Encounters Section Initially C62, then as C-CDA History and Physical (H&P) CCD Encounters Section Initially C62, then as C-CDA Operative Note CCD Procedures Section Initially C62, then as C-CDA Procedure Note CCD Procedures Section Initially C62, then as C-CDA Progress Note CCD Encounters Section Initially C62, then as C-CDA Laboratory Pathology CCD Results Section Initially C62, then as C-CDA Background of Community Health Partner Organization 4.1 Contact Information for Sustainment and Support Activities (Note: Completion of the POC list is needed prior to your go-live date but not required to submit your questionnaire). 4.2 Scope of Community Health Partner Organization # Readiness Questionnaire Question Partner Answer 1. What is the scope of your organization? HIE/HIN Regional HIO
come on board and/or current facilities depart your organization. All of the VA Medical Centers have the capability to exchange over the eHealth Exchange. 8. Are you using or will you be using the Connect Gateway? If yes, what version? If no, what other gateway product are you using? VA is using the 4.2.2.2 Connect Gateway product. Yes, Connect Version: ____________ No, other, please specify name and version: ___________________________________ 9. Please identify the EHR Vendor(s) you are or your affiliated members are VA is using VistA/CPRS throughout its facilities, which it created and is available as an open source under OSHERA (oshera.org) Vendor: Product Name: Version: 10. What would be the expected benefits of a partnership with the VA? VA benefits from eHealth Exchange with partners throughout the country by being able to provide continuity of care to the Veterans we serve. 4.3 Support/Sustainment of Health Information Exchange (HIE) # Readiness Questionnaire Question Partner Answer Is your vendor or development organization tasked to support enhancements and correction of defects during testing and post-go live phases with VHIE? Yes No
in the eHealth Exchange validation environment test UDDI? Yes the VA test environments include all systems/applications involved in the Exchange: VAMCs, VistA Web, MVI (Master Veteran Index), VAP (Veteran Authorizations and Preferences-consent management), Adapter, and Gateway. 2. How many environments will you use (e.g. Dev, Test, Pre-Prod, Prod) Development Environment Testing Environment (VA has 3 environments available for test) Pre-production Environment Production Environment Development Environment Testing Environment (s) Pre-production Environment Production Environment Other, __________________ 3. Can you load test patients in your production environment to support production validation activities and system validation activities? VA has four test patients that have been configured in our production environment that can be utilized for production validation activities. We are unable to load additional test patients into out production environment. Initial production validation: Yes No On-going system validation activities: Yes No 4. Which port do you communicate on? IF the answer is 4437 or 14430, please provide your domain name and IP address for your production servers so VA can create a firewall exception to allow communications. If your endpoints use port 443 then VA does not require a firewall exception. VA receives communications on port 443 and sends outbound communications on port 443, 4437 or 14430. If outbound communication is Yes 443 OR 4437 OR 14430 No If you communicate on 4437 or 14430, please provide the domain name and IP address for your production servers that VA would send queries to your endpoints:
Complete and pass eHealth Exchange Participant Testing with CCHIT Acquire Certificate Enter production OID and endpoints in production UDDI Yes, VA onboarded in 2009 2. Have you signed the Data Use and Reciprocal Support Agreement (DURSA)? If not, when is that scheduled to occur? Yes, VA signed the DURSA in 2009. Yes No (Not yet signed) Expected DURSA signing: 3. Which version of the specifications have you or will you certify your HIE on? VA is certified on the 2010 and 2011 specifications. 2010 2011 Both 4. If you are certifying or will certify on 2010 specifications, when do you plan on upgrading to 2011 specifications? VA is certified on the 2011 specifications. Date upgrade planned: 5. Does your organization own your OIDs? If not, who owns it? Yes, the VA owns its OIDs. Yes No If no, who: 6. Has your organization registered your OIDS/endpoints in the eHealth Exchange Test UDDI (this references the validation UDDI; not the DIL environment UDDI) and Production UDDI? Yes, VA has registered its OIDs and end points in the eHealth Exchange UDDI and Production UDDI Registered in eHealth Exchange Validation Test UDDI? Yes No Registered in eHealth Exchange Production UDDI? Yes No
VA initiates a patient discovery message to all partners on the eHealth Exchange at the time of consenting/authorizing or when needing to discover where the patient has been treated. 9. Will your organization persist the VA identifier and use it for future queries or will you initiate a patient discovery every time you do a document query? VA persists the patient’s identifier, after the patient discovery, and uses it for subsequent queries. Will persist the VA identifier and use it for future queries Yes - how long? _________ No Will initiate a patient discovery every time a document query is done Yes No ______________________________ 10. Can you include the below noted values in your LivingSubjectID field? VA’s identity management systems require that a correlation be stored in our Master Patient Index (MPI) to be able to release data to a partner. If your system does not provide a patient unique ID and assigning authority in your LivingSubjectID field when sending a patient discovery message to VA, your subsequent document query and document retrieve requests would fail our policy check. Yes, our patient discovery includes a LivingSubjectID with unique patient ID and assigning authority No, we would have to modify our system to support this request 11. Do you ever use the MatchCriterion tag for any request or response? The use of the MatchCriterion tag causes patient discoveries to fail. Therefore, please do not use any MatchCriterion tags for any request or response. Yes No
eHealth Exchange, provides a framework of trust assurance to support health information exchange across the eHealth Exchange. Health Care Network A Health Care Network is a generic term for a health organization made up of one or more hospitals, clinics, pharmacies, labs, et al, that are related under the same management and financial structure. Health Information/Health Data/Clinical Data Sources: eHealth Exchange Architectural Overview () Refers to all information associated with a patient over time. The information can contain health assessments (physical health, mental health, substance abuse, etc.), diagnosis, problems, progress notes, medications (prescription and over-the-counter), alerts, laboratory test results, demographics and any information relevant to the treatment of a patient. Health Information Exchange (HIE) Source: HealthIT.gov Verb: The electronic sharing of health-related information among organizations. Also referred in this questionnaire as health data exchange. Noun: For the purpose of this questionnaire, an HIE refers to a Health Information Organization whose purpose and scope is to facilitate health information exchange electronically across multiple organizations. Health Information Organization (HIO) Sources: HealthIT.gov, eHealth Exchange Architectural Overview () An organization that provides services to enable the electronic sharing of health-related information. The scope of an HIO may range from a single provider practice, to large chains or delivery networks, existing jurisdictional HIEs/RHIOs, and state or county agencies. Participant (HIE/HIO Participant) An organization that is a direct stakeholder of a Health Information Organization by sending and/or receiving data via the Health Information Exchange. For the purposes of this questionnaire participants are delineated by data source where each distinct provider of data is considered a participant. (I.e. several hospitals/practices/providers may all participate in one data stream with the HIE.) Probabilistic Matching Algorithm Probabilistic patient matching algorithms allow for a statistical variability in the matching of patient identity traits which allow for greater chance of matching on data fields that are likely to