ProcedureOccurrence
type: StructureDefinition
node role: treeRoot
id:
  v: ProcedureOccurrence
language:
  v: en
text:
  status:
    v: extensions
  div:
    v: Generated Narrative: StructureDefinition ProcedureOccurrence Language: en Name Flags Card. Type Description & Constraints<img src="[binary]" alt="doco" style="background-color: inherit"/> ProcedureOccurrence 0..* Base Procedure Occurrence OMOP Table Instances of this logical model can be the target of a Reference #xD; procedure_occurrence_id 1..1 integer Procedure Occurrence Identifier #xD; person_id 1..1 Reference(Person OMOP Table) Person #xD; procedure_concept_id 1..1 code Procedure #xD; procedure_date 1..1 date Procedure Date #xD; procedure_datetime 0..1 dateTime Procedure Datetime #xD; procedure_end_date 0..1 date Procedure End Date #xD; procedure_end_datetime 0..1 dateTime procedure_end_datetime #xD; procedure_type_concept_id 1..1 code Procedure Type #xD; modifier_concept_id 0..1 code Modifier #xD; quantity 0..1 integer Quantity #xD; provider_id 0..1 Reference(Provider OMOP Table) Provider #xD; visit_occurrence_id 0..1 Reference(Visit Occurrence OMOP Table) VisitOccurrence #xD; visit_detail_id 0..1 Reference(Visit Detail OMOP Table) Visit Detail #xD; procedure_source_value 0..1 string Procedure Source Value #xD; <a href="StructureDefinition-ProcedureOccurrence-definitions.html#ProcedureOccurrence.procedure-source-concept-id" title="This is the concept representing the procedure source value and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Procedure necessary for a given analytic use case. Consider using PROCEDURE_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.">procedure_source_concept_id 0..1 code Procedure Source Concept #xD; modifier_source_value 0..1 string Modifier Source Value #xD; <img src="[binary]" alt="doco" style="background-color: inherit"/> Documentation for this format
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-type-characteristics
    l: structuredefinition-type-characteristics
  value: Code
    v: can-be-target
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-wg
    l: structuredefinition-wg
  value: Code
    v: brr
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm
    l: structuredefinition-fmm
  value: Integer
    v: 1
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/omop/ImplementationGuide/hl7.fhir.uv.omop
        l: hl7.fhir.uv.omop
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
    l: structuredefinition-standards-status
  value: Code
    v: informative
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/omop/ImplementationGuide/hl7.fhir.uv.omop
        l: hl7.fhir.uv.omop
url:
  v: http://hl7.org/fhir/uv/omop/StructureDefinition/ProcedureOccurrence
  l: ProcedureOccurrence
version:
  v: 1.0.0
name:
  v: ProcedureOccurrence
title:
  v: Procedure Occurrence OMOP Table
status:
  v: active
date:
  v: 2026-02-12T17:30:34+00:00
publisher:
  v: HL7 International / Biomedical Research and Regulation
contact:
  name:
    v: HL7 International / Biomedical Research and Regulation
  telecom:
    system:
      v: url
    value:
      v: http://www.hl7.org/Special/committees/rcrim
description:
  v: This table contains records of activities or processes ordered by, or carried out by, a healthcare provider on the patient with a diagnostic or therapeutic purpose.
jurisdiction:
  coding:
    system:
      v: http://unstats.un.org/unsd/methods/m49/m49.htm
      l: m49.htm
    code:
      v: 001
    display:
      v: World
fhir version:
  v: 5.0.0
mapping:
  identity:
    v: rim
  uri:
    v: http://hl7.org/v3
    l: v3
  name:
    v: RIM Mapping
kind:
  v: logical
abstract:
  v: false
type:
  v: http://hl7.org/fhir/uv/omop/StructureDefinition/ProcedureOccurrence
  l: ProcedureOccurrence
base definition:
  v: http://hl7.org/fhir/StructureDefinition/Base
  l: Base
derivation:
  v: specialization
