version 3.8.0 - Download Excel Version

Summary

Bridge Message Type Description HL7 Message Type Supported HL7 Trigger Events
patient.ADT.patient-merge patient MRN merge ADT A18, A40
patient.ADT.demographic-update patient demographic update ADT A08, A28, A31
patient.ADT.event patient event ADT A01, A02, A03, A04, A05, A06, A07, A09, A10, A11, A12, A13, A14, A15, A16, A17, A20, A25, A26, A27, A38
radiology.ORM create/update radiology exam ORM O01
radiology.ORU create/update exam and add radiology report ORU R01
order.SIU create/update radiology order (similar to ORM without an accession number) SIU S12, S13, S14, S15

Definitions

Specification Field Definition
Bridge Element Bridge message key
Typical HL7 Field Most common location in HL7
HL7 Repeating? Does this field typically contain repeating values?
Mandatory? Is this field mandatory for application functionality?
Required? Is this field required for a message to be accepted?
Description Detailed description of semantic meaning
Aliases Common industry synonyms

Supported Messages

patient.ADT.patient-merge

Bridge Element Typical HL7 Field HL7 Repeating? Mandatory? Required? Description Aliases
ca_operator_id EVN.5.1 No No No the unique identifier of the user who made the update Operator, Patient Event Update User, ADT User, Claim Processor, Billing Editor
ca_operator_person_name EVN.5.2 No No No the name of the employee for the associated identifier key (only applied if a new employee is created)
message_event_time MSH.7.1 No Yes Yes message_event_time Message Event Time
patient_dob PID.7.1 No Yes No patient date of birth Patient DOB
patient_empi PID.2.1 No No No similar to patient_mrn, but sets the boolean EMPI value to indicate this MRN is an EMPI identifier Patient EMPI, Master Patient MRN, Master Patient ID, Global Patient ID, Global MRN
patient_gender PID.8 No Yes No patient gender Patient Gender
patient_location PV1.3.1 No Yes No physical location of patient, refers to location as of time of message Patient Location, Unit, Ward
patient_location_bed PV1.3.3 No No No specific bed number under a location Patient Location Bed, Bed Number
patient_location_name PV1.3.9 No No No human name of patient location Patient Location Human Name, Patient Location Description
patient_location_room PV1.3.2 No No No specific room number under a location Patient Location Room, Room Number
patient_mrn PID.3.1 Yes Yes Yes unique identifier for a patient within a given external system and metasite Patient MRN, Patient ID
patient_mrn_* PID.3.1 Yes No No same as patient_mrn, but the wildcard allows multiple MRN in a single message to be associated with the same patient. The wildcard is an integer >=1 which associates the external system and metasites of the other MRN providers Patient MRN, Patient ID
patient_name PID.5 No Yes No patient name Patient Name
patient_type PV1.2 No Yes No Inpatient or Outpatient, per CMS Patient Type, Hospital Status, Patient Status
previous_patient_mrn MRG.1.1 No No Yes same as patient_mrn, but used in a merge to designate the MRN being consumed / destroyed Previous MRN, Old MRN, Duplicate MRN
site MSH.6 No Yes No a specific geographic boundary, usually a building or facility Site, Hospital Name, Facility Code
site_class PV1.18 No Yes No type of patient (ED, Trauma, outpatient, inpatient, etc.) Site Class, Patient Type, Patient Class, Visit Type, Encounter Type, Admission Type
visit_number PV1.19.1 No Yes No parent of Orders, links series of orders and events to a single admission or encounter Visit Number, Encounter ID, Admission ID, Account Number

patient.ADT.demographic-update

