03 Appendix H_CHCS Interface Control Document Spreadsheet.pdf
PDF 125 KB Posted
- Attached to
- Teleradiology Federal contract opportunity
- Solicitation number
- HT001520R0063
- Issued by
- Defense Health Agency
About this file
This document outlines requirements for a teleradiology services contract. The contractor shall provide non-personal professional diagnostic radiology services to interpret images and reports for Department of Defense medical facilities worldwide, including the United States, outside the continental United States, and in U.S. territories. Services are needed to support basic radiology needs and on-call coverage throughout the Military Health System. The contractor will use approved secure broadband connections to transmit medical images and data between requiring Defense Health Agency military treatment facilities and the contractor's own facilities. This contract is intended to provide supplementary diagnostic interpretation assistance for military radiologists.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| HT001520R0063 Conformed Solicitaiton through Amendment 0003.pdf | ||
| HT001520R0063 Amendment 0003.pdf | ||
| 01 Questions and Answers Amendment 0002.pdf | ||
| 05 Contractor Employee Mandatory Training.pdf | ||
| 06 DHA Contractor Common Access Card (CAC) Request Process.pdf | ||
| 07 DHA FSO Guide CTR Request.pdf | ||
| 04 Attachment 2 Joint Medical Device Risk Assessment Questionnaire.pdf | ||
| 00 HT001520R0063 Amendment 0002.pdf | ||
| 02 Appendix H_CHCS Interface Control Document.pdf | ||
| 08 DMDC TASS Application.xlsx | XLSX spreadsheet | |
| HT001520R0063 Amendment 0001.pdf | ||
| HT001520R0063 Conformed Solicitation with Amendment 0001.pdf | ||
| HT001520R0063.pdf |
Show all 13
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Capability Stakeholder Requirement - Voice Dictation Interface Primary Text - The system shall establish a bidirectional interface with the voice dictation system system to exchange data with the Cerner RadNet solution.
Requirements The EHR shall provide the capability to receive an Accept Acknowledgement with an Application Error (AE) status from voice dictation system for each incoming HL7 Message that has not been accepted for any reason other than those requiring an Application Reject.
The EHR shall re-transmit the original HL7 message to voice dictation system upon receipt of an Acknowledgment Code-"AA", "AE", or "AR", “CA”, “CR”,” CE”).
The EHR shall have the capability to populate the CE (Diagnostic Serv Sect ID) data type in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the CE (Diagnostic Serv Sect ID) field in the OBR Observation Request Segment sent via HL7 Message, if populated to voice dictation system The EHR shall have the capability to populate the CE (Diagnostic Serv Sect ID) LEN will not exceed 10 characters in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the CE (Enterer’s Location) field in the ORC Common Order Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate the CE (Enterer’s Location) LEN will not exceed 80 characters in the ORC Common Order Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the CE (Entering Device) data type in the ORC Common Order Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the CE (Entering Device) field in the ORC Common Order Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate the CE (Entering Device) LEN will not exceed 60 characters in the ORC Common Order Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the CE (Entering Organization) data type in the ORC Common Order Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the CE (Entering Organization) field in the ORC Common Order Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate the CE (Entering Organization) LEN will not exceed 60 characters in the ORC Common Order Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the CE (Language-Patient) data type in the PID Patient Identification Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the CE (Language-Patient) field in the PID Patient Identification Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate CE (Language-Patient) LEN will not exceed 60 characters in the PID Patient Identification Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the CE (Observation Identifier) data type in the OBX Observation Result Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the CE (Observation Identifier) field in the OBX Observation Result Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate the CE (Reason for Study) data type in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the CE (Reason for Study) field in the OBR Observation Request Segment sent via HL7 Message, if populated to voice dictation system The EHR shall have the capability to populate the CE (Reason for Study) LEN will not exceed 300 characters in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the CE (Universal Service ID) data type in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the CE (Universal Service ID) field in the OBR Observation Request Segment sent via HL7 Message, if populated to voice dictation system The EHR shall have the capability to populate the CE (Universal Service ID) LEN that will not exceed 200 characters in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate CE (Veteran Military Status) data type in the PID Patient Identification Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the CE (Veteran Military Status) field in the PID Patient Identification Segment sent via HL7 Message interface, if populated, to voice dictation system The EHR shall have the capability to populate CE (Veteran Military Status) LEN will not exceed 60 characters in the PID Patient Identification Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate CK (Patient Account Number) data type in the PID Patient Identification Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the CK (Patient Account Number) field in the PID Patient Identification Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate CK (Patient Account Number) Mandatory for Results in the PID Patient Identification Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the CK (Patient ID (External ID)) field in the PID Patient Identification Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate the CM (Alternate Visit ID) data type in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the CM (Alternate Visit ID) field in the PV1 Patient Visit Information Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate the CM (Alternate Visit ID) LEN will not exceed 20 characters in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the CM (Assistant Result Interpreter) data type in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the CM (Assistant Result Interpreter) field in the OBR Observation Request Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate the CM (Assistant Result Interpreter) LEN will not exceed 300 characters in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system
Appendix H_CHCS Interface Control Document.docx Page 1 of 10
Requirements The EHR shall have the capability to populate the CM (Discharged to Location) data type in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the CM (Discharged to Location) field in the PV1 Patient Visit Information Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate the CM (Discharged to Location) LEN will not exceed 25 characters in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dicatation system The EHR shall have the capability to populate CM (Driver’s Lic Num-Patient) data type in the PID Patient Identification Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the CM (Driver’s Lic Num-Patient) field in the PID Patient Identification Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate CM (Driver’s Lic Num-Patient) LEN will not exceed 25 characters in the PID Patient Identification Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the CM (Filler Order Number) data type in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate CM (Filler Order Number) data type in the ORC Common Order Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the CM (Filler Order Number) field in the ORC Common Order Segment sent via HL7 Message interface, if populated, to voice dictation system The EHR shall have the capability to populate CM (Filler Order Number) LEN will not exceed 22 characters in the ORC Common Order Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the CM (Filler Order Number) LEN will not exceed 75 characters in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the CM (Financial Class) data type in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the CM (Financial Class) field in the PV1 Patient Visit Information Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate the CM (Hospital Service) data type in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the CM (Hospital Service) field in the PV1 Patient Visit Information Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate the CM (Hospital Service) LEN will not exceed 3 characters in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the CM (Message Type) data type as a Mandatory field in the MSH Message Header Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the CM (Message Type) data type in the MSH Message Header Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the CM (Message Type) LEN will not exceed 7 characters in the MSH Message Header Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate CM (Placer Group Number) data type in the ORC Common Order Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the CM (Placer Group Number) field in the ORC Common Order Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate the CM (Placer Group Number) LEN will not exceed 22 characters in the ORC Common Order Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the CM (Placer Order Number) data type in the Mandatory field of the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the CM (Placer Order Number) data type in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate CM (Placer Order Number) data type in the ORC Common Order Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the CM (Placer Order Number) field in the ORC Common Order Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate CM (Placer Order Number) LEN will not exceed 22 characters in the ORC Common Order Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the CM (Placer Order Number) LEN will not exceed 75 characters in the OBR Observation Request Segment sent via HL7 Message interface tovoice dictation system
The EHR shall have the capability to populate CM (Placer Order Number) Mandatory for Orders in the ORC Common Order Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the CM (Principal Result Interpreter) as a Mandatory field for Results in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the CM (Principal Result Interpreter) data type in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the CM (Principal Result Interpreter) field in the OBR Observation Request Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate the CM (Principal Result Interpreter) LEN will not exceed 200 characters in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the CM (Quantity/Timing) as a Mandatory field for Orders in the OBR Observation Request Segment sent via HL7 Message to voice dictation system The EHR shall have the capability to populate the CM (Quantity/Timing) data type in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the CM (Quantity/Timing) field in the OBR Observation Request Segment sent via HL7 Message, if populated to voice dictation system The EHR shall have the capability to populate the CM (Quantity/Timing) LEN will not exceed 200 characters in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the CM (Technician) data type in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the CM (Technician) data type in the OBR Observation Request Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate the CM (Transcriptionist) data type in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the CM (Transcriptionist) field in the OBR Observation Request Segment sent via HL7 Message, if populated, to voice dictation system
Appendix H_CHCS Interface Control Document.docx Page 2 of 10
The EHR shall have the capability to populate the CM (Transcriptionist) LEN will not exceed 200 characters in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the CN (Operator ID) field in the EVN Event Type Segment sent via HL7 Message, if populated to voice dictation system The EHR shall have the capability to populate CK (Patient Account Number) LEN will not exceed 20 characters in the PID Patient Identification Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the XCN (Other Healthcare Provider) data type in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the XTN (Phone Number-Home) data type in the PID Patient Identification Segment sent via HL7 Message interface to voice dictation system The EHR shall provide the capability to interface with voice dictation system via Health Level 7 (HL7) message to report transactional information over a TCP/IP based local area network (LAN).
The EHR shall provide the capability to interface an HL7 ORM message via voice dictation system for a Radiology Order to radiology modalities at the performing Facility.
The EHR shall have the capability to populate\the ID (Accept Acknowledgement Type) data type in the MSH Message Header Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ID (Accept Acknowledgement Type) field in the MSH Message Header Segment sent via HL7 Message, if populated to voice dictation system The EHR shall have the capability to populate the ID (Accept Acknowledgement Type) LEN will not exceed 2 characters in the MSH Message Header Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ID (Account Status) data type in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ID (Account Status) field in the PV1 Patient Visit Information Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate the ID (Account Status) LEN will exceed 2 characters in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the ID (Admission Type) data type in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ID (Admission Type) LEN will not exceed 2 characters in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system.
The EHR shall have the capability to populate the ID (Admit Source) data type in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ID (Admit Source) field in the PV1 Patient Visit Information Segment sent via HL7 Message, if populated, voice dictation system The EHR shall have the capability to populate the ID (Admit Source) LEN will not exceed 3 characters in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the ID (Ambulatory Status) data type in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ID (Ambulatory Status) field in the PV1 Patient Visit Information Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate the ID (Ambulatory Status) LEN will not exceed 2 characters in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the ID (Country Code) LEN will not exceed 2 characters in the MSH Message Header Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ID (Courtesy Code) field in the PV1 Patient Visit Information Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate the ID (Courtesy Code) LEN will not exceed 2 characters in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the ID (Diet Type) data type in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ID (Diet Type) field in the PV1 Patient Visit Information Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate the ID (Discharge Disposition) field in the PV1 Patient Visit Information Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate the ID (Discharge Disposition) LEN will not exceed 3 characters in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system.
The EHR shall have the capability to populate the ID (Event Reason of Code) data type in the EVN Event Type Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate ID (Marital Status) data type in the PID Patient Identification Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ID (Marital Status) field in the PID Patient Identification Segment sent via HL7 Message, if populated, voice dictation system The EHR shall have the capability to populate ID (Marital Status) LEN will not exceed 1 character in the PID Patient Identification Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate ID (Order Control) data type in the ORC Common Order Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate ID (Order Control) LEN will not exceed 2 characters in the ORC Common Order Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ID (Order Control) Mandatory field in the ORC Common Order Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ID (Order Status) data type in the ORC Common Order Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ID (Order Status) LEN will not exceed 2 characters in the ORC Common Order Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate ID (Patient Class) data type in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ID (Patient Class) field in the PV1 Patient Visit Information Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate ID (Patient Class) LEN will not exceed 1 character in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ID (Pre-admit Test indicator) data type in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ID (Pre-admit Test indicator) field in the PV1 Patient Visit Information Segment sent via HL7 Message, if populated, to voice dictation system
Appendix H_CHCS Interface Control Document.docx Page 3 of 10
The EHR shall have the capability to populate the ID (Pre-admit Test indicator) LEN will not exceed 2 characters in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ID (Priority) data type in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ID (Priority) field in the OBR Observation Request Segment sent via HL7 Message, if populated to voice dictation system The EHR shall have the capability to populate the ID (Processing ID) data type in the MSH Message Header Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ID (Processing ID) field in the MSH Message Header Segment sent via HL7 Message, if populated to voice dictation system The EHR shall have the capability to populate the ID (Processing ID) LEN will not exceed 1 character in the MSH Message Header Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ID (Race) field in the PID Patient Identification Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate the ID (Readmission Indicator) data type in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ID (Readmission Indicator) field in the PV1 Patient Visit Information Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate the ID (Readmission Indicator) LEN will not exceed 2 characters in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system.
The EHR shall have the capability to populate ID (Religion) data type in the PID Patient Identification Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ID (Religion) field in the PID Patient Identification Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate ID (Religion) LEN will not exceed 3 characters in the PID Patient Identification Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ID (Response Flag) data type in the ORC Common Order Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ID (Response Flag) LEN will not exceed 1 character in the ORC Common Order Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ID (Result Status) data type in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ID (Result Status) LEN will not exceed 1 characters in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the ID (Servicing Facility) data type in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ID (Servicing Facility) field in the PV1 Patient Visit Information Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate the ID (Servicing Facility) LEN will not exceed 2 characters in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the ID (Sex) data type in the PID Patient Identification Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ID (Sex) field in the PID Patient Identification Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate the ID (Source of Comment) data type in the Notes and Comments Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ID (Source of Comment) LEN will not exceed 8 characters in the Notes and Comments Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the ID (Version ID) data type in the MSH Message Header Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ID (Version ID) field in the MSH Message Header Segment sent via HL7 Message, if populated to voice dictation system The EHR shall have the capability to populate the ID (Version ID) LEN will not exceed 8 characters in the MSH Message Header Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ID (Very Important Person Indicator (VIP)) data type in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the ID (Very Important Person Indicator (VIP)) field in the PV1 Patient Visit Information Segment sent via HL7 Message, if populated, to voice dictation system.
The EHR shall have the capability to populate the ID (Very Important Person Indicator (VIP)) LEN will not exceed 2 characters in the PV1 Patient Visit Information Segment sent via HL7 Message to the voice dictation system.
The EHR shall attempt to reconnect to voice dictation system every five (5) seconds for up to 180 seconds (3 minutes) when connection is lost.
The EHR shall have the capability to populate the MRG Merge Patient Information Segment sent via HL7 Message interface to voice dictation system The EHR shall provide the capability to receive an Accept Acknowledgement with an Application Accept (AA) status from voice dictation system for each incoming HL7 Message in which the MSH conforms to MSH as the first segment.
The EHR shall provide the capability to receive an Accept Acknowledgement with an Application Accept (AA) status from voice dictation system for each incoming HL7 Message in which the MSH conforms to a valid Message ID in Message Control ID Field (MSH-10).
The EHR shall provide the capability to receive an Accept Acknowledgement with an Application Accept (AA) status from voice dictation system for each incoming HL7 Message in which the MSH conforms to a valid message type in Message Type Field (MSH-9).
The EHR shall provide the capability to receive an Accept Acknowledgement with an Application Reject (AR) status from voice dictation system for each incoming HL7 Message in which the MSH fails to conform to MSH as the first segment.
The EHR shall provide the capability to receive an Accept Acknowledgement with an Application Reject (AR) status from voice dictation system for each incoming HL7 Message in which the MSH fails to conform to the valid message ID in the Message Control ID Field (MSH-10).
The EHR shall provide the capability to receive an Accept Acknowledgement with an Application Reject (AR) status from voice dictation system for each incoming HL7 Message in which the MSH fails to conform to the valid message type in the Message Type Field (MSH-9).
The EHR shall have the capability to populate the MSH Message Header Segment sent via HL7 Message interface to voice dictation system The EHR shall provide the capability to support a two way DOD X.509 TLS certificates for mutual authentication with voice dictation system when establishing a secure connection.
Appendix H_CHCS Interface Control Document.docx Page 4 of 10
The EHR shall have the capability to populate the NM (Sequence Number) data type in the MSH Message Header Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the NM (Sequence Number) field in the MSH Message Header Segment sent via HL7 Message, if populated to voice dictation system The EHR shall have the capability to populate the NM (Sequence Number) LEN will not exceed 15 characters in the MSH Message Header Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the NM (Visit Number) data type in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the NM (Visit Number) field in the PV1 Patient Visit Information Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate the NM (Visit Number) LEN will not exceed 20 characters in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the NTE Notes and Comments Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the OBX Observation Result Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ORC Common Order sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the PID Patient Identification Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the PL (Assigned Patient Location) data type in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate PL (Assigned Patient Location) LEN will not exceed 80 characters in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the (Response Flag) field in the ORC Common Order Segment sent via HL7 Message interface, if populated, voice dictation system The EHR shall have the capability to populate the CN (Operator ID) data type in the EVN Event Type Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Field Separator) data type in the MSH Message Header Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Sending Facility) data type in the MSH Message Header Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system The EHR shall provide the capability to receive a radiology result from voice dictation system via an HL7 ORU message.
The EHR shall provide the capability to send a radiology order to voice dictation system via an HL7 ORM message.
The EHR shall have the capability to populate the SI (Set ID- Observational Simple) LEN will not exceed 4 characters in the OBX Observation Result Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the SI (Set ID-Notes&Comments) field in the Notes and Comments Segment sent via HL7 Message, if populated to voice dictation system The EHR shall have the capability to populate the SI (Set ID-Notes&Comments) data type in the Notes and Comments Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the SI (Set ID-Notes&Comments) LEN will not exceed 4 characters in the Notes and Comments Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the SI (Set ID-Observation Request) data type in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the SI (Set ID-Observation Request) LEN will not exceed 4 characters in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the SI (Set ID-Patient ID) data type in the PID Patient Identification Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the SI (Set ID-Patient ID) field in the PID Patient Identification Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate the SI (Set ID-Patient ID) LEN will not exceed 4 characters in the PID Patient Identification Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate SI (Set ID-Patient Visit) data type in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the SI (Set ID-Patient Visit) field in the PV1 Patient Visit Information Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate SI (Set ID-Patient Visit) LEN will not exceed 4 characters in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system.
The EHR shall have the capability to populate the ST (Alternate Patient ID) data type in the PID Patient Identification Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Alternate Patient ID) LEN will not exceed 20 characters in the PID Patient Identification Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the ST (Alternate Patient ID) Mandatory in the PID Patient Identification Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Comment) data type as a Mandatory field in the Notes and Comments Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Comment) data type in the Notes and Comments Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Comment) LEN will not exceed 80 characters in the Notes and Comments Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Date/Time of Message) data type as a Mandatory field in the MSH Message Header Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the ST (Date/Time of Message) data type in the MSH Message Header Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Date/Time of Message) LEN will not exceed 26 characters in the MSH Message Header Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the ST (Encoding Characters) data type as a Mandatory field in the MSH Message Header Segment sent via HL7 Message interface to voice dictation system
Appendix H_CHCS Interface Control Document.docx Page 5 of 10
The EHR shall have the capability to populate the ST (Encoding Characters) data type in the MSH Message Header Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Encoding Characters) LEN will not exceed 4 characters in the MSH Message Header Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the ST (Field Separator) data type as a Mandatory field in the MSH Message Header Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Field Separator) LEN will not exceed 1 character in the MSH Message Header Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the ST (Filler Field 1) data type in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Filler Field 1) field in the OBR Observation Request Segment sent via HL7 Message, if populated to voice dictation system The EHR shall have the capability to populate the ST (Filler Field 1) LEN will not exceed 60 characters in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the ST (Filler Field 2) data type in the OBR Observation Request Segment sent via HL7 Message, if populated to voice dictation system The EHR shall have the capability to populate the ST (Filler Field 2) data type in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Filler Field 2) LEN will not exceed 60 characters in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate ST (Message Control ID) data type as a Mandatory field in the MSH Message Header Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Message Control ID) data type in the MSH Message Header Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Message Control ID) LEN will not exceed 20 characters in the MSH Message Header Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the ST (Mothers Maiden Name) data type in the PID Patient Identification Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Mothers Maiden Name) field in the PID Patient Identification Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate ST (Observation Value) data type in the OBX Observation Result Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Observation Value) field in the OBX Observation Result Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate ST (Observation Value) LEN will not exceed 300 characters in the OBX Observation Result Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the ST (Order Callback Phone Number) field in the OBR Observation Request Segment sent via HL7 Message, if populated to voice dictation system The EHR shall have the capability to populate the ST (Order Callback Phone Number) LEN will not exceed 250 characters in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Order Control Code Reason) field in the ORC Common Order Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate the ST (Order Control Code Reason) LEN will not exceed 200 characters in the ORC Common Order Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the ST (Patient ID(Internal ID)) data type in the PID Patient Identification Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Patient ID(Internal ID)) LEN will not exceed 20 characters in the PID Patient Identification Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the ST (Patient ID(Internal ID)) Mandatory field in the PID Patient Identification Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Placer Field 1) data type in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Placer Field 1) field in the OBR Observation Request Segment sent via HL7 Message, if populated to voice dictation system The EHR shall have the capability to populate the ST (Placer Field 1) LEN will not exceed 60 characters in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the ST (Placer Field 2) data type in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Placer Field 2) field in the OBR Observation Request Segment sent via HL7 Message, if populated to voice dictation system The EHR shall have the capability to populate the ST (Placer Field 2) LEN will not exceed 60 characters in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the ST (Pre-admit number) data type in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Pre-admit number) field in the PV1 Patient Visit Information Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate the ST (Pre-admit number) LEN will not exceed 20 characters in the PV1 Patient Visit Information Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the ST (Prior Account Number) data type in the MRG Merge Patient Information Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Prior Account Number) field in the MRG Merge Patient Information Segment sent via HL7 Message, if populated to voice dictation system The EHR shall have the capability to populate the ST (Prior Account Number) LEN that will not exceed 20 characters in the MRG Merge Patient Information Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Prior Alternate Patient ID) data type in the MRG Merge Patient Information Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Prior Alternate Patient ID) field in the MRG Merge Patient Information Segment sent via HL7 Message, if populated to voice dictation system The EHR shall have the capability to populate the ST (Prior Alternate Patient ID) LEN that will not exceed 16 characters in the MRG Merge Patient Information Segment sent via HL7 Message interface to voice dictation system
Appendix H_CHCS Interface Control Document.docx Page 6 of 10
The EHR shall have the capability to populate the ST (Prior Patient ID- External) data type in the MRG Merge Patient Information Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Prior Patient ID- External) field in the MRG Merge Patient Information Segment sent via HL7 Message, if populated to voice dictation system The EHR shall have the capability to populate the ST (Prior Patient ID- External) LEN will not exceed 16 characters in the MRG Merge Patient Information Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Prior Patient ID- Internal) data type as a Mandatory field in the MRG Merge Patient Information Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Prior Patient ID- Internal) data type in the MRG Merge Patient Information Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Prior Patient ID- Internal) LEN that will not exceed 20 characters in the MRG Merge Patient Information Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Receiving Application) data type in the MSH Message Header Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Receiving Application) field in the MSH Message Header Segment sent via HL7 Message, if populated to voice dictation system The EHR shall have the capability to populate the ST (Receiving Application) LEN will not exceed 30 characters in the MSH Message Header Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the ST (Receiving Facility) data type in the MSH Message Header Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Receiving Facility) field in the MSH Message Header Segment sent via HL7 Message, if populated to voice dictation system The EHR shall have the capability to populate the ST (Receiving Facility) LEN will not exceed 30 characters in the MSH Message Header Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the ST (Relevant Clinical Information) data type in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Relevant Clinical Information) field in the OBR Observation Request Segment sent via HL7 Message, if populated to voice dictation system The EHR shall have the capability to populate the ST (Relevant Clinical Information) LEN will not exceed 300 characters in the OBR Observation Request Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate ST (Result Status) data type in the OBX Observation Result Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Result Status) field in the OBX Observation Result Segment sent via HL7 Message, if populated, to voice dictation system The EHR shall have the capability to populate ST (Result Status) LEN will not exceed 1 character in the OBX Observation Result Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Sending Application) data type as Mandatory field in the MSH Message Header Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the capability to populate the ST (Sending Application) data type in the MSH Message Header Segment sent via HL7 Message interface to voice dictation system The EHR shall have the capability to populate the ST (Sending Application) LEN will not exceed 15 characters in the MSH Message Header Segment sent via HL7 Message interface to voice dictation system
The EHR shall have the…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .