Narratif généré : DéfinitionStructure OMOPProcedureOccurrence Nom Drapeaux Card. Type Description et contraintes OMOPProcedureOccurrence 0..* Base Procedure Occurrence OMOP Table Les instances de ce modèle logique peuvent être la cible d'une référence #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 Reference(Concept OMOP Table) 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 Reference(Concept OMOP Table) Procedure Type #xD; modifier_concept_id 0..1 Reference(Concept OMOP Table) 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-OMOPProcedureOccurrence-definitions.html#OMOPProcedureOccurrence.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 Reference(Concept OMOP Table) Procedure Source Concept #xD; modifier_source_value 0..1 string Modifier Source Value #xD; Documentation pour ce format
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.
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.
The PERSON_ID of the PERSON for whom the procedure is recorded. This may be a system generated code.
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
Use this date to determine the date the procedure started.
Use this field to house the date that the procedure ended.
Use this field to house the datetime that the procedure ended.
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.
The modifiers are intended to give additional information about the procedure but as of now the vocabulary is under review.
If the quantity value is omitted, a single procedure is assumed.
The provider associated with the procedure record, e.g. the provider who performed the Procedure.
The visit during which the procedure occurred.
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.
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.
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.