HL7 Specifications refer to a set of international standards for the exchange, integration, sharing, and retrieval of electronic health information. These standards are crucial for enabling different healthcare systems and applications to communicate effectively with one another.

HL7 Specifications

The HL7 Specifications are here. This is simply a guideline that outlines common configurations we use.

Results

Our system automatically adapts to match your HL7 results. We recommend using a results message format similar to the one you've used in a recent interface project. However, there are a few exceptions:

• If you include an embedded PDF, the base64 content should be sent in a single segment (typically seen in an OBX ED or specialized Z segment). The content should not be broken into multiple segments due to character limits.
• We do not accept NTEs between ORC and OBR segments. Instead, NTEs at the ORC level should be moved to the OBR level.

Orders

For orders, our default (preferred) HL7 message format is outlined in our specifications.

Adjustment to the order message spec:

Adjustments to the default format can be made if necessary. Here are some common adjustments:

• By default, AOEs are sent in OBX segments, but they can be changed to NTEs if needed.
• By default, the IN1 segment is always included, even for patient and client bill types. However, it can be suppressed for Patient/Client bill types if desired. In this case, the default bill code will be sent in a different segment (see comments on default bill codes below).
• By default, the PV1 segment is suppressed, but it can be added if necessary. There's no additional data added, just a rearrangement of data if PV1 is needed in addition to PID.
• Six types of insurances are sent: Client (Account), Patient, Medicare, Medicaid, Private Insurance, and HMOs. Medicare, Medicaid, Private Insurance, and HMOs are grouped as 'Third Party' Insurance. See the mapping below for more clarity.
• Sometimes LIS/LIMS require default insurance codes in the IN1 segment when Client (Account) or Patient bill types are sent, or when third-party insurance is sent without a code. If this applies to your situation, please refer to the default insurance code mapping below. These codes can be adjusted as needed.

HL7 order message field mappings:

Any HL7 mappings can be adjusted as needed. The default mappings are below:

Gender:

• Male: M
• Female: F
• Unknown: U

Insurance Type (normally IN1.47.1)

• Client/Account: C
• Patient: P
• Medicare: T
• Medicaid: T
• Private Insurance: T
• HMOs: T

Default Insurance Codes (if needed):

• Client/Account: 033
• Patient: 033
• Medicare: 9999999
• Medicare: 9999999
• Private Insurance: 9999999
• HMOs: 9999999

Insured relationship to Patient:

• Self: Self
• Spouse: Spouse
• Child: Child

Guarantor relationship to Patient:

• Self: Self
• Spouse: Spouse
• Child: Child
• Other: Other

Lab Compendum Formatting

Lab Compendium Formatting typically refers to a structured way of organizing and presenting information about laboratory experiments, protocols, and findings in a consistent manner. 

Labs and 3rd parties connecting with RXNT:

If possible, please use this format when providing us with a compendium using the specified format (AOEs are supported).

Still, need help? Contact us!

Have a great idea? Tell us about it!