HL7 Integration
InSched supports HL7 (Health Level Seven) message creation for exchanging clinical and financial data with other healthcare systems. HL7 is a widely adopted standard for healthcare data interoperability.
Supported Message Types
| Message | Type | Description |
|---|---|---|
| ADT A19 | Patient Query | Patient demographic query and response |
| DFT P03 | Financial | Detailed financial transaction |
HL7 Message Structure
Message Header (MSH)
Every HL7 message begins with a header segment containing:
- Sending and receiving application identifiers
- Sending and receiving facility identifiers
- Message control ID
- HL7 version (default: 2.7)
- Testing flag
Standard Separators
| Separator | Character | Purpose |
|---|---|---|
| Field | | | Separates fields within a segment |
| Component | ^ | Separates components within a field |
| Repetition | ~ | Separates repeating fields |
| Escape | \ | Escape character |
| Subcomponent | & | Separates subcomponents |
HL7 Segments Generated
| Segment | Name | Content |
|---|---|---|
| MSH | Message Header | Routing and version information |
| EVN | Event Type | Trigger event details |
| PID | Patient Identification | Demographics, identifiers, contact info |
| PV1 | Patient Visit | Visit/encounter details |
| GT1 | Guarantor | Guarantor information |
| IN1 | Insurance | Insurance coverage details |
| FT1 | Financial Transaction | Charge and payment details |
Data Types
The integration uses standard HL7 data types:
| Type | Name | Example Usage |
|---|---|---|
| XCN | Extended Composite ID | Provider identification |
| XTN | Extended Telecommunication | Phone numbers, email |
| PL | Person Location | Address fields |
Usage
HL7 messages are generated automatically when configured events occur (such as patient check-in or charge posting), enabling real-time data exchange with connected systems like labs, hospitals, or clearinghouses.