Bridge Element Typical HL7 Field HL7 Repeating? Mandatory? Required? Description Aliases
ca_operator_id EVN.5.1 No No No the unique identifier of the user who made the update Operator, Patient Event Update User, ADT User, Claim Processor, Billing Editor
ca_operator_person_name EVN.5.2 No No No the name of the employee for the associated identifier key (only applied if a new employee is created)
icd_code_* DG1.3.1 No No No One or more ICD codes associated with the event (a visit or charge). The wildcard is an integer starting with 1 and incrementing sequentially per association event. ICD Code, Diagnosis Code
message_event_time MSH.7.1 No Yes Yes message_event_time Message Event Time
patient_dob PID.7.1 No Yes No patient date of birth Patient DOB
patient_empi PID.2.1 No No No similar to patient_mrn, but sets the boolean EMPI value to indicate this MRN is an EMPI identifier Patient EMPI, Master Patient MRN, Master Patient ID, Global Patient ID, Global MRN
patient_gender PID.8 No Yes No patient gender Patient Gender
patient_location PV1.3.1 No Yes No physical location of patient, refers to location as of time of message Patient Location, Unit, Ward
patient_location_bed PV1.3.3 No No No specific bed number under a location Patient Location Bed, Bed Number
patient_location_name PV1.3.9 No No No human name of patient location Patient Location Human Name, Patient Location Description
patient_location_room PV1.3.2 No No No specific room number under a location Patient Location Room, Room Number
patient_mrn PID.3.1 Yes Yes Yes unique identifier for a patient within a given external system and metasite Patient MRN, Patient ID
patient_mrn_* PID.3.1 Yes No No same as patient_mrn, but the wildcard allows multiple MRN in a single message to be associated with the same patient. The wildcard is an integer >=1 which associates the external system and metasites of the other MRN providers Patient MRN, Patient ID
patient_name PID.5 No Yes No patient name Patient Name
patient_type PV1.2 No Yes No Inpatient or Outpatient, per CMS Patient Type, Hospital Status, Patient Status
site MSH.6 No Yes No a specific geographic boundary, usually a building or facility Site, Hospital Name, Facility Code
site_class PV1.18 No Yes No type of patient (ED, Trauma, outpatient, inpatient, etc.) Site Class, Patient Type, Patient Class, Visit Type, Encounter Type, Admission Type
visit_number PV1.19.1 No Yes No parent of Orders, links series of orders and events to a single admission or encounter Visit Number, Encounter ID, Admission ID, Account Number

patient.ADT.event

Bridge Element Typical HL7 Field HL7 Repeating? Mandatory? Required? Description Aliases
ca_operator_id EVN.5.1 No No No the unique identifier of the user who made the update Operator, Patient Event Update User, ADT User, Claim Processor, Billing Editor
ca_operator_person_name EVN.5.2 No No No the name of the employee for the associated identifier key (only applied if a new employee is created)
icd_code_* DG1.3.1 No No No One or more ICD codes associated with the event (a visit or charge). The wildcard is an integer starting with 1 and incrementing sequentially per association event. ICD Code, Diagnosis Code
message_event_time MSH.7.1 No Yes Yes message_event_time Message Event Time
patient_dob PID.7.1 No Yes No patient date of birth Patient DOB
patient_empi PID.2.1 No No No similar to patient_mrn, but sets the boolean EMPI value to indicate this MRN is an EMPI identifier Patient EMPI, Master Patient MRN, Master Patient ID, Global Patient ID, Global MRN
patient_event_reason EVN.4.1 No No No reason from a list explaining the patient event Patient Event Reason, ADT Reason
patient_event_time EVN.2 No Yes No time when a patient event happened Patient Event Time, ADT Event
patient_event_type MSH.9.2 No Yes Yes type of event updating patient information Patient Event Type, ADT Action
patient_gender PID.8 No Yes No patient gender Patient Gender
patient_location PV1.3.1 No Yes No physical location of patient, refers to location as of time of message Patient Location, Unit, Ward
patient_location_bed PV1.3.3 No No No specific bed number under a location Patient Location Bed, Bed Number
patient_location_name PV1.3.9 No No No human name of patient location Patient Location Human Name, Patient Location Description
patient_location_room PV1.3.2 No No No specific room number under a location Patient Location Room, Room Number
patient_mrn PID.3.1 Yes Yes Yes unique identifier for a patient within a given external system and metasite Patient MRN, Patient ID
patient_mrn_* PID.3.1 Yes No No same as patient_mrn, but the wildcard allows multiple MRN in a single message to be associated with the same patient. The wildcard is an integer >=1 which associates the external system and metasites of the other MRN providers Patient MRN, Patient ID
patient_name PID.5 No Yes No patient name Patient Name
patient_type PV1.2 No Yes No Inpatient or Outpatient, per CMS Patient Type, Hospital Status, Patient Status
site MSH.6 No Yes No a specific geographic boundary, usually a building or facility Site, Hospital Name, Facility Code
site_class PV1.18 No Yes No type of patient (ED, Trauma, outpatient, inpatient, etc.) Site Class, Patient Type, Patient Class, Visit Type, Encounter Type, Admission Type
visit_number PV1.19.1 No Yes No parent of Orders, links series of orders and events to a single admission or encounter Visit Number, Encounter ID, Admission ID, Account Number

