Add cancellation process

[trawlinson-kainos]

Description

Update the API specs to add in the route for sending cancellations to the suppliers.
Also updated the FHIR Task status a little to demonstrate how the 'order-rejected' update would work.

Context

There is clarification needed between order cancellation (user-driven) and rejection (supplier-driven).
An API spec update was needed for order cancellation, and a similar update also helps to clarify how order rejection is expected to work.

Type of changes

• Refactoring (non-breaking change)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would change existing functionality)
• Bug fix (non-breaking change which fixes an issue)

Checklist

• I am familiar with the contributing guidelines
• I have followed the code style of the project
• I have added tests to cover my changes
• I have updated the documentation accordingly
• This PR is a result of pair or mob programming

---

Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

• I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

[github-actions]

🔬 FHIR Validation Results

⚠️ Validation passed with warnings — 0 error(s) · 4 warning(s) · 16 info

observation_reactive_with_contact.example.json

Severity	Location	Message
ℹ️ information	—	All OK

observation_non_reactive.example.json

Severity	Location	Message
ℹ️ information	—	All OK

observation_non_definitive_result.example.json

Severity	Location	Message
ℹ️ information	—	All OK

get_test_results_non_reactive.example.json

Severity	Location	Message
ℹ️ information	Bundle	No types could be determined from the search string, so the types can't be checked

task_update_received-at-lab.example.json

Severity	Location	Message
⚠️ warning	Task.statusReason.text	value should not start or finish with whitespace ' Test kit has been received at the lab and is being processed'
⚠️ warning	Task	Constraint failed: dom-6: 'A resource should have narrative for robust management' (defined in http://hl7.org/fhir/StructureDefinition/DomainResource) (Best Practice Recommendation)
ℹ️ information	Task.statusReason	Binding for path Task.statusReason in profile StructureDefinition[http://hl7.org/fhir/StructureDefinition/Task
ℹ️ information	Task.businessStatus	Binding for path Task.businessStatus in profile StructureDefinition[http://hl7.org/fhir/StructureDefinition/Task

observation_reactive_without_contact.example.json

Severity	Location	Message
ℹ️ information	—	All OK

ordereligibility_ineligible_operationoutcome.example.json

Severity	Location	Message
ℹ️ information	—	All OK

task_update_test-processed.example.json

Severity	Location	Message
⚠️ warning	Task.statusReason.text	value should not start or finish with whitespace ' Test kit has been processed'
⚠️ warning	Task	Constraint failed: dom-6: 'A resource should have narrative for robust management' (defined in http://hl7.org/fhir/StructureDefinition/DomainResource) (Best Practice Recommendation)
ℹ️ information	Task.statusReason	Binding for path Task.statusReason in profile StructureDefinition[http://hl7.org/fhir/StructureDefinition/Task
ℹ️ information	Task.businessStatus	Binding for path Task.businessStatus in profile StructureDefinition[http://hl7.org/fhir/StructureDefinition/Task

ordereligibility_servicerequest.example.json

Severity	Location	Message
ℹ️ information	—	All OK

task_update_dispatched.example.json

Severity	Location	Message
ℹ️ information	Task.statusReason	Binding for path Task.statusReason in profile StructureDefinition[http://hl7.org/fhir/StructureDefinition/Task
ℹ️ information	Task.businessStatus	Binding for path Task.businessStatus in profile StructureDefinition[http://hl7.org/fhir/StructureDefinition/Task

order_cancelled.example.json

Severity	Location	Message
ℹ️ information	—	All OK

order_servicerequest.example.json

Severity	Location	Message
ℹ️ information	—	All OK

operationoutcome_business_rule.example.json

Severity	Location	Message
ℹ️ information	—	All OK

Full HTML report available in the workflow run artifacts.

[trawlinson-kainos]

@ElldanLimited - I think I've managed to get the allowed businessStatus values as an enum, but it would be useful to check that's worked for you (not 100% confident in the inheritance parts of OpenAPI!).

I've also removed references to 'order rejection', and clarified in the documentation (status-transitions.md) that the Pre-Eligibility Check is where any patient eligibility decisions by the supplier will be made.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud