Current Build
FHIR Infrastructure Work GroupMaturity Level: 3Ballot Status: Trial Use

This page describes several issues around lifecycle management for the resources and the content they contain. Specifically, this page describes:

Many FHIR resources have a status element that represents the lifecycle state of the resource or the clinical process represented by the resource. Work groups can specify status values appropriate to the individual resource. Although consistency between resources is not the primary objective, it is helpful to users and developers to have well-crafted value sets that cover all possible states (since the value sets are typically required and non-extensible).

To understand existing status elements, and to help create extensions and resources involving resource states, we note that status value sets follow one of the following life cycles:

  • Clinical workflow process life cycle
  • Request/Order life cycle
  • Entity status life cycle
  • Clinical status life cycle

Describes the lifecycle states of complex activities common in healthcare. Typically, these states follow a chronological life cycle that leads from initiation to the conclusion of the action. A characteristic (but non-exhaustive) set of states for the clinical workflow process life cycle include:

  • planned - resources for the activity are being allocated but the activity has not begun
  • cancelled - the planned activity did not start and will not take place
  • in-progress - the activity has begun
  • on-hold (suspended) - the activity has been temporarily interrupted
  • stopped (aborted, failed) - the activity has not been completed but no future action is planned
  • completed (finished) - the activity has been completed

Examples of the clinical workflow life cycle:

  • Communication.status: preparation | in-progress | not-done | suspended | aborted | completed | entered-in-error | unknown
  • Encounter.status: planned | arrived | triaged | in-progress | onleave | finished | cancelled | entered-in-error | unknown
  • Goal.status: proposed | accepted | cancelled | entered-in-error | rejected
  • MedicationAdministration.status: in-progress | not-done | on-hold | completed | entered-in-error | stopped | unknown
  • MedicationDispense.status: preparation | in-progress | not-done | on-hold | completed | entered-in-error | stopped
  • Procedure.status: preparation | in-progress | not-done | suspended | aborted | completed | entered-in-error | unknown

Some resources in FHIR represent orders or requests. The request lifecycle can be generalized in terms of four stages: creating the request, sending the request, receiving acceptance or refusal of the request, and fulfillment of the request. A characteristic (but non-exhaustive) set of states for the request/order pattern include:

  • proposed: An actor (e.g. a clinical decision support system) has proposed an action to be requested
  • draft: The request is in preliminary form, prior to being requested
  • requested: The request has been made
  • rejected: The request receiver has declined the request
  • accepted: The request receiver has accepted the request
  • in-progress: Work to fulfill the request has begun
  • on-hold (suspended): Work on the request has been interrupted
  • stopped (aborted): The activity has not been completed but no future action is planned
  • completed: Work on the requested task has been completed, and no further action is required
  • cancelled: The request has been withdrawn

Examples of the request/order life cycle:

  • CommunicationRequest.status: draft | active | suspended | cancelled | completed | entered-in-error | unknown
  • DeviceRequest.status: draft | active | suspended | cancelled | completed | entered-in-error | unknown
  • MedicationRequest.status: active | on-hold | cancelled | completed | entered-in-error | stopped | draft | unknown
  • ServiceRequest.status: draft | active | suspended | cancelled | completed | entered-in-error | unknown

The entity availability life cycle indicates if the resource, or the entity described by the resource, is ready for use, not yet ready for use, or has been retired from use. A characteristic (but non-exhaustive) set of states for the entity availability life cycle include:

  • draft: The entity is being prepared but is not yet in use
  • active: The entity is in use
  • suspended: The entity is not in use at the momesnt, but may return to active status
  • amended: The entity has undergone a revision but is still active
  • retired (superseded): The entity is no longer in use.

Examples of the entity availability life cycle:

  • DiagnosticReport.status: registered | partial | final | amended | cancelled | entered-in-error | unknown
  • MedicationStatement.status: active | completed | entered-in-error | intended | stopped | on-hold | unknown | not-taken. (note: in-progress and completed are states reflecting the administration of the medication)
  • DocumentManifest.status: current | superseded | entered-in-error
  • CapabilityStatement.status: draft | active | retired | unknown
  • StructureDefinition.status: draft | active | retired | unknown
  • Questionnaire.status: draft | active | retired | unknown
  • DocumentReference.status: current | superseded | entered-in-error
  • QuestionnaireResponse.status: in-progress | completed | amended | entered-in-error | stopped
  • Flag.status: active | inactive | entered-in-error
  • Location.status: active | suspended | inactive
  • Organization.active: true | false
  • Patient.active: true | false

