Patient Index (MPI) so that VA can expect to receive multiple patient identifiers and assigning authorities or do you have a single entity-level MPI that provides a single unique patient ID? VA has one assigning authority. Two or more Assigning Authorities 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 Other:___________________ 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 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 Does you organization initiate a patient discovery at the time of document Clinical Data Content # Readiness Questionnaire Question Partner Answer
A PDF version of the rendered C62s Upon request, VHIE Health Partner Integration (PI) team will provide it in its welcome packet. If possible, please provide the above with the business questionnaire. If your organization will be sending C62s, please describe the format (HITSP C62, C-CDA C62 with non-XML body and/or structured body, attached PDF or other file types)? VA will send C62s. Our clinical interface is capable of displaying a HITSP C62. C-CDA and attached files may be supported depending on vendor implementation. C62 C-CDA C62 with non-XML body and/or structured body Attached .pdf Other file types, please explain: The VA will perform a technical review of the C62 sample(s) that is(are) provided. The review will cover how your organization’s data displays in the VA’s VistaWeb and JLV viewers and conformance to the HITSP C62-Unstructured Document specification. Will the C62 sample(s) provided by your organization be electronically-generated (vs manually-constructed) from your Exchange solution in your test environment? VA will generate an electronic version. Yes (C62.xml samples electronically-generated) No (C62.xml samples C-CDA (Consolidated Clinical Document Architecture) Check here if NOT APPLICABLE Please indicate which of the following Continuity of Care documents (CCD) you plan to support in production: (Select one or more): VA can send: HITSP C32 V2.5 HITSP C62 C-CDA CCD R1.1 C-CDA CCD R2.1 C-CDA Encounter Summary R2.1 VA can receive: C32 V2.5 C62 HITSP C-32 (Based upon the standards required for Stage 1 Meaningful Use (2011 Edition) Consolidated CDA (C-CDA) Send C-CDA: Yes No If yes, version: r1.1 or r2.1? If no, do you have a planned date: Yes , date: __________ No