Interoperability
IHE DEC
IHE Devices — Device Enterprise Communication (DEC) Integration Profile
Scope
DEC is the IHE profile for publishing point-of-care device data — from vital signs monitors, infusion pumps, ventilators, anesthesia systems, and similar devices — to enterprise applications such as clinical information systems and EHRs. A Device Observation Reporter, typically a gateway, device, or clinical information system, maps proprietary device data into a single syntactic and semantic representation, time-stamps it with consistent enterprise time, and sends it to a Device Observation Consumer as an HL7 v2 message. The ACM alert profile extends DEC.
Where it applies in the room
- Charting validated vital signs and device observations from the bedside into the EHR
- Device gateways and integration middleware between bedside devices and enterprise systems
- Binding patient identity to device data — the profile recommends IHE patient demographics transactions (ITI-21, ITI-30, ITI-31) and treats bar code or RFID as valid alternatives
Key requirements at a glance
| Actors | Device Observation Reporter (DOR) and Device Observation Consumer (DOC). |
|---|---|
| Communicate PCD Data [PCD-01] | HL7 v2 ORU^R01, an unsolicited update initiated by the DOR. MLLP transport by default, with a Web Services transport option. |
| Consistent semantics and time | Device data is mapped to one syntactic and semantic representation and time-stamped with a consistent enterprise time. |
| Subscribe to Patient Data | An optional publish/subscribe extension (DEC-SPD) lets consuming applications negotiate which device data they receive. |
Summarized for reference. Consult the source document for the definitive text.
Caveats
- The profile assumes implementation within a single enterprise on a secure network and does not itself address privacy, security, and confidentiality of cross-enterprise exchange.
- DEC does not address open- or closed-loop control of devices, and real-time data such as alarms and waveforms is outside DEC itself; alerts are carried by the ACM profile.
- Correct device–patient association remains a separate, safety-critical problem; IHE calls patient identification perhaps the most essential infrastructural component of device data exchange.
- Support for a profile, and for its options, varies by implementation. Ask for IHE integration statements and testing evidence rather than relying on a feature list.
Source & further reading
- · IHE Wiki — Device Enterprise Communication — IHE
- · IHE Devices domain — profile list — publisher
- · IHE Devices Technical Framework, Vol. 1 — Profiles (DEC, section 3) — official text (PDF)
- · IHE Devices Technical Framework, Vol. 2 — Transactions (PCD-01) — official text (PDF)
Related frameworks
Also known as
- IHE PCD Device Enterprise Communication
- Device Enterprise Communication
- IHE PCD DEC
- IHE DEC
Help us improve
Spotted something wrong, outdated, or unclear? Let the editors know.