## eRef /Task Resource Profile
**Completeness: 60% Pilot Read%**
[view discussion space](https://3.basecamp.com/3573371/buckets/7773495/documents/1125072124)
A task called "Process Request" is used to track the progress of an eReferral status over the eReferral's lifetime. It is attached to the ServiceRequest by an eReferral server on receive of a new eReferral. See "implementation notes" for more details".
### LEGEND
* ~~strikethrough~~ indicates the the element is not included in this profile
* `red` indicates that the field is likely useful in a future iteration of the specification
**Canonical URl for this profile:**
http://fhir.infoway-inforoute.ca/StructureDefinition/ca-eReferral-Task
| Name | Card | Type | Comments |Terminology Binding|
|---|---|---|---|
| ~~identifier~~ | ~~1..1~~ | ~~Identifier~~ |
| ~~instantiates[x]~~ | ~~0..0~~ | | |
| basedOn | 1..1 | Reference | references the ServiceRequest associated with this task.
| ~~groupIdentifier~~ | ~~0..*~~ | ~~Identifier~~ | ~~Requisition or grouper id~~
| ~~partOf~~ | ~~0..*~~ | ~~Reference(Task)~~ | ~~Composite task~~ unnecessary complexity. Also, there is a similar concept available in ServieRequest.requesition.
| status | 1..1 | code | the eReferral server sets as "requested" if there is an acceptance process in the workflow, or "ready" if not. The eReferral server is responsible for progressing the status through the other states in the task state machine.
| ~~statusReason~~ | ~~0..*~~ | ~~CodeableConcept~~ |
| businessStatus | 0..1 | CodeableConcept | Use businessStatus.text for custom deployment specific status information (e.g., called 3x, waiting for approval, etc...).
| intent | 1..1 | code | set to ="proposal" |
| ~~priority~~ | ~~0..*~~ | ~~code~~ | Is already captured in ServiceRequest
| code | 0..1 | CodeableConcept | For ServiceRequests, the eReferral server set the .coding.code="process-request" and .text to ="Process Request" when a new referral is submitted to the eReferral server. This code stays fixed for the life of this task. `future work - if have other types of tasks may use alternate codes, e.g., for communications`
| ~~description~~ | ~~0..*~~ | ~~string~~ | Assigned by server to describe the task, e.g., ="This task tracks the status of the referral (using status + businessStatus) as it progresses through its lifecycle". Presented for readibility, not computibility.
| ~~focus~~ | ~~0..*~~ | ~~Reference(Any)~~ | ~~What task is acting on~~ (handled by basedOn)
| ~~for~~ | ~~0..*~~ | ~~Reference(Any)~~ | ~~Beneficiary of the Task~~ It is understood that the patient is the benificiary of this task (serviceRequest.subject)
| ~~context~~ | ~~0..*~~ | ~~Reference (Encounter) / EpisodeOfCare)~~ | ~~Healthcare event during which this task originated~~ unnecessary complexity, note that serviceRequests are usually for transfers between organizations.
| executionPeriod | 0..* | Period | .end represents when the ServiceRequest is closed. `Future use: .start can be used to indicate when work started on the ServiceRequest`
| authoredOn | 0..1 | dateTime | the dateTime that the eReferral was received by the eReferral server. This will usually be the same as ServiceRequest.authoredOn, except in cases when ServiceRequest.authoredOn is used to record that a request was signed by the requester before the transmission took place.
| lastModified | 0..1 | dateTime | Used to indicate the dateTime when an update of note/significance was made to the referral (i.e., related resources such as ServiceRequest, patient, Task, Appointment, etc...)
| ~~requester~~ | ~~0..*~~ | ~~Reference(Device \ Organization \ Patient \ Practitioner \ PractitionerRole \ RelatedPerson)~~ | it is implied that this was requested by the serviceRequest.requester
| ~~performerType~~ | ~~0..*~~ | ~~CodeableConcept~~ |
| `owner` | `0..1` | `Reference(PractitionerRole)` |`for future use` the person assigned to the task, who is responsible for handling this referral.
| ~~reasonCode~~ | ~~0..*~~ | ~~CodeableConcept~~ | ~~Why task is needed~~ unnecessary complexity
| ~~reasonReference~~ | ~~0..*~~ | ~~Reference(Any)~~ | ~~Why task is needed~~ unnecessary complexity
| ~~note~~ | ~~0..*~~ | ~~Annotation~~ | ~~Comments made about the task~~
| `relevantHistory` | `0..*` | `Reference(Provenance)` | `for future use - Track the provenance/history for key events of this referral. Note: use this instead of ServiceRequest.relevantHistory`
| ~~restriction~~ | 0..* |~~BackboneElement~~ | ~~constraints on fulfillment tasks~~
| `input` | `0..*` | `BackboneElement` | `for potential future use: information used to perform task. In the case where this referral was created from a forwarded referral, may wish to record the ServiceRequest.basedOn as the Task.input.`
| `output` | `0..*` | `BackboneElement` | `for future use - for the case of sending a forwarded referral based on this referral, could record the forwarded ServiceRequest resource with this. Other potential uses could include recording resultant information packages when a referral is closed (e.g., an outcome message, a consult note)`
| `output.type` | `1..1` | `CodeableConcept` | `for future use` Label for output
| `output.value[x]` | `1..1` | `Reference(Communication)` | `for future use` Result for output