This wiki has undergone a migration to Confluence found Here
Difference between revisions of "HeartRate FHIR Profile Proposal"
Jump to navigation
Jump to search
Line 65: | Line 65: | ||
* past informative ballot for heart rate DCM | * past informative ballot for heart rate DCM | ||
− | * openEHR | + | * openEHR [[http://www.openehr.org/ckm/#showArchetype_1013.1.170 pulse archetype]] |
===Expected implementations=== | ===Expected implementations=== |
Revision as of 07:26, 25 May 2014
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
Contributing or Reviewing Work Groups
- None
Relevant Others standards and sources
- past informative ballot for heart rate DCM
- openEHR [pulse 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