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

Difference between revisions of "Medication For Infusion FHIR Profile Proposal"

From HL7Wiki
Jump to navigation Jump to search
(migrate to Confluence)
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
 
<div class="messagebox cleanup metadata">
 
<div class="messagebox cleanup metadata">
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
+
Current version: https://confluence.hl7.org/display/FHIR/Medication+For+Infusion+FHIR+Profile+Proposal<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 
<div style="background:#F0F0F0">
 
<div style="background:#F0F0F0">
 
This page documents a [[:category:Pending FHIR Profile Proposal|Pending]] [[:category:FHIR Profile Proposal|FHIR Profile Proposal]]
 
This page documents a [[:category:Pending FHIR Profile Proposal|Pending]] [[:category:FHIR Profile Proposal|FHIR Profile Proposal]]
Line 26: Line 26:
 
* Be consistent with other similar Profiles
 
* Be consistent with other similar Profiles
 
-->
 
-->
 
+
==Resource Details==
==Parent Resource==
+
===Parent Resource===
  
 
<!--Put a link to the resource that will be profiled here.-->
 
<!--Put a link to the resource that will be profiled here.-->
* [[ParentResourceAddress|ResourceName]]
+
*[[ParentResourceAddress|ResourceName]]
  
===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
+
*Constraint 1
* Constraint 2
+
*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
+
*Extension 1
* Extension 2
+
*Extension 2
  
==Example Scenarios==
+
===Purpose==
 +
<!--Choose one of the following or describe other purpose-->
 +
 
 +
*Part of ballot
 +
*or Define good practice
 +
*or Example
 +
*or Local requirement
 +
*or Other <ProvideDetailsHere>
 +
 
 +
===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.) -->
  
==Scope of coverage==
+
===Scope of coverage===
  
 
<!-- Define the full scope of coverage for the Profile.  The scope must be clearly delineated such that it does not overlap with any other existing or expected Profile.  The scope will be used to govern "what is the set of potential applications to consider when evaluating what elements are 'core' – i.e. in the 80%"
 
<!-- Define the full scope of coverage for the Profile.  The scope must be clearly delineated such that it does not overlap with any other existing or expected Profile.  The scope will be used to govern "what is the set of potential applications to consider when evaluating what elements are 'core' – i.e. in the 80%"
Line 61: Line 70:
 
-->
 
-->
  
==Owning committee name==
+
==Ownership==
 +
===Owning committee name===
  
 
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the Profiles. -->
 
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the Profiles. -->
 
[[YourCommitteeName]]
 
[[YourCommitteeName]]
  
==Contributing or Reviewing Work Groups==
+
===Contributing or Reviewing Work Groups===
  
 
<!-- Additional work groups that may have an interest in contributing to, or reviewing  the content of the Profile (optional) -->
 
<!-- Additional work groups that may have an interest in contributing to, or reviewing  the content of the Profile (optional) -->
* Work Group Name
+
*Work Group Name
* or link
+
*or link
* or "None"
+
*or "None"
 +
 
 +
===gForge Users===
 +
 
 +
<!-- Identify the userids who will require commit access to gForge to maintain the Profile.  (Ensure all users have registered for gForge.) -->
  
==FHIR Profile Development Project Insight ID==
+
===FHIR Profile Development Project Insight ID===
  
 
<!-- Please specify the id of your work group’s PSS for doing FHIR work.  (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc -->
 
<!-- Please specify the id of your work group’s PSS for doing FHIR work.  (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc -->
  
==Expected implementations==
+
===Expected implementations===
  
 
<!--Key Profiles are justified by CCDA, for Profiles not deemed "key", what interest is there by implementers in using this particular Profile. Provide named implementations if possible - ideally provide multiple independent implementations. -->
 
<!--Key Profiles are justified by CCDA, for Profiles not deemed "key", what interest is there by implementers in using this particular Profile. Provide named implementations if possible - ideally provide multiple independent implementations. -->
  
==Timelines==
+
==Plans==
 +
===Timelines===
  
 
<!-- Indicate the target date for having the Profile complete from a committee perspective and ready for vetting and voting -->
 
<!-- Indicate the target date for having the Profile complete from a committee perspective and ready for vetting and voting -->
  
==gForge Users==
+
===Balloting Requirements===
 +
<!-- Indicate the intended method of balloting by choosing one of the options below, or propose alternative-->
  
<!-- Identify the userids who will require commit access to gForge to maintain the Profile.  (Ensure all users have registered for gForge.) -->
+
Choose one:
 +
 
 +
*Ballot with next FHIR DSTU or Normative Edition
 +
*Ballot independently as DSTU
 +
*Realm specific ballot
 +
*No Ballot
 +
 
 +
<!-- Indicate the desired ballot date.-->
 +
Desired Ballot Date
 +
 
 +
*PutDesiredBallotDateHere

Latest revision as of 16:20, 31 October 2019



PutProposedProfileNameHere

Resource Details

Parent Resource

Constraints to be Applied

  • Constraint 1
  • Constraint 2

Extensions to be Applied

  • Extension 1
  • Extension 2

=Purpose

  • Part of ballot
  • or Define good practice
  • or Example
  • or Local requirement
  • or Other <ProvideDetailsHere>

Example Scenarios

Scope of coverage

Ownership

Owning committee name

YourCommitteeName

Contributing or Reviewing Work Groups

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

gForge Users

FHIR Profile Development Project Insight ID

Expected implementations

Plans

Timelines

Balloting Requirements

Choose one:

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

Desired Ballot Date

  • PutDesiredBallotDateHere