Hello everyone, @grace @dkayiwa @raff @mseaton @ibacher @taseew
In our current Bahmni implementation, we are utilizing the FHIR Workflow Module to manage request-fulfillment patterns. We have found that the current implementation of org.openmrs.module.fhir2.model.FhirTask (v2.5.0) only supports a limited set of statuses: REQUESTED, ACCEPTED, REJECTED, and COMPLETED.
To support more granular clinical workflows, we would like to propose adding the following R4-compliant statuses to the model:
READY: Essential for signaling that a specimen has been collected and the task is now actionable.
ON HOLD: Critical for exception handling, such as when a test is paused due to some issues.
CANCELLED: Necessary to track orders that are discontinued after they have already been accepted by the fulfiller.
Expanding the fhir_task table to include these states will significantly improve the visibility of order fulfillment for clinicians using the Order Tracking dashboards.
We are eager to hear the community’s thoughts on expanding the FhirTask status enum to better align with the HL7 FHIR R4 specification.
@angshuonline @mohant @rahu1ramesh @arshiya_sehzad @akhilmalhotra @devsingh05298