Skip to main content

Data formats

Terms used on this page (7)
  • HL7 - Health Level Seven - the standard family for exchanging healthcare messages
  • FHIR - Fast Healthcare Interoperability Resources - a modern web API standard for health data
  • ORM - an HL7 v2 order message
  • OML - an HL7 v2 laboratory order message
  • ORU - an HL7 v2 observation result message
  • CSV - comma-separated values - a text file with one record per row
  • XLSX - the Excel workbook file format

See the Glossary for every term.

A connection is a transport (how data arrives or leaves - MLLP, SFTP, a database...) carrying a format (what the data is - HL7 v2, CSV, JSON...). The two are independent, so the same transport can carry different formats.

CodeFormatWhat it is
HL7V2HL7 v2ORM / OML orders, ORU results - pipe-delimited segments
FHIR_R4FHIR R4ServiceRequest / DiagnosticReport bundles, JSON or XML
JSONJSONAny JSON document, mapped field by field
XMLXMLAny XML document, mapped by path
CSVCSVOne order or result per row, columns from the header line
XLSXExcel (XLSX)A worksheet, one order or result per row
FIXED_WIDTHFixed-width textPositional flat files from older systems
PDFPDFResult reports going out - not parsed on the way in

Which connector carries which format​

ConnectorHL7 v2FHIR R4JSONXMLCSVExcel (XLSX)Fixed-width textPDF
MLLP (HL7 over TCP)✅
Apache Kafka✅✅✅✅✅
RabbitMQ✅✅✅✅✅
Email✅✅✅✅✅✅✅✅
HTTP / REST API✅✅✅✅✅
Inbound webhook✅✅✅✅✅
FHIR server✅
SOAP web service✅✅
SFTP✅✅✅✅✅✅✅✅
FTP / FTPS✅✅✅✅✅✅✅✅
Shared folder✅✅✅✅✅✅✅✅
Database✅
Amazon S3✅✅✅✅✅✅✅✅
Azure Blob Storage✅✅✅✅✅✅✅✅
note

PDF is for result reports going out - it is not parsed on the way in.

A ticked format is what you can configure, not what carries orders today

Which connector and format combinations carry real orders right now is on the Stage 1 and Stage 2 page.