D2A Parent Task
The Parent Task builds on the CarePlan and details the high level tasks/activities that need to be undertaken to facilitate a safe and timely discharge and which organisation is responsible for them. The Parent Task will usually be agreed as part of the Triage process in the ToC Hub and recorded in the D2A section of the Notts Care Record (NCR).
Note: as the Parent Task will be created/mastered by the NCR, hence the details below are provided for Data Consumers, e.g. those organisations that wish to automatically create workflow in their line of business systems, when a new Parent task is created for which their Organization is the Owner.
The NCR Project Team can advise on how organisations can create a subscription to Parent Task for their Organization. On receipt of a subscription notification, Data Consumers may also need to fetch the referenced Patient, Encounter Resources etc. to be able to populate all the required fields in the Line of Business System (LoBS)
The D2A parent Task Plan will comprise of the following attributes:
Attribute | Cardinality | Type | Details |
---|---|---|---|
meta.profile | 1..1 | url | Fixed: https://fhir.hl7.org.uk/STU3/StructureDefinition/CareConnect-Task-1 |
id | 1..1 | string | Unique id for updates and referencing |
basedOn | 1..1 | Reference | Reference to the CarePlan created by the Hospital to model the D2A Discharge Plan |
status | 1..1 | code | 'requested' when the task is created 'cancelled' if the task is cancelled Note: all other statuses will be derived from the assoicated D2A Child Task |
intent | 1..1 | code | Fixed: plan |
code.coding | 1..1 | code | Fixed: "system": "https://fhir.nottscr.nhs.uk/CodeSystem/D2A-ArtifactCode-1", |
description | 1..1 | string | description of what is required |
for | 1..1 | Reference | Reference to the relevant Patient FHIR Resource |
context | 1..1 | Reference | Reference to the relevant Encounter FHIR Resource |
executionPeriod.start | 1..1 | DateTime | When the D2A Parent Task was added in the NCR |
executionPeriod.end | 0..1 | DateTime | When the D2A Parent Task was cancelled in the NCR (Note: period.end will be derived from the aassoicated D2A Child Task when one exists and parent has not been cancelled) |
authoredOn | 1..1 | DateTime | When the task was created .., this will be the same as executionPeriod.start |
lastModified | 1..1 | DateTime | When the task was last updated |
owner | 1..1 | Reference | Reference to Organization that is responsible for the task |
output:reasonForAbandonedDischarge | 0..1 | code/string | details of why the task was cancelled / discharge abandoned |
Example
Example of a D2A Trigger Task :