HL7 to ASTM Converter
Convert HL7 v2.x (ORU^R01) lab result messages into ASTM E1394/LIS2-A2 records.
This tool runs entirely in your browser. Your files are never uploaded to a server.
ASTM E1394 / LIS2-A2 output
H|\^&|MSG00001||LabSystem|||||||P|LIS2-A2|20240101120000 P|1||SYNTHETIC-001||Example^Patient||19800101|F O|1|ORD-1||^^^GLU|R|20240101110000|20240101111500 R|1|^^^GLU|98|mg/dL|70-99|N||F C|1|I|Hemolyzed sample, repeat recommended|G L|1|N
Maps the fields both standards use for header, patient, order, result, and comment data (H/P/O/R/C ↔ MSH/PID/OBR/OBX/NTE). Unmapped segments or records (ORC, PV1, NK1, ASTM Q/M, etc.) are dropped and listed above rather than silently lost. This is a structural bridge for common lab-result fields, not a certified interface engine — verify field positions against the exact sending/receiving system profile before production use.
What this tool does
Converts an HL7 v2.x result message into an ASTM E1394/LIS2-A2-style message: MSH becomes an H (Header) record, PID becomes a P (Patient Information) record, each OBR becomes an O (Order) record, each OBX under it becomes an R (Result) record, and each NTE becomes a C (Comment) record attached to the result it followed.
How to use it
Paste an HL7 v2.x message (segments separated by line breaks) into the input box. The tool parses the MSH field separator automatically, converts recognized segments field by field, and lists anything it had to drop or default underneath the output so you can see exactly what didn't carry over.
Worked example
The bundled sample converts a single-result glucose message — MSH/PID/OBR/OBX/NTE — into H/P/O/R/C records terminated by an L record, with the observation identifier, value, units, reference range, abnormal flag, and result status carried straight across.
Field mapping
PID-3 maps to P-4 (patient ID) and PID-5 to P-6 (name). OBR-4 maps to O-5 (universal test ID) and OBR-16 to O-17 (ordering provider). OBX-3/5/6/7/8/11 map to R-3/4/5/6/7/9 (test ID, value, units, reference range, abnormal flag, result status), and NTE-3 maps to C-4 (comment text). MSH-10/11/7 map to H-3/12/14.
What gets dropped
Segments this converter doesn't map — PV1, ORC, NK1, and others — are removed from the output and named in a warning list rather than silently disappearing, so you always know what a receiving ASTM system won't see.
Important limitations
This is a structural field mapper for common ORU^R01-style result messages, not a certified interface engine or a substitute for the exact profile your instrument or LIS vendor documents — HL7 escape sequences and repeating fields aren't expanded, and any segment structure beyond MSH/PID/OBR/OBX/NTE needs manual handling.
Privacy and sources
Conversion runs entirely in your browser; nothing you paste is uploaded. Field correspondences are based on the published HL7 v2.3+ segment definitions and the archived CLSI LIS01-A2/LIS02-A2 (formerly ASTM E1381/E1394) record layouts; content reviewed September 2026.
Frequently Asked Questions
- Which HL7 segments does the converter read?
- MSH, PID, OBR, OBX, and NTE. Any other segment (PV1, ORC, NK1, and so on) is dropped and listed as a warning under the output rather than silently ignored.
- Does it handle multiple results per order?
- Yes — every OBR starts a new O record, and every OBX that follows it becomes its own R record until the next OBR, matching how repeated test panels are normally structured in both formats.
- Can I convert the result back to HL7 afterward?
- Yes — the companion ASTM to HL7 Converter tool performs the reverse mapping, so you can round-trip a message between the two formats to check what survives the conversion.