Search loading...

API Hub

Explore and Make use of Nationally Defined Messaging APIs

 

Procedure Request Implementation Guidance

ProcedureRequest resource implementation guidance

ProcedureRequest: Implementation Guidance

Usage

Within the Clinical Decision Support API implementation, the ProcedureRequest resource will be used to carry the next activity as part of the triage outcome model.

The ProcedureRequest is referenced from ReferralRequest.supportingInfo and will be the diagnostic discriminator, or service requirement; diagnostic discriminator is a description of the next procedure which SHOULD be carried out in the referee service to validate or eliminate the chief concern.

Detailed implementation guidance for a ProcedureRequest within the scope of this implementation guide is given below:

Name Cardinality Type FHIR Documentation CDS Implementation Guidance
identifier 0..1 Identifier Identifiers assigned to this order
definition 0..* Reference
(ActivityDefinition |
PlanDefinition)
Protocol or definition
basedOn 0..* Reference
(Any)
What request fulfils This MUST NOT be populated.
replaces 0..* Reference
(Any)
What request replaces
requisition 0..1 Identifier Composite Request ID This MUST NOT be populated.
status 1..1 code draft | active | suspended | completed | entered-in-error | cancelled RequestStatus (Required) This MUST be populated with the same value as ReferralRequest.status
intent 1..1 code proposal | plan | order + RequestIntent (Required) This MUST be populated with the same value as ReferralRequest.intent
priority 0..1 code routine | urgent | asap | stat RequestPriority (Required) This MUST be populated with 'routine'.
doNotPerform 0..1 boolean True if procedure should not be performed This MUST be 'false'
category 0..* CodeableConcept Classification of procedure Procedure Category Codes (SNOMED CT) (Example) This SHOULD NOT be populated
code 1..1 CodeableConcept What is being requested/ordered Procedure Codes (SNOMED CT) (Example) This MUST be populated by the CDSS with a code that identifies the particular procedure which has been requested.
subject 1..1 Reference
(Patient |
Group |
Location |
Device)
Individual the service is ordered for This MUST be populated with a reference to the Patient resource.
context 0..1 Reference
(Encounter |
EpisodeOfCare)
Encounter or Episode during which request was created This MUST be populated with a reference to the Encounter supplied in the ServiceDefinition.$evaluate operation.
occurrence[x] 0..1 dateTime |
Period |
Timing
When procedure should occur This MUST be populated with the same value as ReferralRequest.occurrence
asNeeded[x] 0..1 boolean |
CodeableConcept
Preconditions for procedure or diagnostic SNOMED CT Medication As Needed Reason Codes (Example) This MUST NOT be populated
authoredOn 0..1 dateTime Date request signed This MUST NOT be populated
requester 0..1 BackboneElement Who/what is requesting procedure or diagnostic This MUST NOT be populated
performerType 0..1 CodeableConcept Performer role Participant Roles (Example) This MAY be populated
performer 0..1 Reference
(Practitioner |
Organization |
Patient |
Device |
RelatedPerson |
HealthcareService)
Requested perfomer This MAY be populated
reasonCode 0..* CodeableConcept Explanation/Justification for test Procedure Reason Codes (Example) This MUST not be populated
reasonReference 0..* Reference
(Condition |
Observation)
Explanation/Justification for test This MUST be populated with the same value as ReferralRequest.reasonReference
supportingInfo 0..* Reference
(Any)
Additional clinical information This MUST be populated with the same value as ReferralRequest.supportinInfo
specimen 0..* Reference
(Specimen)
Procedure Samples This MUST NOT be populated
bodySite 0..* CodeableConcept Location on Body SNOMED CT Body Structures (Example) This MAY be populated
note 0..* Annotation Comments This MUST NOT be populated
relevantHistory 0..* Reference
(Provenance)
Request provenance This MUST be populated with the same value as ReferralRequest.relevantHistory
Tags: rest fhir api

All content is available under the Open Government Licence v3.0, except where otherwise stated