Guide d'implémentation du GT Standards et Interopérabilité pour les EDS
0.1.0 - ci-build
Guide d'implémentation du GT Standards et Interopérabilité pour les EDS - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
Draft as of 2024-10-08 |
Definitions for the OMOPProcedureOccurrence logical model.
Guidance on how to interpret the contents of this table can be found here
0. OMOPProcedureOccurrence | |
Definition | 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. |
Short | Procedure Occurrence OMOP Table |
Logical Model | Instances of this logical model are not marked to be the target of a Reference |
2. OMOPProcedureOccurrence.procedure-occurrence-id | |
Definition | 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. |
Short | Procedure Occurrence Identifier |
Control | 1..1 |
Type | integer |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
4. OMOPProcedureOccurrence.person-id | |
Definition | The PERSON_ID of the PERSON for whom the procedure is recorded. This may be a system generated code. |
Short | Person |
Control | 1..1 |
Type | Reference(Person OMOP Table) |
6. OMOPProcedureOccurrence.procedure-concept-id | |
Definition | 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 |
Short | Procedure |
Control | 1..1 |
Type | Reference(Concept OMOP Table) |
8. OMOPProcedureOccurrence.procedure-date | |
Definition | Use this date to determine the date the procedure started. |
Short | Procedure Date |
Control | 1..1 |
Type | date |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
10. OMOPProcedureOccurrence.procedure-datetime | |
Definition | Procedure Datetime |
Short | Procedure Datetime |
Control | 0..1 |
Type | dateTime |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
12. OMOPProcedureOccurrence.procedure-end-date | |
Definition | Use this field to house the date that the procedure ended. |
Short | Procedure End Date |
Control | 0..1 |
Type | date |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
14. OMOPProcedureOccurrence.procedure-end-datetime | |
Definition | Use this field to house the datetime that the procedure ended. |
Short | procedure_end_datetime |
Control | 0..1 |
Type | dateTime |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
16. OMOPProcedureOccurrence.procedure-type-concept-id | |
Definition | 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. |
Short | Procedure Type |
Control | 1..1 |
Type | Reference(Concept OMOP Table) |
18. OMOPProcedureOccurrence.modifier-concept-id | |
Definition | The modifiers are intended to give additional information about the procedure but as of now the vocabulary is under review. |
Short | Modifier |
Control | 0..1 |
Type | Reference(Concept OMOP Table) |
20. OMOPProcedureOccurrence.quantity | |
Definition | If the quantity value is omitted, a single procedure is assumed. |
Short | Quantity |
Control | 0..1 |
Type | integer |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
22. OMOPProcedureOccurrence.provider-id | |
Definition | The provider associated with the procedure record, e.g. the provider who performed the Procedure. |
Short | Provider |
Control | 0..1 |
Type | Reference(Provider OMOP Table) |
24. OMOPProcedureOccurrence.visit-occurrence-id | |
Definition | The visit during which the procedure occurred. |
Short | VisitOccurrence |
Control | 0..1 |
Type | Reference(Visit Occurrence OMOP Table) |
26. OMOPProcedureOccurrence.visit-detail-id | |
Definition | 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. |
Short | Visit Detail |
Control | 0..1 |
Type | Reference(Visit Detail OMOP Table) |
28. OMOPProcedureOccurrence.procedure-source-value | |
Definition | 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. |
Short | Procedure Source Value |
Control | 0..1 |
Type | string |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
30. OMOPProcedureOccurrence.procedure-source-concept-id | |
Definition | 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. |
Short | Procedure Source Concept |
Control | 0..1 |
Type | Reference(Concept OMOP Table) |
32. OMOPProcedureOccurrence.modifier-source-value | |
Definition | Modifier Source Value |
Short | Modifier Source Value |
Control | 0..1 |
Type | string |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
Guidance on how to interpret the contents of this table can be found here
0. OMOPProcedureOccurrence | |
Definition | 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. |
Short | Procedure Occurrence OMOP Table |
Control | 0..* |
Is Modifier | false |
Logical Model | Instances of this logical model are not marked to be the target of a Reference |
2. OMOPProcedureOccurrence.procedure-occurrence-id | |
Definition | 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. |
Short | Procedure Occurrence Identifier |
Control | 1..1 |
Type | integer |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
4. OMOPProcedureOccurrence.person-id | |
Definition | The PERSON_ID of the PERSON for whom the procedure is recorded. This may be a system generated code. |
Short | Person |
Control | 1..1 |
Type | Reference(Person OMOP Table) |
6. OMOPProcedureOccurrence.procedure-concept-id | |
Definition | 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 |
Short | Procedure |
Control | 1..1 |
Type | Reference(Concept OMOP Table) |
8. OMOPProcedureOccurrence.procedure-date | |
Definition | Use this date to determine the date the procedure started. |
Short | Procedure Date |
Control | 1..1 |
Type | date |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
10. OMOPProcedureOccurrence.procedure-datetime | |
Definition | Procedure Datetime |
Short | Procedure Datetime |
Control | 0..1 |
Type | dateTime |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
12. OMOPProcedureOccurrence.procedure-end-date | |
Definition | Use this field to house the date that the procedure ended. |
Short | Procedure End Date |
Control | 0..1 |
Type | date |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
14. OMOPProcedureOccurrence.procedure-end-datetime | |
Definition | Use this field to house the datetime that the procedure ended. |
Short | procedure_end_datetime |
Control | 0..1 |
Type | dateTime |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
16. OMOPProcedureOccurrence.procedure-type-concept-id | |
Definition | 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. |
Short | Procedure Type |
Control | 1..1 |
Type | Reference(Concept OMOP Table) |
18. OMOPProcedureOccurrence.modifier-concept-id | |
Definition | The modifiers are intended to give additional information about the procedure but as of now the vocabulary is under review. |
Short | Modifier |
Control | 0..1 |
Type | Reference(Concept OMOP Table) |
20. OMOPProcedureOccurrence.quantity | |
Definition | If the quantity value is omitted, a single procedure is assumed. |
Short | Quantity |
Control | 0..1 |
Type | integer |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
22. OMOPProcedureOccurrence.provider-id | |
Definition | The provider associated with the procedure record, e.g. the provider who performed the Procedure. |
Short | Provider |
Control | 0..1 |
Type | Reference(Provider OMOP Table) |
24. OMOPProcedureOccurrence.visit-occurrence-id | |
Definition | The visit during which the procedure occurred. |
Short | VisitOccurrence |
Control | 0..1 |
Type | Reference(Visit Occurrence OMOP Table) |
26. OMOPProcedureOccurrence.visit-detail-id | |
Definition | 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. |
Short | Visit Detail |
Control | 0..1 |
Type | Reference(Visit Detail OMOP Table) |
28. OMOPProcedureOccurrence.procedure-source-value | |
Definition | 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. |
Short | Procedure Source Value |
Control | 0..1 |
Type | string |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
30. OMOPProcedureOccurrence.procedure-source-concept-id | |
Definition | 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. |
Short | Procedure Source Concept |
Control | 0..1 |
Type | Reference(Concept OMOP Table) |
32. OMOPProcedureOccurrence.modifier-source-value | |
Definition | Modifier Source Value |
Short | Modifier Source Value |
Control | 0..1 |
Type | string |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
Guidance on how to interpret the contents of this table can be found here
0. OMOPProcedureOccurrence | |
Definition | 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. |
Short | Procedure Occurrence OMOP Table |
Control | 0..* |
Is Modifier | false |
Logical Model | Instances of this logical model are not marked to be the target of a Reference |
2. OMOPProcedureOccurrence.procedure-occurrence-id | |
Definition | 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. |
Short | Procedure Occurrence Identifier |
Control | 1..1 |
Type | integer |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
4. OMOPProcedureOccurrence.person-id | |
Definition | The PERSON_ID of the PERSON for whom the procedure is recorded. This may be a system generated code. |
Short | Person |
Control | 1..1 |
Type | Reference(Person OMOP Table) |
6. OMOPProcedureOccurrence.procedure-concept-id | |
Definition | 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 |
Short | Procedure |
Control | 1..1 |
Type | Reference(Concept OMOP Table) |
8. OMOPProcedureOccurrence.procedure-date | |
Definition | Use this date to determine the date the procedure started. |
Short | Procedure Date |
Control | 1..1 |
Type | date |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
10. OMOPProcedureOccurrence.procedure-datetime | |
Definition | Procedure Datetime |
Short | Procedure Datetime |
Control | 0..1 |
Type | dateTime |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
12. OMOPProcedureOccurrence.procedure-end-date | |
Definition | Use this field to house the date that the procedure ended. |
Short | Procedure End Date |
Control | 0..1 |
Type | date |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
14. OMOPProcedureOccurrence.procedure-end-datetime | |
Definition | Use this field to house the datetime that the procedure ended. |
Short | procedure_end_datetime |
Control | 0..1 |
Type | dateTime |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
16. OMOPProcedureOccurrence.procedure-type-concept-id | |
Definition | 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. |
Short | Procedure Type |
Control | 1..1 |
Type | Reference(Concept OMOP Table) |
18. OMOPProcedureOccurrence.modifier-concept-id | |
Definition | The modifiers are intended to give additional information about the procedure but as of now the vocabulary is under review. |
Short | Modifier |
Control | 0..1 |
Type | Reference(Concept OMOP Table) |
20. OMOPProcedureOccurrence.quantity | |
Definition | If the quantity value is omitted, a single procedure is assumed. |
Short | Quantity |
Control | 0..1 |
Type | integer |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
22. OMOPProcedureOccurrence.provider-id | |
Definition | The provider associated with the procedure record, e.g. the provider who performed the Procedure. |
Short | Provider |
Control | 0..1 |
Type | Reference(Provider OMOP Table) |
24. OMOPProcedureOccurrence.visit-occurrence-id | |
Definition | The visit during which the procedure occurred. |
Short | VisitOccurrence |
Control | 0..1 |
Type | Reference(Visit Occurrence OMOP Table) |
26. OMOPProcedureOccurrence.visit-detail-id | |
Definition | 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. |
Short | Visit Detail |
Control | 0..1 |
Type | Reference(Visit Detail OMOP Table) |
28. OMOPProcedureOccurrence.procedure-source-value | |
Definition | 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. |
Short | Procedure Source Value |
Control | 0..1 |
Type | string |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |
30. OMOPProcedureOccurrence.procedure-source-concept-id | |
Definition | 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. |
Short | Procedure Source Concept |
Control | 0..1 |
Type | Reference(Concept OMOP Table) |
32. OMOPProcedureOccurrence.modifier-source-value | |
Definition | Modifier Source Value |
Short | Modifier Source Value |
Control | 0..1 |
Type | string |
Primitive Value | This primitive element may be present, or absent, or replaced by an extension |