Clinical status is somewhat different than the previous status values, since it does not deal with workflow or lifecycle. Instead, it indicates how evidence is affecting a clinical interpretation. Here are two examples:

  • AllergyIntolerance.clinicalStatus: active | inactive
  • Condition.clinicalStatus: active | inactive

Many clinical systems maintain current lists of some kind of resources for a patient. Some of the commonly maintained lists include:

  • Current Problem List: a list of the problems that are of concern for care of the patient
  • Current Medication List: a list of the medications that a patient is known to be on at the current time

Because of the way that resources are used, there is no simple way to determine, from examination of a resource, whether it is 'current' or not. Take, as an example, the Condition resource. In a typical EHR, condition resources might be published on the RESTful interface for the following reasons:

  • to represent an item in a patient's curated problem list
  • to represent a complaint or a diagnosis from an encounter record
  • to represent a problem for investigation provided by a diagnostic system as part of a ServiceRequest/DiagnosticReport pair
  • the resources were received from another system as part of a referral package, and were current for that system when they were received

There is no element on the Condition resource than can convey the difference between these usages. In particular, there can be no way to differentiate between current and past resources without having to retrospectively alter resources, which is problematic with regard to integrity and digital signatures.

One consequence of this is that searching the condition resource for a given patient will return more than just the patient's current problems. Though this is somewhat counter-intuitive to some implementers, restricting searches on Condition to only include the patient's current curated problem list excludes all the other - important - uses of the Condition resource.

Determining whether a Condition is an entry on a patient's current problem list is done by checking with the Condition resource is referenced from the correct list.

On the RESTful API, this is done using the list search mechanism:

 GET [base]/AllergyIntolerance?patient=42&_list=$current-allergies

This is a request to fetch all the allergies in the patient 42's "Current Problem List". Note that the server is not required to actually make a resource representation of the current allergy list available, though doing so assists clients in their audit/integrity tasks. See List Operation "Find" for further information.

In a document, current lists are determined by the code on a Composition section.

FHIR defines the following names for functional lists:

List ResourceType Description Possible LOINC codes in documents / sections
$current-problems Condition The "Current Problem List" - A list of current and active diagnoses as well as past diagnoses relevant to the current care of the patient 46105-3 (Problem conditions Set)
$current-medications MedicationStatement/ MedicationRequest A list of all medications that the patient is taking. The 'current medications list' sometimes may include a mix of prescribed and over-the-counter medications - or only some of them. The list may contain a mix of prescriptions and more general statements, or only one of the two. The list may also correspond to a formal reconciled medication administration schedule, but more often does not 57828-6 (Prescription list), 10160-0 (History of medication)
$current-allergies AllergyIntolerance A list of known or suspected propensities to medications, foods, or environmental agents that is provided to help prevent reactions while care is occurring 18716-1 (Allergy studies (set)), 52472-8 (Allergies and Adverse Drug Reactions), and 48765-2 (Allergies and adverse reactions Document)
$current-drug-allergies AllergyIntolerance A list of known or suspected propensities to medications that is provided to help prevent reactions while care is occurring. This list is a subset of the full allergies list (same as above?)

The entered-in-error state indicates the resource was created accidentally, and should be ignored. This state can apply to resources created by manual entry. It is usually not associated with the Clinical Workflow Process life cycle, but can be associated with the Request/Order and the Entity Availability life cycles.

This table summarizes what is expected to happen for each resource in the case that the data it contains is subsequently found to be an erroneous entry.

