Guided Notes

HL7 v2 & Clinical Document Architecture

How HL7 v2 messages and C-CDA documents work, where each is used, their strengths and limitations, and reading them as an informaticist.

HL7 v2 in one slide

Slide 1 / 5

• Event-driven messages (ADT admit, ORU result…) sent between systems inside an organization. • Pipe-delimited segments (MSH, PID, PV1, OBR, OBX) with fields, components (^) and repetitions (~). • Highly flexible — 'if you've seen one HL7 v2 interface, you've seen one': each site customizes fields, so every interface needs specification and testing. • Still the backbone of hospital integration.