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

Difference between revisions of "HeartRate FHIR Profile Proposal"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "{{subst::Template:FHIR Profile Proposal}}")
 
Line 14: Line 14:
  
  
−
=PutProposedProfileNameHere=
+
=HeartRateAnalysis=
  
−
<!-- Profile names should meet the following characteristics:
+
==Profile Details==
−
* 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
 
−
-->
 
  
−
==Resource Details==
+
* This is a profile on observation that shows how to properly report a full heart rate analysis, including defining the relevant vocabularies
 +
* This same profile should be followed for simpler representations of heartbeat
  
 
===Parent Resource===
 
===Parent Resource===
  
−
<!--Put a link to the resource/datatype (or group of resources) that will be profiled here.-->
+
* This profile is a profile on [[http://hl7.org/implement/standards/fhir/observation.html Observation]](and also includes additional component observations)
−
* [[ParentResourceAddress|ResourceName]]
 
  
 
====Constraints to be Applied====
 
====Constraints to be Applied====
  
−
<!--Describe how the current resource will be constrained.-->
+
* This profile will describe a bunch of constraints on the Observation resource
−
* Constraint 1
+
* this profile will include a bunch of value sets that define related values
−
* Constraint 2
 
  
 
====Extensions to be Applied====
 
====Extensions to be Applied====
  
−
<!--Describe how the current resource will be extended.-->
+
* no extensions anticipated
−
* Extension 1
 
−
* 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.) -->
+
* Clinician records a casual observation of a heart rate
 +
* cardio lab reports a full detailed observation of heart and how it responds to exercise
  
 
===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%"
+
Heart Rate analysis
  
−
Scope should consider numerous aspects of breadth of scope, including:
+
* Subject: Human is the focus.  
−
* Subject: Human vs. non-human vs. non-patient (e.g. lab bench medicine)
+
** Todo: is this appropriate for non-human patients?
−
* Disciplines: Environmental Health, Palliative, Respiratory, Psychology, Maternity, Clinical Research
+
** Todo: Is there anything about this profile that makes it unsuitable for use for patient self-measurements of heartrate?
−
* Delivery environment (Community, Geriatric, Home care, Emergency, Inpatient, Intensive, Neonatal, Pediatric, Primary)
+
** Todo: is there anything about this profile that makes it unsuitable for recording a heart rate as part of a set of vital signs?
−
* Locale: Country, region
+
** todo: is there anything about this profile that makes it unsuitable for recording a heart rate from a fitness monitoring device?
 +
* Disciplines: All dicisplines that do heart rate
 +
* Delivery environment: Any
 +
* Locale: Any
  
−
As a rule, Profiles should encompass all of these aspects.
+
==Ownership==
−
-->
 
  
−
==Ownership==
 
 
===Owning committee name===
 
===Owning committee name===
  
−
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the Profiles. -->
+
[[Patient_Care]]
−
[[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) -->
+
* None
−
* Work Group Name
+
 
−
* or link
+
===Relevant Others standards and sources===
−
* or "None"
+
 
 +
* past informative ballot for heart rate DCM
 +
* openEHR heart rate archetype??
  
 
===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. -->
+
* ??
  
 
===gForge Users===
 
===gForge Users===
  
−
<!-- Identify the userids who will require commit access to gForge to maintain the Profile.  (Ensure all users have registered for gForge.) -->
+
* Grahame Grieve
−
 
+
* later: Michael Van Der Zel
  
 
===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 -->
+
* ??
  
 
==Plans==
 
==Plans==
 
===Timelines===
 
===Timelines===
  
−
<!-- Indicate the target date for having the Profile complete from a committee perspective and ready for vetting and voting -->
+
* for QA then DSTU
−
*TargetDateForInternalReview
 
  
 
===Balloting Requirements===
 
===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.-->
+
* Ballot with next FHIR DSTU or Normative Edition
−
 
 
−
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
 

Revision as of 05:14, 25 May 2014

OpenHotTopic.GIF

This page documents a Pending FHIR Resource Proposal



HeartRateAnalysis

Profile Details

  • This is a profile on observation that shows how to properly report a full heart rate analysis, including defining the relevant vocabularies
  • This same profile should be followed for simpler representations of heartbeat

Parent Resource

  • This profile is a profile on [Observation](and also includes additional component observations)

Constraints to be Applied

  • This profile will describe a bunch of constraints on the Observation resource
  • this profile will include a bunch of value sets that define related values

Extensions to be Applied

  • no extensions anticipated

Example Scenarios

  • Clinician records a casual observation of a heart rate
  • cardio lab reports a full detailed observation of heart and how it responds to exercise

Scope of coverage

Heart Rate analysis

  • Subject: Human is the focus.
    • Todo: is this appropriate for non-human patients?
    • Todo: Is there anything about this profile that makes it unsuitable for use for patient self-measurements of heartrate?
    • Todo: is there anything about this profile that makes it unsuitable for recording a heart rate as part of a set of vital signs?
    • todo: is there anything about this profile that makes it unsuitable for recording a heart rate from a fitness monitoring device?
  • Disciplines: All dicisplines that do heart rate
  • Delivery environment: Any
  • Locale: Any

Ownership

Owning committee name

Patient_Care

Contributing or Reviewing Work Groups

  • None

Relevant Others standards and sources

  • past informative ballot for heart rate DCM
  • openEHR heart rate archetype??

Expected implementations

  •  ??

gForge Users

  • Grahame Grieve
  • later: Michael Van Der Zel

FHIR Profile Development Project Insight ID

  •  ??

Plans

Timelines

  • for QA then DSTU

Balloting Requirements

  • Ballot with next FHIR DSTU or Normative Edition
Retrieved from "https://wiki.hl7.org/w/index.php?title=HeartRate_FHIR_Profile_Proposal&oldid=87021"