radiology.ORM

Bridge Element Typical HL7 Field HL7 Repeating? Mandatory? Required? Description Aliases
accession_number ORC.3.1 No Yes Yes exam unique identifier, child of Order Accession Number, Study ID
appointment_time OBR.36 No Yes No the time the exam is scheduled to occur Scheduled, Appointment
begin_exam_event_time OBR.22 No No No the time begin exam status was set Begin Exam Event
begin_exam_time ORC.7.4 No Yes No the time the tech started the exam Begin Exam, Start Exam, In-progress
ca_attending_id PV1.7.1 No No No the unique identifier of the admitting or attending provider of the patient (not necessarily the ordering or authorizing) Attending Provider, Admitting Provider
ca_attending_person_name PV1.7.2-5 No No No the name of the employee for the associated identifier key (only applied if a new employee is created)
ca_authorizing_id OBR.16.1 No No No the unique identifier of the provider who authorized the order (not necessarily attending or ordering) Authorizing Provider, Approving Provider
ca_authorizing_person_name OBR.16.2-5 No No No the name of the employee for the associated identifier key (only applied if a new employee is created)
ca_check_in_user_id ORC.10.1 No No No the unique identifier of the user who registered the patient Check-in User, Front Desk, Registrar
ca_check_in_user_person_name ORC.10.2-5 No No No the name of the employee for the associated identifier key (only applied if a new employee is created)
ca_ordering_id ORC.12.1 No Yes No the unique identifier of the provider who ordered the exam (not necessarily attending or authorizing) Ordering Provider, Requesting Provider, Referring Provider
ca_ordering_person_name ORC.12.2-5 No No No the name of the employee for the associated identifier key (only applied if a new employee is created)
ca_scheduler_id ORC.10.1 No No No the unique identifier of the user who scheduled the exam Scheduler, Registrar
ca_scheduler_person_name ORC.10.2-5 No No No the name of the employee for the associated identifier key (only applied if a new employee is created)
ca_sign_in_user_id ORC.10.1 No No No the unique identifier of the user who arrived the patient Sign-in User, Front Desk, Registrar
ca_sign_in_user_person_name ORC.10.2-5 No No No the name of the employee for the associated identifier key (only applied if a new employee is created)
ca_technologist_id OBR.34.1 No Yes No the unique identifier of the technologist who performed the exam Technologist, Performing Technologist, Exam Staff
ca_technologist_person_name OBR.34.2-5 No No No the name of the employee for the associated identifier key (only applied if a new employee is created)
check_in_time PV1.44 No Yes No when a patient has completed registration / sign-in Check-in, End Registration, Arrival, Ready for Exam
diagnosis OBR.31 No No No free text explanation of why a procedure was ordered Reason for Exam, History, Diagnosis
end_exam_event_time ORC.9.1 No No No the time the end exam status was set End Exam Event
end_exam_time OBR.7.1 No Yes No the time the tech ended the exam End Exam, Completed, Taken, Performed
exam_priority OBR.27.6 No No No priority of exam Priority, Urgency
exam_resource OBR.19.1 No Yes No unique identifier of scanner used for exam Resource, Modality, Scanner, Device
exam_resource_name OBR.19.2 No No No human name of a scanner Human Modality Name, Human Scanner Name, Human Device Name, Resource Description
exam_status OBR.25 No Yes Yes current status of an exam or report Exam Status, Report Status
hcpcs_code_* OBR.44 Yes No No One or more HCPCS codes associated with the procedure code for the exam. The wildcard is an integer >= 1 (depending on the cardinality of procedure-HCPCS mappings) HCPCS Code, CPT Code
icd_code_* DG1.3.1 No No No One or more ICD codes associated with the event (a visit or charge). The wildcard is an integer starting with 1 and incrementing sequentially per association event. ICD Code, Diagnosis Code
master_order_number ORC.4.1 No No No Master/parent order number, used to associate child orders. Master Order Number, Primary Order Number, Parent Order Number
message_event_time MSH.7.1 No Yes Yes message_event_time Message Event Time
modality OBR.24 No Yes No type of modality used for a scan Modality, Modality Type, Device Type, Scanner Type
order_arrival_time OBR.27.4 No Yes No the time an order arrives in the filling system Order Arrival, Order Placed, Order Created
order_comments OBR.13 No No No free text comments about the exam or patient, usually entered after the procedure is completed Order Comments, Technologist Comments, Exam Comments, Procedure Comments
order_number OBR.2.1 No Yes No child of Visit, links one or more exams, can also be linked by a Master Order Number Order Number
patient_dob PID.7.1 No Yes No patient date of birth Patient DOB
patient_empi PID.2.1 No No No similar to patient_mrn, but sets the boolean EMPI value to indicate this MRN is an EMPI identifier Patient EMPI, Master Patient MRN, Master Patient ID, Global Patient ID, Global MRN
patient_gender PID.8 No Yes No patient gender Patient Gender
patient_location PV1.3.1 No Yes No physical location of patient, refers to location as of time of message Patient Location, Unit, Ward
patient_location_bed PV1.3.3 No No No specific bed number under a location Patient Location Bed, Bed Number
patient_location_name PV1.3.9 No No No human name of patient location Patient Location Human Name, Patient Location Description
patient_location_room PV1.3.2 No No No specific room number under a location Patient Location Room, Room Number
patient_mrn PID.3.1 Yes Yes Yes unique identifier for a patient within a given external system and metasite Patient MRN, Patient ID
patient_mrn_* PID.3.1 Yes No No same as patient_mrn, but the wildcard allows multiple MRN in a single message to be associated with the same patient. The wildcard is an integer >=1 which associates the external system and metasites of the other MRN providers Patient MRN, Patient ID
patient_name PID.5 No Yes No patient name Patient Name
patient_type PV1.2 No Yes No Inpatient or Outpatient, per CMS Patient Type, Hospital Status, Patient Status
procedure_code OBR.4.1 No Yes No unique identifier for type of exam Procedure Code, Exam Code, Order Code, Exam Type, Orderable, Item
procedure_description OBR.4.2 No No No human description of procedure Procedure Description, Exam Description, Order Description, Item Description
procedure_modifier OBR.45.1 No No No additional procedure details (e.g. foreign body screening, laterality, etc.) Procedure Modifier, Exam Modifier, Modifier
rad_exam_dept ORC.13.9 No Yes No department within radiology performing the service, often modality- or location-oriented Radiology Department, Service, Modality, Unit, Specialty
reschedule_event_time OBR.27.4 No No No when the exam appointment was rescheduled Reschedule Event, Appointment Reschedule
schedule_event_time OBR.27.4 No Yes No the time when exam was scheduled from the order Schedule Event, Appointment Created
sign_in_time PV1.44 No Yes No when the patient first arrives for an exam Sign-in, Arrival
site MSH.6 No Yes Yes a specific geographic boundary, usually a building or facility Site, Hospital Name, Facility Code
site_class PV1.18 No Yes No type of patient (ED, Trauma, outpatient, inpatient, etc.) Site Class, Patient Type, Patient Class, Visit Type, Encounter Type, Admission Type
visit_number PV1.19.1 No Yes No parent of Orders, links series of orders and events to a single admission or encounter Visit Number, Encounter ID, Admission ID, Account Number

