Wiki Spaces

Documentation
Projects
Resources

Get Help from Others

Q&A: Ask OpenMRS
Discussion: OpenMRS Talk
Real-Time: IRC Chat | Slack

Projects

Page tree
Skip to end of metadata
Go to start of metadata

FM2-2 - Getting issue details... STATUS

Task is a FHIR resource that is part of the Workflow ModuleTask is used to represent an activity that is to be performed,and track the completion of said activity.

A number of different communication patterns use the Task resource, including the placing and fulfilling laboratory orders.. 

The OpenMRS data model does not contain a natural mapping of this concept support. In order to support workflows requiring Task, the OpenMRS FHIR module extends the data model with a representation of the Task resource that is stored in the fhir_task table. 

Supported Elements

  • Task.id - The logical identifier of the Task resource
  • Task.status - The current status of the Task, represented using states from this state machine. The OpenMRS implementation supports requested, accepted, rejected, and completed states. 
  • Task.basedOn - A reference to the ServiceRequest resource that represents the order that caused the creation of this Task.
  • Task.intent - Represents the actionability of the Task. The current OpenMRS implementation supports only the order value for this element. 
  • Task.inputs - Information needed for performing the Task.
  • Task.outputs - Information produced by performing the Task.

Task.status State Machine

Supported States: REQUESTED, REJECTED, ACCEPTED, COMPLETED


Targeted OpenMRS Use Cases 

  1. Lab Integration Workflow

Available RESTful web services for the Task Resource supported by the OpenMRS FHIR API

GET

URLDescription
/ws/fhir2/Task/{uuid}Above request will fetch the DiagnosticReport for the given unique uuid.

CREATE

URLDescription
/ws/fhir2/Task


UPDATE 

URLDescription
/ws/fhir2/Task/{uuid}
  • No labels