This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Endpoint FHIR Profile Proposal"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "{{subst::Template:FHIR Profile Proposal}}")
 
(Blanked the page)
 
Line 1: Line 1:
  
<div class="messagebox cleanup metadata">
 
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 
<div style="background:#F0F0F0">
 
This page documents a [[:category:Pending FHIR Resource Proposal|Pending]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]]
 
</div>
 
</div>
 
[[Category:FHIR Resource Proposal]]
 
[[Category:FHIR Profile Proposal]]
 
[[Category:Pending FHIR Profile Proposal]]
 
 
 
<!-- For additional guidance on considerations for profile creation, refer to [[FHIR Profile Considerations]] -->
 
 
 
=PutProposedProfileNameHere=
 
 
<!-- Profile names should meet the following characteristics:
 
* Lower camel case
 
* U.S. English
 
* Domain-friendly
 
* Short
 
* Clear
 
* Unique
 
* Avoid non-universal abbreviations (e.g. URL would be ok)
 
* Be expressed as a noun
 
* Be consistent with other similar Profiles
 
* Incorporate the name of the Resource being profiled
 
-->
 
 
==Profile balloting plans==
 
 
 
==Profile Details==
 
 
===Profiled Resource(s)===
 
 
<!--Put a link to the resource/datatype (or group of resources) that will be profiled here.-->
 
* [[ParentResourceAddress|ResourceName]]
 
 
====Constraints to be Applied====
 
 
<!--Describe how the current resource will be constrained.-->
 
* Constraint 1
 
* Constraint 2
 
 
====Extensions to be Applied====
 
 
<!--Describe how the current resource will be extended.-->
 
* Extension 1
 
* Extension 2
 
 
===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.) -->
 
 
===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%"
 
 
Scope should consider numerous aspects of breadth of scope, including:
 
* Subject: Human vs. non-human vs. non-patient (e.g. lab bench medicine)
 
* Disciplines: Environmental Health, Palliative, Respiratory, Psychology, Maternity, Clinical Research
 
* Delivery environment (Community, Geriatric, Home care, Emergency, Inpatient, Intensive, Neonatal, Pediatric, Primary)
 
* Locale: Country, region
 
 
As a rule, Profiles should encompass all of these aspects.
 
-->
 
 
===Realm===
 
Please describe the realm to which this profile applies, or indicate that it is realm neutral.
 
 
==Ownership==
 
===Owning committee name===
 
 
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the Profiles. -->
 
[[YourCommitteeName]]
 
 
===Contributing or Reviewing Work Groups===
 
 
<!-- Additional work groups that may have an interest in contributing to, or reviewing  the content of the Profile (optional) -->
 
* Work Group Name
 
* or link
 
* or "None"
 
 
===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. -->
 
 
===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===
 
 
<!-- 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 -->
 
 
==Plans==
 
===Timelines===
 
 
<!-- Indicate the target date for having the Profile complete from a committee perspective and ready for vetting and voting -->
 
*TargetDateForInternalReview
 
 
===Balloting Requirements===
 
 
<!-- Indicate the intended method of balloting by choosing one of the options below, or propose alternative.  If Realm Specific or No Ballot indicate the amount of informal review required by the FHIR community.-->
 
 
Choose one:
 
*Ballot with next FHIR DSTU or Normative Edition
 
*or Ballot independently as DSTU
 
*or Realm specific ballot
 
*or No Ballot
 
 
<!-- Indicate the desired ballot date.-->
 
Desired Ballot Date
 
*PutDesiredBallotDateHere
 

Latest revision as of 20:33, 12 May 2016