OperationDefinition-CDR-Task-RejectDocumentMisfile

Overview

Reject Document Misfile.

On successful execution, the CDR updates the identified Task to status completed, records a misfile review outcome of rejected, and records the reviewer and review reason. The CDR also removes the errorstatus meta tag from the focus DocumentReference.

Formal Views of Profile Content

OperationDefinition
OperationDefinition.id[0]CDR-Task-RejectDocumentMisfile
OperationDefinition.url[0]https://fhir.nhs.wales/OperationDefinition/CDR-Task-RejectDocumentMisfile
OperationDefinition.version[0]0.1
OperationDefinition.name[0]CDRTaskRejectDocumentMisfile
OperationDefinition.title[0]CDR Reject Document Misfile
OperationDefinition.status[0]draft
OperationDefinition.kind[0]operation
OperationDefinition.description[0]Reject Document Misfile.
OperationDefinition.affectsState[0]True
OperationDefinition.code[0]reject-document-misfile
OperationDefinition.comment[0]On successful execution, the CDR updates the identified Task to status completed, records a misfile review outcome of rejected, and records the reviewer and review reason. The CDR also removes the errorstatus meta tag from the focus DocumentReference.
OperationDefinition.resource[0]Task
OperationDefinition.system[0]False
OperationDefinition.type[0]False
OperationDefinition.instance[0]True
OperationDefinition.parameter[0].name[0]source
OperationDefinition.parameter[0].use[0]in
OperationDefinition.parameter[0].min[0]1
OperationDefinition.parameter[0].max[0]1
OperationDefinition.parameter[0].documentation[0]The source Device from which the operation request originated. The CDR uses a business identifier of type applicationInstanceId provided in Device.identifier to determine if the Device already exists. If no matching Device record exists, the server will return an error.
OperationDefinition.parameter[0].type[0]Device
OperationDefinition.parameter[1].name[0]timestamp
OperationDefinition.parameter[1].use[0]in
OperationDefinition.parameter[1].min[0]0
OperationDefinition.parameter[1].max[0]1
OperationDefinition.parameter[1].documentation[0]The date and time at which the user completed the document misfile review. If not supplied, the server uses the date and time at which the operation is processed.
OperationDefinition.parameter[1].type[0]dateTime
OperationDefinition.parameter[2].name[0]reviewer
OperationDefinition.parameter[2].use[0]in
OperationDefinition.parameter[2].min[0]1
OperationDefinition.parameter[2].max[0]1
OperationDefinition.parameter[2].documentation[0]The Practitioner reviewing the potentially misfiled document. The CDR uses the business identifier provided in Practitioner.identifier to determine whether the Practitioner already exists. If no matching Practitioner record exists, the server will return an error.
OperationDefinition.parameter[2].type[0]Practitioner
OperationDefinition.parameter[3].name[0]misfileRejectedReason
OperationDefinition.parameter[3].use[0]in
OperationDefinition.parameter[3].min[0]1
OperationDefinition.parameter[3].max[0]1
OperationDefinition.parameter[3].documentation[0]The reason the reviewer rejects that the document is misfiled.
OperationDefinition.parameter[3].type[0]string
OperationDefinition.parameter[4].name[0]return
OperationDefinition.parameter[4].use[0]out
OperationDefinition.parameter[4].min[0]1
OperationDefinition.parameter[4].max[0]1
OperationDefinition.parameter[4].documentation[0]The updated Task recording completion of the document misfile review with an outcome of rejected.
OperationDefinition.parameter[4].type[0]Task
<OperationDefinition xmlns="http://hl7.org/fhir">
<id value="CDR-Task-RejectDocumentMisfile" />
<url value="https://fhir.nhs.wales/OperationDefinition/CDR-Task-RejectDocumentMisfile" />
<version value="0.1" />
<name value="CDRTaskRejectDocumentMisfile" />
<title value="CDR Reject Document Misfile" />
<status value="draft" />
<kind value="operation" />
<description value="Reject Document Misfile." />
<affectsState value="true" />
<code value="reject-document-misfile" />
<comment value="On successful execution, the CDR updates the identified Task to status completed, records a misfile review outcome of rejected, and records the reviewer and review reason. The CDR also removes the errorstatus meta tag from the focus DocumentReference." />
<resource value="Task" />
<system value="false" />
<type value="false" />
<instance value="true" />
<name value="source" />
<use value="in" />
<min value="1" />
<max value="1" />
<documentation value="The source Device from which the operation request originated. The CDR uses a business identifier of type applicationInstanceId provided in Device.identifier to determine if the Device already exists. If no matching Device record exists, the server will return an error." />
<type value="Device" />
</parameter>
<name value="timestamp" />
<use value="in" />
<min value="0" />
<max value="1" />
<documentation value="The date and time at which the user completed the document misfile review. If not supplied, the server uses the date and time at which the operation is processed." />
<type value="dateTime" />
</parameter>
<name value="reviewer" />
<use value="in" />
<min value="1" />
<max value="1" />
<documentation value="The Practitioner reviewing the potentially misfiled document. The CDR uses the business identifier provided in Practitioner.identifier to determine whether the Practitioner already exists. If no matching Practitioner record exists, the server will return an error." />
<type value="Practitioner" />
</parameter>
<name value="misfileRejectedReason" />
<use value="in" />
<min value="1" />
<max value="1" />
<documentation value="The reason the reviewer rejects that the document is misfiled." />
<type value="string" />
</parameter>
<name value="return" />
<use value="out" />
<min value="1" />
<max value="1" />
<documentation value="The updated Task recording completion of the document misfile review with an outcome of rejected." />
<type value="Task" />
</parameter>
</OperationDefinition>
{
"resourceType": "OperationDefinition",
"id": "CDR-Task-RejectDocumentMisfile",
"url": "https://fhir.nhs.wales/OperationDefinition/CDR-Task-RejectDocumentMisfile",
"version": "0.1",
"name": "CDRTaskRejectDocumentMisfile",
"title": "CDR Reject Document Misfile",
"status": "draft",
"kind": "operation",
"description": "Reject Document Misfile.",
"affectsState": true,
"code": "reject-document-misfile",
"comment": "On successful execution, the CDR updates the identified Task to status completed, records a misfile review outcome of rejected, and records the reviewer and review reason. The CDR also removes the errorstatus meta tag from the focus DocumentReference.",
"Task"
],
"system": false,
"type": false,
"instance": true,
{
"name": "source",
"use": "in",
"min": 1,
"max": "1",
"documentation": "The source Device from which the operation request originated. The CDR uses a business identifier of type applicationInstanceId provided in Device.identifier to determine if the Device already exists. If no matching Device record exists, the server will return an error.",
"type": "Device"
},
{
"name": "timestamp",
"use": "in",
"min": 0,
"max": "1",
"documentation": "The date and time at which the user completed the document misfile review. If not supplied, the server uses the date and time at which the operation is processed.",
"type": "dateTime"
},
{
"name": "reviewer",
"use": "in",
"min": 1,
"max": "1",
"documentation": "The Practitioner reviewing the potentially misfiled document. The CDR uses the business identifier provided in Practitioner.identifier to determine whether the Practitioner already exists. If no matching Practitioner record exists, the server will return an error.",
"type": "Practitioner"
},
{
"name": "misfileRejectedReason",
"use": "in",
"min": 1,
"max": "1",
"documentation": "The reason the reviewer rejects that the document is misfiled.",
"type": "string"
},
{
"name": "return",
"use": "out",
"min": 1,
"max": "1",
"documentation": "The updated Task recording completion of the document misfile review with an outcome of rejected.",
"type": "Task"
}
]
}

Example FHIR Resource