This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Operation Outcome FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
Line 30: Line 30:
 
FHIR Core Team (eventually, InM)
 
FHIR Core Team (eventually, InM)
 
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. -->
 
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. -->
[[YourCommitteeName]]
 
  
 
==Reviewing Work Groups==
 
==Reviewing Work Groups==

Revision as of 20:39, 10 February 2013



IssueReport

Owning committee name

FHIR Core Team (eventually, InM)

Reviewing Work Groups

InM

FHIR Resource Development Project Insight ID

None - FMG needs to do a PSS

Scope of coverage

Reflects both system level and business level issues (errors, warnings and information messages) resulting from some sort of system action on a FHIR resource or bundle of resources. Encompasses such concepts as:

  • user doesn't have permission
  • internal database error
  • drug dose out of bounds
  • duplicate record

Note: Instances of this resource may be transient or persisted.


RIM scope

  • AcknowledgementDetail (system issues)
  • Observation[classCode="ALRT" and moodCode="EVN"] (business issues)


Resource appropriateness

Base construct exists in most communication protocols that involve requesting an action. Healthcare introduces specific types of healthcare issues such as contraindications.

Simple error responses might *not* have an identifier because they are only relevant in the context of a particular request and there is no need to persist them. However, if there is a need to persist repsonses or if there's a need to track issues identified (and possibly managed) associated with a particular action, then they will be tracked and potentially queryable.


Expected implementations

Mandated as part of the response for "failure" when invoking REST operations. May also be part of response for messages


Content sources

  • v2 ERR segment
  • v3 AcknowledgementDetail in Transmission wrappers
  • v3 DetectedIssue CMET
  • SOAP?
  • NCPDP?
  • Others?


Resource Relationships

No relationships expected in core. Some order resources might have links to IssueReport to identify issues associated with the order. In extensions, an IssueReport might refer to resources relevant to the issue or even where the issue itself is defined.


Timelines

Part of initial DSTU

gForge Users

N/A