This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

VirtualMedicalDevice FHIR Profile Proposal

From HL7Wiki
Revision as of 16:23, 31 October 2019 by JoshP (talk | contribs) (migrate to Confluence)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search



VirtualMedicalDevice

Profile Details

Parent Resource

Constraints to be Applied

  • parent = Resource(MedicalDeviceSystem)

Extensions to be Applied

  • None

Example Scenarios

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

Scope of coverage

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

Owning committee name

Health Care Devices (DEV) WG

Contributing or Reviewing Work Groups

Health Care Devices (DEV) WG

Expected implementations

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

gForge Users

TBD

FHIR Profile Development Project Insight ID

TBD

Plans

Timelines

  • 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