radiology.ORU

Bridge Element Typical HL7 Field HL7 Repeating? Mandatory? Required? Description Aliases
accession_number ORC.3.1 No Yes Yes exam unique identifier, child of Order Accession Number, Study ID
appointment_time OBR.36 No Yes No the time the exam is scheduled to occur Scheduled, Appointment
begin_exam_event_time OBR.22 No No No the time begin exam status was set Begin Exam Event
begin_exam_time ORC.7.4 No Yes No the time the tech started the exam Begin Exam, Start Exam, In-progress
ca_attending_id PV1.7.1 No No No the unique identifier of the admitting or attending provider of the patient (not necessarily the ordering or authorizing) Attending Provider, Admitting Provider
ca_attending_person_name PV1.7.2-5 No No No the name of the employee for the associated identifier key (only applied if a new employee is created)
ca_authorizing_id OBR.16.1 No No No the unique identifier of the provider who authorized the order (not necessarily attending or ordering) Authorizing Provider, Approving Provider
ca_authorizing_person_name OBR.16.2-5 No No No the name of the employee for the associated identifier key (only applied if a new employee is created)
ca_check_in_user_id ORC.10.1 No No No the unique identifier of the user who registered the patient Check-in User, Front Desk, Registrar
ca_check_in_user_person_name ORC.10.2-5 No No No the name of the employee for the associated identifier key (only applied if a new employee is created)
ca_ordering_id ORC.12.1 No Yes No the unique identifier of the provider who ordered the exam (not necessarily attending or authorizing) Ordering Provider, Requesting Provider, Referring Provider
ca_ordering_person_name ORC.12.2-5 No No No the name of the employee for the associated identifier key (only applied if a new employee is created)
ca_radiologist1_id OBR.32.1 No Yes No the unique identifier of the user who signed the report Signing Radiologist, Primary Radiologist, Attending Radiologist
ca_radiologist1_person_name OBR.32.2-5 No No No the name of the employee for the associated identifier key (only applied if a new employee is created)
ca_radiologist2_id OBR.33.1 Yes Yes No the unique identifier of the user who assisted with the report Secondary Radiologist, Assisting Radiologist, Resident
ca_radiologist2_person_name OBR.33.2-5 Yes No No the name of the employee for the associated identifier key (only applied if a new employee is created)
ca_scheduler_id ORC.10.1 No No No the unique identifier of the user who scheduled the exam Scheduler, Registrar
ca_scheduler_person_name ORC.10.2-5 No No No the name of the employee for the associated identifier key (only applied if a new employee is created)
ca_sign_in_user_id ORC.10.1 No No No the unique identifier of the user who arrived the patient Sign-in User, Front Desk, Registrar
ca_sign_in_user_person_name ORC.10.2-5 No No No the name of the employee for the associated identifier key (only applied if a new employee is created)
ca_technologist_id OBR.34.1 No Yes No the unique identifier of the technologist who performed the exam Technologist, Performing Technologist, Exam Staff
ca_technologist_person_name OBR.34.2-5 No No No the name of the employee for the associated identifier key (only applied if a new employee is created)
ca_transcriptionist_id OBR.35.1 No No No the unique identifier of the transcriptionist who transcribed the report revision Transcriptionist, Correctionist, Editor
ca_transcriptionist_person_name OBR.35.2-5 No No No the name of the employee for the associated identifier key (only applied if a new employee is created)
check_in_time PV1.44 No Yes No when a patient has completed registration / sign-in Check-in, End Registration, Arrival, Ready for Exam
diagnosis OBR.31 No No No free text explanation of why a procedure was ordered Reason for Exam, History, Diagnosis
end_exam_event_time ORC.9.1 No No No the time the end exam status was set End Exam Event
end_exam_time OBR.7.1 No Yes No the time the tech ended the exam End Exam, Completed, Taken, Performed
exam_priority OBR.27.6 No No No priority of exam Priority, Urgency
exam_resource OBR.19.1 No Yes No unique identifier of scanner used for exam Resource, Modality, Scanner, Device
exam_resource_name OBR.19.2 No No No human name of a scanner Human Modality Name, Human Scanner Name, Human Device Name, Resource Description
exam_status OBR.25 No Yes Yes current status of an exam or report Exam Status, Report Status
hcpcs_code_* OBR.44 Yes No No One or more HCPCS codes associated with the procedure code for the exam. The wildcard is an integer >= 1 (depending on the cardinality of procedure-HCPCS mappings) HCPCS Code, CPT Code
icd_code_* DG1.3.1 No No No One or more ICD codes associated with the event (a visit or charge). The wildcard is an integer starting with 1 and incrementing sequentially per association event. ICD Code, Diagnosis Code
master_order_number ORC.4.1 No No No Master/parent order number, used to associate child orders. Master Order Number, Primary Order Number, Parent Order Number
message_event_time MSH.7.1 No Yes Yes message_event_time Message Event Time
modality OBR.24 No Yes No type of modality used for a scan Modality, Modality Type, Device Type, Scanner Type
order_arrival_time OBR.27.4 No Yes No the time an order arrives in the filling system Order Arrival, Order Placed, Order Created
order_comments OBR.13 No No No free text comments about the exam or patient, usually entered after the procedure is completed Order Comments, Technologist Comments, Exam Comments, Procedure Comments
order_number OBR.2.1 No Yes No child of Visit, links one or more exams, can also be linked by a Master Order Number Order Number
patient_dob PID.7.1 No Yes No patient date of birth Patient DOB
patient_empi PID.2.1 No No No similar to patient_mrn, but sets the boolean EMPI value to indicate this MRN is an EMPI identifier Patient EMPI, Master Patient MRN, Master Patient ID, Global Patient ID, Global MRN
patient_gender PID.8 No Yes No patient gender Patient Gender
patient_location PV1.3.1 No Yes No physical location of patient, refers to location as of time of message Patient Location, Unit, Ward
patient_location_bed PV1.3.3 No No No specific bed number under a location Patient Location Bed, Bed Number
patient_location_name PV1.3.9 No No No human name of patient location Patient Location Human Name, Patient Location Description
patient_location_room PV1.3.2 No No No specific room number under a location Patient Location Room, Room Number
patient_mrn PID.3.1 Yes Yes Yes unique identifier for a patient within a given external system and metasite Patient MRN, Patient ID
patient_mrn_* PID.3.1 Yes No No same as patient_mrn, but the wildcard allows multiple MRN in a single message to be associated with the same patient. The wildcard is an integer >=1 which associates the external system and metasites of the other MRN providers Patient MRN, Patient ID
patient_name PID.5 No Yes No patient name Patient Name
patient_type PV1.2 No Yes No Inpatient or Outpatient, per CMS Patient Type, Hospital Status, Patient Status
procedure_code OBR.4.1 No Yes No unique identifier for type of exam Procedure Code, Exam Code, Order Code, Exam Type, Orderable, Item
procedure_description OBR.4.2 No No No human description of procedure Procedure Description, Exam Description, Order Description, Item Description
procedure_modifier OBR.45.1 No No No additional procedure details (e.g. foreign body screening, laterality, etc.) Procedure Modifier, Exam Modifier, Modifier
rad_exam_dept ORC.13.9 No Yes No department within radiology performing the service, often modality- or location-oriented Radiology Department, Service, Modality, Unit, Specialty
report_body OBX.5 Yes Yes No free text report results Report Body, Report Text, Result, Dictation
report_event_time OBR.22 No Yes No the time a result was signed/drafted/transcribed Report Event, Signing Time, Edit Time, Last Updated, Draft Time
report_impression OBX.5 Yes Yes No impression/most import subsection of the report text Impression, Opinion, Findings
reschedule_event_time OBR.27.4 No No No when the exam appointment was rescheduled Reschedule Event, Appointment Reschedule
schedule_event_time OBR.27.4 No Yes No the time when exam was scheduled from the order Schedule Event, Appointment Created
sign_in_time PV1.44 No Yes No when the patient first arrives for an exam Sign-in, Arrival
site MSH.6 No Yes Yes a specific geographic boundary, usually a building or facility Site, Hospital Name, Facility Code
site_class PV1.18 No Yes No type of patient (ED, Trauma, outpatient, inpatient, etc.) Site Class, Patient Type, Patient Class, Visit Type, Encounter Type, Admission Type
visit_number PV1.19.1 No Yes No parent of Orders, links series of orders and events to a single admission or encounter Visit Number, Encounter ID, Admission ID, Account Number

