Difference between revisions of "Alert FHIR Resource Proposal"
Line 106: | Line 106: | ||
Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording) | Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording) | ||
--> | --> | ||
− | An alert is linked to the patient resource | + | 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== | ==Timelines== |
Revision as of 19:57, 27 May 2013
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
Alert
Owning committee name
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 should not be the only place where clinical content is saved as an alert can be de-activated. 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 time.
RIM scope
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