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

Difference between revisions of "VirtualMedicalDevice FHIR Profile Proposal"

From HL7Wiki
Jump to navigation Jump to search
Line 34: Line 34:
  
 
<!--Put a link to the resource/datatype (or group of resources) that will be profiled here.-->
 
<!--Put a link to the resource/datatype (or group of resources) that will be profiled here.-->
* [[ParentResourceAddress|ResourceName]]
+
* [http://hl7.org/implement/standards/fhir/devicecomponent.html DeviceComponent]
  
 
====Constraints to be Applied====
 
====Constraints to be Applied====
  
 
<!--Describe how the current resource will be constrained.-->
 
<!--Describe how the current resource will be constrained.-->
* Constraint 1
+
* parent = Resource(MedicalDeviceSystem)
* Constraint 2
 
  
 
====Extensions to be Applied====
 
====Extensions to be Applied====
  
 
<!--Describe how the current resource will be extended.-->
 
<!--Describe how the current resource will be extended.-->
* Extension 1
+
* None
* Extension 2
 
  
 
===Example Scenarios===
 
===Example Scenarios===
  
 
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this Profile.  They should demonstrate the full scope of the Profile and allow exercising of the Profiles capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) -->
 
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this Profile.  They should demonstrate the full scope of the Profile and allow exercising of the Profiles capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) -->
 +
* A plugin module (virtual medical device) from a patient monitoring system containment tree.
  
 
===Scope of coverage===
 
===Scope of coverage===
Line 64: Line 63:
 
As a rule, Profiles should encompass all of these aspects.
 
As a rule, Profiles should encompass all of these aspects.
 
-->
 
-->
 +
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==
 
==Ownership==

Revision as of 00:44, 4 October 2014



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

YourCommitteeName

Contributing or Reviewing Work Groups

  • Work Group Name
  • or link
  • or "None"

Expected implementations

gForge Users

FHIR Profile Development Project Insight ID

Plans

Timelines

  • TargetDateForInternalReview

Balloting Requirements

Choose one:

  • Ballot with next FHIR DSTU or Normative Edition
  • or Ballot independently as DSTU
  • or Realm specific ballot
  • or No Ballot

Desired Ballot Date

  • PutDesiredBallotDateHere