Healthcare Information Technology
Why it matters
Medical devices increasingly live on hospital networks, so the CBET exam tests whether you can connect a device to the IT infrastructure without breaking either one. Know the roles of EHR/EMR, PACS, the laboratory information system (LIS), and pharmacy systems, and how data move between them.
Core concepts to master
- Standards and interfaces: HL7 (clinical/administrative messaging), DICOM (medical imaging), FHIR (modern web-based interoperability), and IEEE 802.11 for wireless. Know which standard fits which data type - this is a frequent question.
- Networking basics: IP addressing, DHCP (automatic address assignment), DNS (name resolution), VLANs (segmenting device traffic), switches vs routers, and wired vs wireless security.
- Device integration: bedside monitors to central stations, infusion pumps to the EHR, and the concept of a device integration/connectivity engine.
- Security and privacy: HIPAA Privacy Rule (use/disclosure of protected health information) vs Security Rule (administrative, physical, technical safeguards); encryption, authentication, least privilege, and patching.
- Risk management for networked devices: IEC 80001-family concepts - inventory, risk assessment, and change control before connecting a device to the network.
- Downtime and backup: what happens when the network fails, and how devices behave.
Traps
Mixing HL7 and DICOM; assuming HIPAA only means passwords; confusing a VLAN with a VPN; and forgetting that a device’s network configuration change is a change-control event requiring documentation and often vendor coordination.
Rule of thumb
Identify the data type first, then the standard, then the transport. Images → DICOM; orders, results, and ADT messages → HL7; web/app interoperability → FHIR; wireless link → 802.11. Then ask who owns the endpoint and who owns the network.
Worked example
A CT scanner cannot send studies to the archive. Verify the device’s IP/gateway and DICOM AE titles and destination port, confirm the PACS is reachable (ping), then check the DICOM service logs. Do not start by rebooting the scanner - verify the path first.