Profile: Procedure

Definition

The Procedure Resource is an action that is or was performed on or for a patient. This can be a physical intervention like an operation, or less invasive interventions like long term services, counseling, or hypnotherapy.

This resource is used to record the details of current and historical procedures performed on or for a patient. A procedure is an activity that is performed on, with, or for a patient as part of the provision of care. Examples include surgical procedures, diagnostic procedures, endoscopic procedures, biopsies, counseling, physiotherapy, personal support services, adult day care services, non-emergency transportation, home modification, exercise, etc. Procedures may be performed by a healthcare professional, a service provider, a friend or relative or in some cases by the patient themselves.

This resource provides summary information about the occurrence of the procedure and is not intended to provide real-time snapshots of a procedure as it unfolds, though for long-running procedures such as psychotherapy, it could represent summary level information about overall progress. The creation of a resource to support detailed real-time procedure information awaits the identification of a specific implementation use-case to share such information.

Context

The Procedure (PS-CA) profile represents the constraints applied to the Procedure resource by the PS-CA project, which is informed by the constraints of the Procedure IPS-UV profile and the Canadian Baseline Profile to allow for cross-border and cross-jurisdiction sharing of History of Procedure information.

Links

Simplifier project page: Procedure(PS-CA) Profile

Derived from: Procedure(R4) Profile

Example: PS-CA:BC Procedure

Content

idΣ0..1string
metaΣ0..1Meta
implicitRulesΣ ?!0..1uri
language0..1codeBinding
text0..1Narrative
contained0..*Resource
extensionI0..*Extension
modifierExtension?! I0..*Extension
identifierΣ0..*Identifier
instantiatesCanonicalΣ0..*canonical(PlanDefinition | ActivityDefinition | Measure | OperationDefinition | Questionnaire)
instantiatesUriΣ0..*uri
basedOnΣ I0..*Reference(CarePlan | ServiceRequest)
partOfΣ I0..*Reference(Procedure | Observation | MedicationAdministration)
statusS Σ ?!1..1codeBinding
statusReasonΣ0..1CodeableConcept
categoryΣ0..1CodeableConcept
codeS Σ1..1CodeableConceptPSCABinding
id0..1string
extensionI0..*Extension
referenceS Σ I1..1string
typeΣ0..1uriBinding
identifierΣ0..1Identifier
displayΣ0..1string
encounterΣ I0..1Reference(Encounter)
id0..1string
data-absent-reasonI0..1Extension(code)
performedDateTimedateTime
performedPeriodPeriod
performedStringstring
performedAgeAge
performedRangeRange
recorderΣ I0..1Reference(Patient | RelatedPerson | Practitioner | PractitionerRole)
asserterΣ I0..1Reference(Patient | RelatedPerson | Practitioner | PractitionerRole)
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
functionΣ0..1CodeableConcept
actorΣ I1..1Reference(Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | Device)
onBehalfOfI0..1Reference(Organization)
locationΣ I0..1Reference(Location)
reasonCodeΣ0..*CodeableConcept
reasonReferenceΣ I0..*Reference(Condition | Observation | Procedure | DiagnosticReport | DocumentReference)
bodySiteΣ0..*CodeableConceptPSCABinding
outcomeΣ0..1CodeableConcept
reportI0..*Reference(DiagnosticReport | DocumentReference | Composition)
complication0..*CodeableConcept
complicationDetailI0..*Reference(Condition)
followUp0..*CodeableConcept
note0..*Annotation
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
action0..1CodeableConceptBinding
manipulatedI1..1Reference(Device)
usedReferenceI0..*Reference(Device | Medication | Substance)
usedCode0..*CodeableConcept

 

Usage

The Procedure Resource is used to populate entries in the Procedure section of a Patient Summary. The data source will be the Provider EMR.

BC-specific Notes

Procedures (Composition.section:sectionProceduresHx)

  • Definition: An action that is or was performed on or for a patient. This can be a physical intervention like an operation, or less invasive like long term services, counseling, or hypnotherapy.

Procedure.code

  • Definition: Identification of the procedure or recording of "absence of relevant procedures" or of "procedures unknown".
  • Comments: Must Support and Required.

Procedure.performed[x].DateTime

  • Definition: Estimated or actual date, date-time, period, or age when the procedure was performed. Allows a period to support complex procedures that span more than one date, and also allows for the length of the procedure to be captured.
  • Comments: Must Support and Required. Date elements are displayed in the format YYYY/MM/DD. There is a stipulation that Procedures entries must be sorted based on their Performed Dates in descending chronological order, such that entries with the most recent performed dates are positioned at the top, while older ones are placed at the bottom.

Procedure.status

  • Definition: A code specifying the state of the procedure. Generally, this will be the in-progress or completed state.
  • Comments: Must Support and Required. This element includes one value: Confirmed, which is a fixed value at a system level. This field need not be shown at the UI level and is currently not planned to be shown in the PS-CA:BC Patient Summary.

Procedure.section-note

  • Definition: Any other notes and comments about the procedure.
  • Comments: Optional with multiples value. This is a Free Text string element at Each Entry, which can be utilized to include additional information regarding each Procedure entry.

Data Fields Mapping (PS-Form & FHIR Profile)

PS Form Fields FHIR Profile Elements
Procedure Procedure.code
Date Performed Procedure.performed[x].DateTime
Status (Hidden) Procedure.status
Notes (Free Text) at Each Entry Procedure.note