snapshot:
  extension:
    url:
      v: http://hl7.org/fhir/tools/StructureDefinition/snapshot-base-version
      l: snapshot-base-version
    value: String
      v: 5.0.0
  element:
    id:
      v: ProcedureOccurrence
    path:
      v: ProcedureOccurrence
    short:
      v: Procedure Occurrence OMOP Table
    definition:
      v: This table contains records of activities or processes ordered by, or carried out by, a healthcare provider on the patient with a diagnostic or therapeutic purpose.
    min:
      v: 0
    max:
      v: *
    base:
      path:
        v: Base
      min:
        v: 0
      max:
        v: *
    is modifier:
      v: false
    mapping:
      identity:
        v: rim
      map:
        v: n/a
  element:
    id:
      v: ProcedureOccurrence.procedure-occurrence-id
    path:
      v: ProcedureOccurrence.procedure_occurrence_id
    short:
      v: Procedure Occurrence Identifier
    definition:
      v: The unique key given to a procedure record for a person. Refer to the ETL for how duplicate procedures during the same visit were handled.
    min:
      v: 1
    max:
      v: 1
    base:
      path:
        v: ProcedureOccurrence.procedure_occurrence_id
      min:
        v: 1
      max:
        v: 1
    type:
      code:
        v: integer
        l: integer
  element:
    id:
      v: ProcedureOccurrence.person-id
    path:
      v: ProcedureOccurrence.person_id
    short:
      v: Person
    definition:
      v: The PERSON_ID of the PERSON for whom the procedure is recorded. This may be a system generated code.
    min:
      v: 1
    max:
      v: 1
    base:
      path:
        v: ProcedureOccurrence.person_id
      min:
        v: 1
      max:
        v: 1
    type:
      code:
        v: Reference
        l: Reference
      target profile:
        v: http://hl7.org/fhir/uv/omop/StructureDefinition/Person
        l: Person
  element:
    id:
      v: ProcedureOccurrence.procedure-concept-id
    path:
      v: ProcedureOccurrence.procedure_concept_id
    short:
      v: Procedure
    definition:
      v: The PROCEDURE_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies. This is the standard concept mapped from the source value which represents a procedure
    min:
      v: 1
    max:
      v: 1

path:
  v: ProcedureOccurrence.procedure_concept_id
min:
  v: 1
max:
  v: 1

code:
  v: code
  l: code

id:
  v: ProcedureOccurrence.procedure-date
path:
  v: ProcedureOccurrence.procedure_date
short:
  v: Procedure Date
definition:
  v: Use this date to determine the date the procedure started.
min:
  v: 1
max:
  v: 1
base:
  path:
    v: ProcedureOccurrence.procedure_date
  min:
    v: 1
  max:
    v: 1
type:
  code:
    v: date
    l: date

id:
  v: ProcedureOccurrence.procedure-datetime
path:
  v: ProcedureOccurrence.procedure_datetime
short:
  v: Procedure Datetime
definition:
  v: Procedure Datetime
min:
  v: 0
max:
  v: 1
base:
  path:
    v: ProcedureOccurrence.procedure_datetime
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: dateTime
    l: dateTime

id:
  v: ProcedureOccurrence.procedure-end-date
path:
  v: ProcedureOccurrence.procedure_end_date
short:
  v: Procedure End Date
definition:
  v: Use this field to house the date that the procedure ended.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: ProcedureOccurrence.procedure_end_date
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: date
    l: date

id:
  v: ProcedureOccurrence.procedure-end-datetime
path:
  v: ProcedureOccurrence.procedure_end_datetime
short:
  v: procedure_end_datetime
definition:
  v: Use this field to house the datetime that the procedure ended.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: ProcedureOccurrence.procedure_end_datetime
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: dateTime
    l: dateTime

id:
  v: ProcedureOccurrence.procedure-type-concept-id
path:
  v: ProcedureOccurrence.procedure_type_concept_id
short:
  v: Procedure Type
definition:
  v: This field can be used to determine the provenance of the Procedure record, as in whether the procedure was from an EHR system, insurance claim, registry, or other sources.
min:
  v: 1
max:
  v: 1
base:
  path:
    v: ProcedureOccurrence.procedure_type_concept_id
  min:
    v: 1
  max:
    v: 1
type:
  code:
    v: code
    l: code

id:
  v: ProcedureOccurrence.modifier-concept-id
path:
  v: ProcedureOccurrence.modifier_concept_id
short:
  v: Modifier
definition:
  v: The modifiers are intended to give additional information about the procedure but as of now the vocabulary is under review.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: ProcedureOccurrence.modifier_concept_id
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: code
    l: code

id:
  v: ProcedureOccurrence.quantity
path:
  v: ProcedureOccurrence.quantity
short:
  v: Quantity
definition:
  v: If the quantity value is omitted, a single procedure is assumed.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: ProcedureOccurrence.quantity
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: integer
    l: integer

id:
  v: ProcedureOccurrence.provider-id
path:
  v: ProcedureOccurrence.provider_id
short:
  v: Provider
definition:
  v: The provider associated with the procedure record, e.g. the provider who performed the Procedure.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: ProcedureOccurrence.provider_id
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: Reference
    l: Reference
  target profile:
    v: http://hl7.org/fhir/uv/omop/StructureDefinition/Provider
    l: Provider

id:
  v: ProcedureOccurrence.visit-occurrence-id
path:
  v: ProcedureOccurrence.visit_occurrence_id
short:
  v: VisitOccurrence
definition:
  v: The visit during which the procedure occurred.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: ProcedureOccurrence.visit_occurrence_id
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: Reference
    l: Reference
  target profile:
    v: http://hl7.org/fhir/uv/omop/StructureDefinition/VisitOccurrence
    l: VisitOccurrence

id:
  v: ProcedureOccurrence.visit-detail-id
path:
  v: ProcedureOccurrence.visit_detail_id
short:
  v: Visit Detail
definition:
  v: The VISIT_DETAIL record during which the Procedure occurred. For example, if the Person was in the ICU at the time of the Procedure the VISIT_OCCURRENCE record would reflect the overall hospital stay and the VISIT_DETAIL record would reflect the ICU stay during the hospital visit.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: ProcedureOccurrence.visit_detail_id
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: Reference
    l: Reference
  target profile:
    v: http://hl7.org/fhir/uv/omop/StructureDefinition/VisitDetail
    l: VisitDetail

id:
  v: ProcedureOccurrence.procedure-source-value
path:
  v: ProcedureOccurrence.procedure_source_value
short:
  v: Procedure Source Value
definition:
  v: This field houses the verbatim value from the source data representing the procedure that occurred. For example, this could be an CPT4 or OPCS4 code.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: ProcedureOccurrence.procedure_source_value
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: string
    l: string

id:
  v: ProcedureOccurrence.procedure-source-concept-id
path:
  v: ProcedureOccurrence.procedure_source_concept_id
short:
  v: Procedure Source Concept
definition:
  v: This is the concept representing the procedure source value and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Procedure necessary for a given analytic use case. Consider using PROCEDURE_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: ProcedureOccurrence.procedure_source_concept_id
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: code
    l: code

id:
  v: ProcedureOccurrence.modifier-source-value
path:
  v: ProcedureOccurrence.modifier_source_value
short:
  v: Modifier Source Value
definition:
  v: Modifier Source Value
min:
  v: 0
max:
  v: 1
base:
  path:
    v: ProcedureOccurrence.modifier_source_value
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: string
    l: string

element:
  id:
    v: ProcedureOccurrence
  path:
    v: ProcedureOccurrence
  short:
    v: Procedure Occurrence OMOP Table
  definition:
    v: This table contains records of activities or processes ordered by, or carried out by, a healthcare provider on the patient with a diagnostic or therapeutic purpose.
element:
  id:
    v: ProcedureOccurrence.procedure-occurrence-id
  path:
    v: ProcedureOccurrence.procedure_occurrence_id
  short:
    v: Procedure Occurrence Identifier
  definition:
    v: The unique key given to a procedure record for a person. Refer to the ETL for how duplicate procedures during the same visit were handled.
  min:
    v: 1
  max:
    v: 1
  type:
    code:
      v: integer
      l: integer
element:
  id:
    v: ProcedureOccurrence.person-id
  path:
    v: ProcedureOccurrence.person_id
  short:
    v: Person
  definition:
    v: The PERSON_ID of the PERSON for whom the procedure is recorded. This may be a system generated code.
  min:
    v: 1
  max:
    v: 1
  type:
    code:
      v: Reference
      l: Reference
    target profile:
      v: http://hl7.org/fhir/uv/omop/StructureDefinition/Person
      l: Person
element:
  id:
    v: ProcedureOccurrence.procedure-concept-id
  path:
    v: ProcedureOccurrence.procedure_concept_id
  short:
    v: Procedure
  definition:
    v: The PROCEDURE_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies. This is the standard concept mapped from the source value which represents a procedure
  min:
    v: 1
  max:
    v: 1
  type:
    code:
      v: code
      l: code
element:
  id:
    v: ProcedureOccurrence.procedure-date
  path:
    v: ProcedureOccurrence.procedure_date
  short:
    v: Procedure Date
  definition:
    v: Use this date to determine the date the procedure started.
  min:
    v: 1
  max:
    v: 1
  type:
    code:
      v: date
      l: date
element:
  id:
    v: ProcedureOccurrence.procedure-datetime
  path:
    v: ProcedureOccurrence.procedure_datetime
  short:
    v: Procedure Datetime
  definition:
    v: Procedure Datetime
  min:
    v: 0
  max:
    v: 1
  type:
    code:
      v: dateTime
      l: dateTime
element:
  id:
    v: ProcedureOccurrence.procedure-end-date
  path:
    v: ProcedureOccurrence.procedure_end_date
  short:
    v: Procedure End Date
  definition:
    v: Use this field to house the date that the procedure ended.
  min:
    v: 0
  max:
    v: 1
  type:
    code:
      v: date
      l: date
element:
  id:
    v: ProcedureOccurrence.procedure-end-datetime
  path:
    v: ProcedureOccurrence.procedure_end_datetime
  short:
    v: procedure_end_datetime
  definition:
    v: Use this field to house the datetime that the procedure ended.
  min:
    v: 0
  max:
    v: 1
  type:
    code:
      v: dateTime
      l: dateTime
element:
  id:
    v: ProcedureOccurrence.procedure-type-concept-id
  path:
    v: ProcedureOccurrence.procedure_type_concept_id
  short:
    v: Procedure Type
  definition:
    v: This field can be used to determine the provenance of the Procedure record, as in whether the procedure was from an EHR system, insurance claim, registry, or other sources.
  min:
    v: 1
  max:
    v: 1
  type:
    code:
      v: code
      l: code
element:
  id:
    v: ProcedureOccurrence.modifier-concept-id
  path:
    v: ProcedureOccurrence.modifier_concept_id
  short:
    v: Modifier
  definition:
    v: The modifiers are intended to give additional information about the procedure but as of now the vocabulary is under review.
  min:
    v: 0
  max:
    v: 1
  type:
    code:
      v: code
      l: code
element:
  id:
    v: ProcedureOccurrence.quantity
  path:
    v: ProcedureOccurrence.quantity
  short:
    v: Quantity
  definition:
    v: If the quantity value is omitted, a single procedure is assumed.
  min:
    v: 0
  max:
    v: 1
  type:
    code:
      v: integer
      l: integer
element:
  id:
    v: ProcedureOccurrence.provider-id
  path:
    v: ProcedureOccurrence.provider_id
  short:
    v: Provider
  definition:
    v: The provider associated with the procedure record, e.g. the provider who performed the Procedure.
  min:
    v: 0
  max:
    v: 1
  type:
    code:
      v: Reference
      l: Reference
    target profile:
      v: http://hl7.org/fhir/uv/omop/StructureDefinition/Provider
      l: Provider

id:
  v: ProcedureOccurrence.visit-occurrence-id
path:
  v: ProcedureOccurrence.visit_occurrence_id
short:
  v: VisitOccurrence
definition:
  v: The visit during which the procedure occurred.
min:
  v: 0
max:
  v: 1
type:
  code:
    v: Reference
    l: Reference
  target profile:
    v: http://hl7.org/fhir/uv/omop/StructureDefinition/VisitOccurrence
    l: VisitOccurrence

id:
  v: ProcedureOccurrence.visit-detail-id
path:
  v: ProcedureOccurrence.visit_detail_id
short:
  v: Visit Detail
definition:
  v: The VISIT_DETAIL record during which the Procedure occurred. For example, if the Person was in the ICU at the time of the Procedure the VISIT_OCCURRENCE record would reflect the overall hospital stay and the VISIT_DETAIL record would reflect the ICU stay during the hospital visit.
min:
  v: 0
max:
  v: 1
type:
  code:
    v: Reference
    l: Reference
  target profile:
    v: http://hl7.org/fhir/uv/omop/StructureDefinition/VisitDetail
    l: VisitDetail

id:
  v: ProcedureOccurrence.procedure-source-value
path:
  v: ProcedureOccurrence.procedure_source_value
short:
  v: Procedure Source Value
definition:
  v: This field houses the verbatim value from the source data representing the procedure that occurred. For example, this could be an CPT4 or OPCS4 code.
min:
  v: 0
max:
  v: 1
type:
  code:
    v: string
    l: string

id:
  v: ProcedureOccurrence.procedure-source-concept-id
path:
  v: ProcedureOccurrence.procedure_source_concept_id
short:
  v: Procedure Source Concept
definition:
  v: This is the concept representing the procedure source value and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Procedure necessary for a given analytic use case. Consider using PROCEDURE_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.
min:
  v: 0
max:
  v: 1
type:
  code:
    v: code
    l: code

id:
  v: ProcedureOccurrence.modifier-source-value
path:
  v: ProcedureOccurrence.modifier_source_value
short:
  v: Modifier Source Value
definition:
  v: Modifier Source Value
min:
  v: 0
max:
  v: 1
type:
  code:
    v: string
    l: string