ResourceStatus
Account.status = entered-in-error
ActivityDefinition.status = retired
AdverseEvent
AllergyIntolerance.verificationStatus = entered-in-error
Appointment.status=entered-in-error
AppointmentResponse.participantStatus=entered-in-error
AuditEventAudit Events are recorded, there is no update or delete.
BasicThere are no fixed arrangements for Basic - profiles should describe how this works as arrangements will depend on the 'type' of Basic resource
Binaryn/a (This would be handled where the binary is linked from)
BodyStructure.active = false
BundleDepends on the type: document - see for Composition; message - see for MessageHeader; transaction / transaction-response / history / searchset - not expected to be stored; collection: just delete it if it's stored, and in error
CapabilityStatement.status = retired
CarePlan.status = entered-in-error
CareTeam.status = entered-in-error
ChargeItem.status = entered-in-error
Claim.status = entered-in-error
ClaimResponse.status = entered-in-error
ClinicalImpression.status = entered-in-error
CodeSystem.status = retired
Communication.status = entered-in-error
CommunicationRequest.status = entered-in-error
CompartmentDefinition.status = retired
Composition.status = entered-in-error
ConceptMap.status = retired
Condition.verificationStatus = entered-in-error
Consent.status = entered-in-error
Contract.status = entered-in-error
Coverage.status = entered-in-error
DetectedIssue.status = entered-in-error
Device.status = entered-in-error
DeviceComponent.operationalStatus = entered-in-error
DeviceMetric.operationalStatus = entered-in-error
DeviceRequest.status = entered-in-error
DeviceUseStatement.status = entered-in-error
DiagnosticReport.status = entered-in-error
DocumentManifest.status = entered-in-error
DocumentReference.status = entered-in-error
EligibilityRequest.status = entered-in-error
EligibilityResponse.status = entered-in-error
Encounter.status=entered-in-error
Endpoint.status=entered-in-error
EnrollmentRequest.status = entered-in-error
EnrollmentResponse.status = entered-in-error
EntryDefinition
EpisodeOfCare.status=entered-in-error
EventDefinition.status = retired
ExampleScenario.status = retired
ExpansionProfile.status=retired
ExplanationOfBenefit.status = entered-in-error
FamilyMemberHistory.status = entered-in-error
Flag.status = entered-in-error
Goal.status = entered-in-error
GraphDefinition.status = retired
Group.active = false
GuidanceResponse.status = entered-in-error
HealthcareService.active = false
ImagingManifestImaging Object Selection state is managed in PACS.
ImagingStudyImaging Study state is managed in PACS.
Immunization.status = entered-in-error
ImmunizationRecommendationImmunization recommendations are generated on "just in time" and typically are not retained by the system generating them so there isn't an expected workflow where a previous recommendation would be re-evaluated and found to be "in error".
ImplementationGuide.status = retired
ImplementationGuideInput.status = retired
ImplementationGuideOutput.status = retired
Library.status = retired
Linkage.active = false
List.status = entered-in-error
Location.status = inactive
MeasureDelete the report if it is
MeasureReportDelete the report if it is
Median/a - this would be handled whereever the media is linked from
MedicationMedication does not have a status
MedicationAdministration.status = entered-in-error
MedicationDispense.status = entered-in-error
MedicationRequest.status = entered-in-error
MedicationStatement.status = entered-in-error
MessageDefinitionmostly n/a, but in the cases where messages are stored in error, they would simply be deleted
MessageHeadermostly n/a, but in the cases where messages are stored in error, they would simply be deleted
NamingSystem.status = retired
NutritionOrder.status = entered-in-error
Observation.status = entered-in-error
ObservationDefinition
OperationDefinition.status = retired
OperationOutcomen/a - this resource is not expected to be stored
Organization.active = false
Patient.active = false
PaymentNotice.status = entered-in-error
PaymentReconciliation.status = entered-in-error
Person.active = false
PlanDefinition.status = retired
Practitioner.active = false
PractitionerRole.active = false
Procedure.status = entered-in-error
ProcessRequest.status = entered-in-error
ProcessResponse.status = entered-in-error
ProvenanceProvenance are recorded, there is no update or delete.
Questionnaire.status = retired
QuestionnaireResponse.status = entered-in-error
RelatedPerson.active = false
RequestGroup.status = entered-in-error
ResearchStudy.status = entered-in-error
ResearchSubject.status = entered-in-error
RiskAssessment.status = entered-in-error
Schedule.active = false
SearchParameter.status = retired
Sequence.status = entered-in-error
ServiceDefinition.status = retired
ServiceRequest.status = entered-in-error
Slot.status = entered-in-error
Specimen.status = entered-in-error
SpecimenDefinition
StructureDefinition.status = retired
StructureMap.status = retired
Subscription.status = off (just turn it off, maybe update the error message)
Substance.status = entered-in-error
SupplyDelivery.status = entered-in-error
SupplyRequest.status = entered-in-error
Task.status = entered-in-error
TerminologyCapabilities.status = retired
TestReport.status = entered-in-error
TestScript.status = retired
UserSession
ValueSet.status = retired
VisionPrescription.status = entered-in-error

Note: Resources that are not listed in this table do not have any explicit documentation with regard to being entered in error.