order.SIU

Bridge Element Typical HL7 Field HL7 Repeating? Mandatory? Required? Description Aliases
appointment_time OBR.36 No Yes No the time the exam is scheduled to occur Scheduled, Appointment
ca_ordering_id ORC.12.1 No Yes No the unique identifier of the provider who ordered the exam (not necessarily attending or authorizing) Ordering Provider, Requesting Provider, Referring Provider
ca_ordering_person_name ORC.12.2-5 No No No the name of the employee for the associated identifier key (only applied if a new employee is created)
exam_priority OBR.27.6 No No No priority of exam Priority, Urgency
exam_resource OBR.19.1 No Yes No unique identifier of scanner used for exam Resource, Modality, Scanner, Device
exam_resource_name OBR.19.2 No No No human name of a scanner Human Modality Name, Human Scanner Name, Human Device Name, Resource Description
hcpcs_code_* OBR.44 Yes No No One or more HCPCS codes associated with the procedure code for the exam. The wildcard is an integer >= 1 (depending on the cardinality of procedure-HCPCS mappings) HCPCS Code, CPT Code
icd_code_* DG1.3.1 No No No One or more ICD codes associated with the event (a visit or charge). The wildcard is an integer starting with 1 and incrementing sequentially per association event. ICD Code, Diagnosis Code
master_order_number ORC.4.1 No No No Master/parent order number, used to associate child orders. Master Order Number, Primary Order Number, Parent Order Number
message_event_time MSH.7.1 No Yes Yes message_event_time Message Event Time
modality OBR.24 No Yes No type of modality used for a scan Modality, Modality Type, Device Type, Scanner Type
order_arrival_time OBR.27.4 No Yes No the time an order arrives in the filling system Order Arrival, Order Placed, Order Created
order_comments OBR.13 No No No free text comments about the exam or patient, usually entered after the procedure is completed Order Comments, Technologist Comments, Exam Comments, Procedure Comments
order_number OBR.2.1 No Yes Yes child of Visit, links one or more exams, can also be linked by a Master Order Number Order Number
order_status MSH.9.2 No Yes Yes current status of an order Order Status
patient_dob PID.7.1 No Yes No patient date of birth Patient DOB
patient_empi PID.2.1 No No No similar to patient_mrn, but sets the boolean EMPI value to indicate this MRN is an EMPI identifier Patient EMPI, Master Patient MRN, Master Patient ID, Global Patient ID, Global MRN
patient_gender PID.8 No Yes No patient gender Patient Gender
patient_mrn PID.3.1 Yes Yes Yes unique identifier for a patient within a given external system and metasite Patient MRN, Patient ID
patient_mrn_* PID.3.1 Yes No No same as patient_mrn, but the wildcard allows multiple MRN in a single message to be associated with the same patient. The wildcard is an integer >=1 which associates the external system and metasites of the other MRN providers Patient MRN, Patient ID
patient_name PID.5 No Yes No patient name Patient Name
patient_type PV1.2 No Yes No Inpatient or Outpatient, per CMS Patient Type, Hospital Status, Patient Status
procedure_code OBR.4.1 No Yes No unique identifier for type of exam Procedure Code, Exam Code, Order Code, Exam Type, Orderable, Item
procedure_description OBR.4.2 No No No human description of procedure Procedure Description, Exam Description, Order Description, Item Description
site MSH.6 No Yes Yes a specific geographic boundary, usually a building or facility Site, Hospital Name, Facility Code
site_class PV1.18 No Yes No type of patient (ED, Trauma, outpatient, inpatient, etc.) Site Class, Patient Type, Patient Class, Visit Type, Encounter Type, Admission Type
visit_number PV1.19.1 No Yes Yes parent of Orders, links series of orders and events to a single admission or encounter Visit Number, Encounter ID, Admission ID, Account Number