This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Alert FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
Line 113: Line 113:
  
 
<!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting -->
 
<!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting -->
 +
Expected to be balloted DSTU in September 2013
  
 
==gForge Users==
 
==gForge Users==
  
 
<!-- 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.) -->

Revision as of 17:34, 27 May 2013



putProposedResourceNameHere

Owning committee name

Patient Care

Contributing or Reviewing Work Groups

  • Work Group Name
  • or link
  • or "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 well understood concept, particularly in EMR and EHR systems as it ensures that important information is readily available.

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

Timelines

Expected to be balloted DSTU in September 2013

gForge Users