CareConnect-CDS-Procedure-1

This is the StructureDefinition overview for the CareConnect-CDS-Procedure-1

The official URL for this profile is: https://fhir.nottinghamshire.gov.uk/STU3/StructureDefinition/CareConnect-CDS-Procedure-1

Differential

Command 'tree' could not render: Sequence contains more than one element

Hybrid

Command 'tree' could not render: Sequence contains more than one element

Snapshot (default)

Command 'tree' could not render: Sequence contains more than one element



Procedure Data Mapping

The table below provides the business context data mappings for the 'Mandatory' and 'Must Support' elements in the CareConnect-CDS-Procedure-1 profile. The CareConnect-CDS-Procedure-1 profile is used to share details of the Primary Support Reason which is used to classify a Patient for National Reporting on Short and Long Term Services (SALT).

FHIR Element Card. Type Description/Business Context
Procedure.id 1..1 id Logical id of Primary Support Reason from Social Care System and used for referencing resource within the Bundle
Procedure.status 1..1 code Binding EventStatus

preparation | in-progress | suspended | aborted | completed | entered-in-error | unknown
Procedure.category 1..1 CodeableConcept Classification of the procedure
Procedure.category.coding 1..1 Coding A reference to a code defined by a terminology system
Procedure.category.coding.system 1..1 uri Fixed Value http://snomed.info/sct
Procedure.category.coding.code 1..1 code Fixed Value 299751000000102
Procedure.category.coding.display 1..1 string Fixed Value Social services procedure
Procedure.subject 1..1 Reference (CareConnect-CDS-Patient-1) Reference to Patient resource who has this Primary Support Reason.
Procedure.performedPeriod 1..1 Period Only the current Primary Support Reason will be shared, therefore implementers MUST SUPPORT Procedure.performedPeriod so that any start and end dates of the Primary Support Reason can be communicated
Procedure.performedPeriod.start 1..1 dateTime Date the patient actually started to receive the service/package
Procedure.performedPeriod.end 0..1 dateTime Date the patient actually started to receive the service/package
Procedure.reasonCode 1..1 CodeableConcept Detail of the Support Reason. Note each support reason should be shared as as seperate procedure (with its effetive dates. Multiple reasonCode.codings are allowed, including the supportReason (see below) and local system codings which identify groups and sub-groups. However reasonCode.text should correspond to the official reasons for national reporting where possible
Procedure.reasonCode.coding 0..* Coding Any reference to a code defined by a local / offical system
Procedure.reasonCode.coding[supportReason] 0..1 Coding Offical reasons used for national reporting on Short and Long Term Activity (SALT). Where possible providers should map local codes to this.

Binding Social Care Support Reason
Procedure.reasonCode.coding[supportReason].system 1..1 uri Fixed value http://example.org/fhir/codesystem/CDS-SocialCareSupportReason

MUST be provided for Procedure.reasonCode.coding[supportReason]
Procedure.reasonCode.coding[supportReason].code 1..1 code MUST be provided for Procedure.reasonCode.coding[supportReason]
Procedure.reasonCode.coding[supportReason].display 1..1 string MUST be provided for Procedure.reasonCode.coding[supportReason]
Procedure.reasonCode.text 1..1 string Plain text representation of offical reporting reason i.e.

Learning Disability Support | Mental Health Support | Physical Support | Sensory Support | Social Support |Support with Memory and Cognition
Procedure.reasonCode.extension[cds-PrimarySupportReasonFlag] 0..1 Extension Boolean flag to indicate that the support reason is the primary support reason

Constraint the patient SHOULD only every have one support reason that the primary one at any point in time.