OperationDefinition-CDR-Task-AcceptDocumentMisfile
Overview
Accept Document Misfile.
On successful execution, the CDR updates the identified Task to status completed, records a misfile review outcome of accepted, and records the reviewer and review reason. The CDR also updates the focus DocumentReference to status entered-in-error and updates its errorstatus meta tag to indicate that the document is misfiled.
Formal Views of Profile Content
- Overview
- Table
- XML
- JSON
| OperationDefinition |
| id : CDR-Task-AcceptDocumentMisfile |
| url : https://fhir.nhs.wales/OperationDefinition/CDR-Task-AcceptDocumentMisfile |
| version : 0.1 |
| name : CDRTaskAcceptDocumentMisfile |
| title : CDR Accept Document Misfile |
| status : draft |
| kind : operation |
| description : Accept Document Misfile. |
| affectsState : True |
| code : accept-document-misfile |
| comment : On successful execution, the CDR updates the identified Task to status completed, records a misfile review outcome of accepted, and records the reviewer and review reason. The CDR also updates the focus DocumentReference to status entered-in-error and updates its errorstatus meta tag to indicate that the document is misfiled. |
| resource : Task |
| system : False |
| type : False |
| instance : True |
| parameter |
| 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 |
| parameter |
| 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 |
| parameter |
| 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 |
| parameter |
| name : misfileAcceptedReason |
| use : in |
| min : 1 |
| max : 1 |
| documentation : The reason the reviewer accepts that the document is misfiled. |
| type : string |
| parameter |
| name : return |
| use : out |
| min : 1 |
| max : 1 |
| documentation : The updated Task recording completion of the document misfile review with an outcome of accepted. |
| type : Task |
| OperationDefinition.id[0] | CDR-Task-AcceptDocumentMisfile |
| OperationDefinition.url[0] | https://fhir.nhs.wales/OperationDefinition/CDR-Task-AcceptDocumentMisfile |
| OperationDefinition.version[0] | 0.1 |
| OperationDefinition.name[0] | CDRTaskAcceptDocumentMisfile |
| OperationDefinition.title[0] | CDR Accept Document Misfile |
| OperationDefinition.status[0] | draft |
| OperationDefinition.kind[0] | operation |
| OperationDefinition.description[0] | Accept Document Misfile. |
| OperationDefinition.affectsState[0] | True |
| OperationDefinition.code[0] | accept-document-misfile |
| OperationDefinition.comment[0] | On successful execution, the CDR updates the identified Task to status completed, records a misfile review outcome of accepted, and records the reviewer and review reason. The CDR also updates the focus DocumentReference to status entered-in-error and updates its errorstatus meta tag to indicate that the document is misfiled. |
| 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] | misfileAcceptedReason |
| 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 accepts 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 accepted. |
| OperationDefinition.parameter[4].type[0] | Task |
<comment value="On successful execution, the CDR updates the identified Task to status completed, records a misfile review outcome of accepted, and records the reviewer and review reason. The CDR also updates the focus DocumentReference to status entered-in-error and updates its errorstatus meta tag to indicate that the document is misfiled." />
<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." />
</parameter>
<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." />
</parameter>
<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." />
</parameter>
</parameter>
<documentation value="The updated Task recording completion of the document misfile review with an outcome of accepted." />
</parameter>
</OperationDefinition>
{
"comment": "On successful execution, the CDR updates the identified Task to status completed, records a misfile review outcome of accepted, and records the reviewer and review reason. The CDR also updates the focus DocumentReference to status entered-in-error and updates its errorstatus meta tag to indicate that the document is misfiled.",
"Task"
],
{
"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.",
},
{
"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.",
},
{
"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.",
},
{
},
{
"documentation": "The updated Task recording completion of the document misfile review with an outcome of accepted.",
}
]
}