Difference between revisions of "Alert FHIR Resource Proposal"
| Line 1: | Line 1: | ||
| − | |||
<div class="messagebox cleanup metadata"> | <div class="messagebox cleanup metadata"> | ||
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | <div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | ||
| Line 56: | Line 55: | ||
As a rule, resources should encompass all of these aspects. | As a rule, resources should encompass all of these aspects. | ||
--> | --> | ||
| − | An alert is a prospective warnings of things that should be taken notice of when providing care to the patient. They are intended to be displayed to a clinician at the point of providing care, but can be available at other times also. The content of the alert can be anything that is of relevance both clinical and non-clinical. For example "Patient has a big dog at home" is as relevant as "Brittle asthmatic, treat aggressively". Alerts should | + | An alert is a prospective warnings of things that should be taken notice of when providing care to the patient. They are intended to be displayed to a clinician at the point of providing care, but can be available at other times also. The content of the alert can be anything that is of relevance both clinical and non-clinical. For example "Patient has a big dog at home" is as relevant as "Brittle asthmatic, treat aggressively". Alerts may duplicate information captured in other resources - AllergyIntolerance, Observation, Problem, Procedure, etc. The purpose is to flag key information for immediate and/or continuous display to healthcare providers. Detailed information should be captured using the appropriate other resource. For example, in the asthmatic example the clinical content would also be a note against the Problem resource - the purpose of the alert is to ensure that the clinician is aware of it at all times. |
==RIM scope== | ==RIM scope== | ||
| − | + | Observation[classCode=ALRT, moodCode=EVN] | |
<!-- Identify the formal RIM mapping for the root concept of the resource. The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. --> | <!-- Identify the formal RIM mapping for the root concept of the resource. The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. --> | ||
| Line 119: | Line 118: | ||
<!-- Identify the userids who will require commit access to gForge to maintain the resource. (Ensure all users have registered for gForge.) --> | <!-- Identify the userids who will require commit access to gForge to maintain the resource. (Ensure all users have registered for gForge.) --> | ||
david_hay | david_hay | ||
| + | |||
| + | ==Issues== | ||
| + | * Added clarification about the specific scope differences between Alerts and things like Problem, AllergyIntolerance, AdverseReaction, Observation, etc. We need to clearly define where one ends and the other begins. | ||
Revision as of 15:47, 3 July 2013
This page documents a Pending FHIR Resource Proposal
Contents
- 1 Alert
- 1.1 Owning committee name
- 1.2 Contributing or Reviewing Work Groups
- 1.3 FHIR Resource Development Project Insight ID
- 1.4 Scope of coverage
- 1.5 RIM scope
- 1.6 Resource appropriateness
- 1.7 Expected implementations
- 1.8 Content sources
- 1.9 Example Scenarios
- 1.10 Resource Relationships
- 1.11 Timelines
- 1.12 gForge Users
- 1.13 Issues
Alert
Owning committee name
(Temporarily managed by FHIR Core with review from Patient care)
Contributing or Reviewing Work Groups
None
FHIR Resource Development Project Insight ID
Pending
Scope of coverage
An alert is a prospective warnings of things that should be taken notice of when providing care to the patient. They are intended to be displayed to a clinician at the point of providing care, but can be available at other times also. The content of the alert can be anything that is of relevance both clinical and non-clinical. For example "Patient has a big dog at home" is as relevant as "Brittle asthmatic, treat aggressively". Alerts may duplicate information captured in other resources - AllergyIntolerance, Observation, Problem, Procedure, etc. The purpose is to flag key information for immediate and/or continuous display to healthcare providers. Detailed information should be captured using the appropriate other resource. For example, in the asthmatic example the clinical content would also be a note against the Problem resource - the purpose of the alert is to ensure that the clinician is aware of it at all times.
RIM scope
Observation[classCode=ALRT, moodCode=EVN]
Resource appropriateness
The alert is a well understood concept, particularly in EMR and EHR systems as it ensures that users are made aware of important information about a patient.
Expected implementations
Any PMS system will likely implement an alerting system. In CCDA, Alerts are grouped with allergies and adverse reactions and so an alert would appear in that section of a CCDA document. However FHIR treats them as a separate resource due to the non-clinical nature of many of the instances.
Content sources
Existing PMS systems, CCDA, openEHR
Example Scenarios
- Record administrative alerts - non payer, drug seeker
- Clinical alerts - brittle asthmatic
- Management alerts - patient is a clinician
Resource Relationships
An alert is linked to the patient resource as the subject of the alert, and to a practitioner, patient or device resource as the author of the resource.
Timelines
Expected to be balloted DSTU in September 2013
gForge Users
david_hay
Issues
- Added clarification about the specific scope differences between Alerts and things like Problem, AllergyIntolerance, AdverseReaction, Observation, etc. We need to clearly define where one ends and the other begins.
