# Medical device integration readiness evaluation (HospitalRoom.org)

License: CC BY 4.0 — attribute HospitalRoom.org with a link back to
https://hospitalroom.org/frameworks/device-integration-readiness

A HospitalRoom.org working definition, not a published standard. Trace one observation
from the device faceplate to the clinical record. Record who owns each condition
(clinical engineering, biomed, IT, nursing informatics).

## Device–patient association

Question: When a new device is wheeled in or a patient transfers, does every outbound observation resolve to the correct patient and bed without relying on an unwritten room assumption?

- [ ] Present
- [ ] Partial
- [ ] Absent
- Evidence:
- Owner:

## Outbound data path

Question: Do vitals and clinically relevant device events reach the EHR or middleware without bedside retyping, with a known path when the primary gateway fails?

- [ ] Present
- [ ] Partial
- [ ] Absent
- Evidence:
- Owner:

## Semantic mapping

Question: Have units, codes, and enumerations been validated per device model so the flowsheet value matches the device faceplate?

- [ ] Present
- [ ] Partial
- [ ] Absent
- Evidence:
- Owner:

## Time sync & continuity

Question: Are clocks synchronized across device, gateway, and EHR, is end-to-end latency documented, and do gap indicators appear when data stops?

- [ ] Present
- [ ] Partial
- [ ] Absent
- Evidence:
- Owner:

## Governance & safety

Question: Is there a named owner, change control for driver/firmware updates, a defined alarm/alert interaction, and a written cybersecurity posture for the interface?

- [ ] Present
- [ ] Partial
- [ ] Absent
- Evidence:
- Owner:

## Working rule

Device–patient association and outbound data path must both be at least Partial before calling a room's medical device integration ready. A serial cable into a gateway that can chart the wrong patient is not integration. All five Present with flowsheet values clinicians do not trust is still a failed installation.