Page tree
Skip to end of metadata
Go to start of metadata




VirtualMedicalDevice[edit | edit source]

Profile Details[edit | edit source]

Parent Resource[edit | edit source]

Constraints to be Applied[edit | edit source]

  • parent = Resource(MedicalDeviceSystem)

Extensions to be Applied[edit | edit source]

  • None

Example Scenarios[edit | edit source]

  • A plugin module (virtual medical device) from a patient monitoring system containment tree.

Scope of coverage[edit | edit source]

The VirtualMedicalDevice profile describes the characteristics, operational status and capabilities of a medical-related subsystem. It can either be a physical hardware piece or a pure software plugin component of a medical device.

Note:

For the initial scope, this VirtualMedicalDevice profile is only applicable to describe a single VMD node represents in the containment tree that is produced by the context scanner in any medical device that implements or derives from the ISO/IEEE 11073 standard.

Ownership[edit | edit source]

Owning committee name[edit | edit source]

Health Care Devices (DEV) WG

Contributing or Reviewing Work Groups[edit | edit source]

Health Care Devices (DEV) WG

Expected implementations[edit | edit source]

  • Center for Medical Interoperability will be in collaboration with Dräger Medical to work on the profile definition for VirtualMedicalDevice.

gForge Users[edit | edit source]

TBD

FHIR Profile Development Project Insight ID[edit | edit source]

TBD

Plans[edit | edit source]

Timelines[edit | edit source]

  • This proposal will not be addressed in the current DSTU cycle. It is provided as guidance to our intended overall architecture for device communications and will be implemented in the future.

Balloting Requirements