Procedure (PS-CA)


This version of the PS-CA Implementation Guide has been superseded by a newer version. A full list of versions & releases of the PS-CA Implementation Guide may be found at Guides.


Additional information on this profile (including the JSON & XML structure and detailed element descriptions) can be found at Procedure (PS-CA)

Profile

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
codeSCTCAΣ0..1CodeableConceptBinding
absentOrUnknownProcedureS Σ0..1CodeableConceptBinding
referenceS Σ I1..1string
typeΣ0..1uriBinding
identifierΣ0..1Identifier
displayΣ0..1string
encounterΣ I0..1Reference(Encounter)
data-absent-reasonS I0..1Extension(code)
performedDateTimedateTime
performedPeriodPeriod
performedStringstring
performedAgeAge
performedRangeRange
recorderΣ I0..1Reference(Patient | RelatedPerson | Practitioner | PractitionerRole)
asserterΣ I0..1Reference(Patient | RelatedPerson | Practitioner | PractitionerRole)
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..*Data Type: Codeable Concept (PS-CA)Binding
outcomeΣ0..1CodeableConcept
reportI0..*Reference(DiagnosticReport | DocumentReference | Composition)
complication0..*CodeableConcept
complicationDetailI0..*Reference(Condition)
followUp0..*CodeableConcept
note0..*Annotation
action0..1CodeableConceptBinding
manipulatedI1..1Reference(Device)
usedReferenceI0..*Reference(Device | Medication | Substance)
usedCode0..*CodeableConcept

Extensions

This profile uses the following extensions:

Key Differences between the IPS-UV and PS-CA

Must Support Differences:

The following elements are considered "must support" in the IPS-UV specification that are relaxed in this version of the PS-CA profile:

  • Procedure.bodySite

    Note: Systems that support these elements are encouraged to send them in patient summaries

Cardinality Differences:

There are no cardinality differences between this profile and IPS-UV

Vocabulary Differences:

  • Procedure.code: slice added for SNOMED CT Canadian Edition procedure codes
  • Procedure.bodySite:
    • SNOMED CT Canadian Edition anatomical regions
    • binding strengthened to preferred

Other differences between the IPS and PS-CA Include:

  • Procedure.code: IPS datatype profile replaced with PS-CA profile
  • Procedure.subject: reference target changed to PS-CA patient
  • Procedure.performer.actor: removed profiling
  • Procedure performer.onBehalfOf: removed profiling