Alert FHIR Resource Proposal
This page documents a Pending FHIR Resource Proposal
Contents
- 1 putProposedResourceNameHere
- 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
putProposedResourceNameHere
Owning committee name
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.
