The CARE_SITE table contains a list of uniquely identified institutional (physical or organizational) units where healthcare delivery is practiced (offices, wards, hospitals, clinics, etc.).

The Standardized Vocabularies contains records, or Concepts, that uniquely identify each fundamental unit of meaning used to express clinical information in all domain tables of the CDM. Concepts are derived from vocabularies, which represent clinical information across a domain (e.g. conditions, drugs, procedures) through the use of codes and associated descriptions. Some Concepts are designated Standard Concepts, meaning these Concepts can be used as normative expressions of a clinical entity within the OMOP Common Data Model and within standardized analytics. Each Standard Concept belongs to one domain, which defines the location where the Concept would be expected to occur within data tables of the CDM.

Concepts can represent broad categories (like "Cardiovascular disease"), detailed clinical elements ("Myocardial infarction of the anterolateral wall") or modifying characteristics and attributes that define Concepts at various levels of detail (severity of a disease, associated morphology, etc.).

Records in the Standardized Vocabularies tables are derived from national or international vocabularies such as SNOMED-CT, RxNorm, and LOINC, or custom Concepts defined to cover various aspects of observational data analysis.

A Condition Era is defined as a span of time when the Person is assumed to have a given condition. Similar to Drug Eras, Condition Eras are chronological periods of Condition Occurrence. Combining individual Condition Occurrences into a single Condition Era serves two purposes:

• It allows aggregation of chronic conditions that require frequent ongoing care, instead of treating each Condition Occurrence as an independent event.
• It allows aggregation of multiple, closely timed doctor visits for the same Condition to avoid double-counting the Condition Occurrences. For example, consider a Person who visits her Primary Care Physician (PCP) and who is referred to a specialist. At a later time, the Person visits the specialist, who confirms the PCP's original diagnosis and provides the appropriate treatment to resolve the condition. These two independent doctor visits should be aggregated into one Condition Era.

This table contains records of Events of a Person suggesting the presence of a disease or medical condition stated as a diagnosis, a sign, or a symptom, which is either observed by a Provider or reported by the patient.

The COST table captures records containing the cost of any medical event recorded in one of the OMOP clinical event tables such as DRUG_EXPOSURE, PROCEDURE_OCCURRENCE, VISIT_OCCURRENCE, VISIT_DETAIL, DEVICE_OCCURRENCE, OBSERVATION or MEASUREMENT.

Each record in the cost table account for the amount of money transacted for the clinical event. So, the COST table may be used to represent both receivables (charges) and payments (paid), each transaction type represented by its COST_CONCEPT_ID. The COST_TYPE_CONCEPT_ID field will use concepts in the Standardized Vocabularies to designate the source (provenance) of the cost data. A reference to the health plan information in the PAYER_PLAN_PERIOD table is stored in the record for information used for the adjudication system to determine the persons benefit for the clinical event.

The death domain contains the clinical event for how and when a Person dies. A person can have up to one record if the source system contains evidence about the Death, such as: Condition in an administrative claim, status of enrollment into a health plan, or explicit record in EHR data.

The Device domain captures information about a person's exposure to a foreign physical object or instrument which is used for diagnostic or therapeutic purposes through a mechanism beyond chemical action. Devices include implantable objects (e.g. pacemakers, stents, artificial joints), medical equipment and supplies (e.g. bandages, crutches, syringes), other instruments used in medical procedures (e.g. sutures, defibrillators) and material used in clinical care (e.g. adhesives, body material, dental material, surgical material).).

A Dose Era is defined as a span of time when the Person is assumed to be exposed to a constant dose of a specific active ingredient.

A Drug Era is defined as a span of time when the Person is assumed to be exposed to a particular active ingredient. A Drug Era is not the same as a Drug Exposure: Exposures are individual records corresponding to the source when Drug was delivered to the Person, while successive periods of Drug Exposures are combined under certain rules to produce continuous Drug Eras.

This table captures records about the exposure to a Drug ingested or otherwise introduced into the body. A Drug is a biochemical substance formulated in such a way that when administered to a Person it will exert a certain biochemical effect on the metabolism. Drugs include prescription and over-the-counter medicines, vaccines, and large-molecule biologic therapies. Radiological devices ingested or applied locally do not count as Drugs.

Comprehensive logical model representing the Electronic Health Record (EHR) data structure for the EDSH (Entrepôt de Données de Santé Hospitalisé) core variables.

This model consolidates all healthcare dimensions into a unified structure supporting:

• Patient demographics and identity management
• Healthcare encounters and administrative data
• Clinical diagnostics and procedures
• Laboratory results and biological examinations
• Medication exposures and prescriptions
• Clinical care measurements and vital signs
• Lifestyle and behavioral factors

The model is optimized for healthcare data interoperability, research, and clinical analytics while maintaining alignment with FHIR standards and French healthcare requirements.

The EPISODE_EVENT table connects qualifying clinical events (such as CONDITION_OCCURRENCE, DRUG_EXPOSURE, PROCEDURE_OCCURRENCE, MEASUREMENT) to the appropriate EPISODE entry. For example, linking the precise location of the metastasis (cancer modifier in MEASUREMENT) to the disease episode.

The EPISODE table aggregates lower-level clinical events (VISIT_OCCURRENCE, DRUG_EXPOSURE, PROCEDURE_OCCURRENCE, DEVICE_EXPOSURE) into a higher-level abstraction representing clinically and analytically relevant disease phases,outcomes and treatments. The EPISODE_EVENT table connects qualifying clinical events (VISIT_OCCURRENCE, DRUG_EXPOSURE, PROCEDURE_OCCURRENCE, DEVICE_EXPOSURE) to the appropriate EPISODE entry. For example cancers including their development over time, their treatment, and final resolution.

The FACT_RELATIONSHIP table contains records about the relationships between facts stored as records in any table of the CDM. Relationships can be defined between facts from the same domain, or different domains. Examples of Fact Relationships include: Person relationships (parent-child), care site relationships (hierarchical organizational structure of facilities within a health system), indication relationship (between drug exposures and associated conditions), usage relationships (of devices during the course of an associated procedure), or facts derived from one another (measurements derived from an associated specimen).

The LOCATION table represents a generic way to capture physical location or address information of Persons and Care Sites.

The BundleLogical has the same objective as the FHIR Bundle resource but allows for the grouping of logical models.

The MEASUREMENT table contains records of Measurements, i.e. structured values (numerical or categorical) obtained through systematic and standardized examination or testing of a Person or Person's sample. The MEASUREMENT table contains both orders and results of such Measurements as laboratory tests, vital signs, quantitative findings from pathology reports, etc. Measurements are stored as attribute value pairs, with the attribute as the Measurement Concept and the value representing the result. The value can be a Concept (stored in VALUE_AS_CONCEPT), or a numerical value (VALUE_AS_NUMBER) with a Unit (UNIT_CONCEPT_ID). The Procedure for obtaining the sample is housed in the PROCEDURE_OCCURRENCE table, though it is unnecessary to create a PROCEDURE_OCCURRENCE record for each measurement if one does not exist in the source data. Measurements differ from Observations in that they require a standardized test or some other activity to generate a quantitative or qualitative result. If there is no result, it is assumed that the lab test was conducted but the result was not captured.

The NOTE_NLP table encodes all output of NLP on clinical notes. Each row represents a single extracted term from a note.

The NOTE table captures unstructured information that was recorded by a provider about a patient in free text (in ASCII, or preferably in UTF8 format) notes on a given date. The type of note_text is CLOB or varchar(MAX) depending on RDBMS.

The OBSERVATION table captures clinical facts about a Person obtained in the context of examination, questioning or a procedure. Any data that cannot be represented by any other domains, such as social and lifestyle facts, medical history, family history, etc. are recorded here.

This table contains records which define spans of time during which two conditions are expected to hold: (i) Clinical Events that happened to the Person are recorded in the Event tables, and (ii) absense of records indicate such Events did not occur during this span of time.

The PAYER_PLAN_PERIOD table captures details of the period of time that a Person is continuously enrolled under a specific health Plan benefit structure from a given Payer. Each Person receiving healthcare is typically covered by a health benefit plan, which pays for (fully or partially), or directly provides, the care. These benefit plans are provided by payers, such as health insurances or state or government agencies. In each plan the details of the health benefits are defined for the Person or her family, and the health benefit Plan might change over time typically with increasing utilization (reaching certain cost thresholds such as deductibles), plan availability and purchasing choices of the Person. The unique combinations of Payer organizations, health benefit Plans and time periods in which they are valid for a Person are recorded in this table.

This table serves as the central identity management for all Persons in the database. It contains records that uniquely identify each person or patient, and some demographic information.

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 PROVIDER table contains a list of uniquely identified healthcare providers. These are individuals providing hands-on healthcare to patients, such as physicians, nurses, midwives, physical therapists etc.

The specimen domain contains the records identifying biological samples from a person.

The VISIT_DETAIL table is an optional table used to represents details of each record in the parent VISIT_OCCURRENCE table. A good example of this would be the movement between units in a hospital during an inpatient stay or claim lines associated with a one insurance claim. For every record in the VISIT_OCCURRENCE table there may be 0 or more records in the VISIT_DETAIL table with a 1:n relationship where n may be 0. The VISIT_DETAIL table is structurally very similar to VISIT_OCCURRENCE table and belongs to the visit domain.

This table contains Events where Persons engage with the healthcare system for a duration of time. They are often also called "Encounters". Visits are defined by a configuration of circumstances under which they occur, such as (i) whether the patient comes to a healthcare institution, the other way around, or the interaction is remote, (ii) whether and what kind of trained medical staff is delivering the service during the Visit, and (iii) whether the Visit is transient or for a longer period involving a stay in bed.

Formalisation de variables socles pour les EDSH

Profil abstrait pour les invariants dans les claims du PMSI.

Profil abstrait pour les invariants dans les claims du champs MCO du PMSI.

Profil générique des résultats de laboratoire du socle commun des EDS.

. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption.

Taux d'ALAT dans le sang. L'alanine-aminotransférase est capable de transférer le groupement amine de l'acide glutamique sur l'acide pyruvique avec formation d'une molécule d'acide α-cétoglutarique et d'alanine.

Taux d'ASAT dans le sang. L'ASAT est une enzyme faisant partie des transaminases qui intervient dans la navette malate-aspartate de transfert des électrons du NADH cytosolique vers le NAD+ mitochondrial.

Profil Bilirubine conjuguée du socle commun des EDSH

Taux de bilirubine sanguin. La bilirubine est un pigment jaune produit de la dégradation de l'hémoglobine, et d'autres hémoprotéines (cytochrome ou catalases).

Condition adapted to Data Management

. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption.

It specifies which core elements, extensions, vocabularies, and value sets SHALL be present and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption.

Profil pour la consommation de tabac.

Encounter adapted to Data Management

Profil Eosinophiles du socle commun des EDSH

Episode of care adapted to Data Management

Profil Erythrocytes du socle commun des EDSH

Profil des résultats de fonction rénale du socle commun des EDS

Part of a multipart branded medication.

French prescribed, dispensed or used medication expressed as branded medication composed of one to many substances. The code the french UCD (Unité Commune de Dispensation).

A complex medication composed of two to many simple médication. The simple medications component are described in as many ingredient.itemReference referencing a Medication resource profiled fr-medication-1.

Simple prescribed, dispensed, administered or used medication expressed in non proprietary name composed of one to many substances. If composed of many substance, the strengh SHALL be defined.

Taux sanguin de GGT. Aminoacyltransférase impliquées dans la catalyse d'enzymes hépatiques impliquées dans le métabolisme des acides aminés.

Taux de glucose dans le sang à jeun (c'est à dire après une période sans apport alimentaire d'au moins 8 heures).

Profil Hématocrite du socle commun des EDSH

Profil Hémoglobine du socle commun des EDSH

Forme glycquée de la molécule de l'hémoglobine dans le sang. Sa valeur biologique est le reflet de la concentration de glucose dans le sang (glycémie) sur trois mois.

Profil Leucocytes du socle commun des EDSH

Location adapted to Data Management

Profil Lymphocytes du socle commun des EDSH

Profil Monocytes du socle commun des EDSH

Profil Neutrophiles du socle commun des EDSH

Organization adapted for Data Management

Profil Patient du socle commun des EDSH

Profil Phosphatases alcaline du socle commun des EDSH

Profil Plaquettes du socle commun des EDSH

Ce profil définit la manière de représenter les observations de poids corporel en utilisant un code LOINC standard et des unités de mesure UCUM.

Practitioner adapted to Data Management

PractitionerRole adapted to Data Management

Profil pour les prescriptions médicamenteuses

Profil de la pression artérielle du socle commun des EDS

Profil pour la prise de médicaments

Procedure adapted to Data Management

Profil pour les Résumés d'Unité Médicale (RUM) du PMSI MCO.

Ce profil définit la manière de représenter les observations de taille corporelle en utilisant un code LOINC standard et des unités de mesure UCUM.

Profil Taux prothrombine (TP) du socle commun des EDSH

Profil Temps de céphaline activée (TCA) du socle commun des EDSH

Taux d'urée dans le sang. L'urée est un catabolite composé formé dans le foie à partir de l'ammoniac produit par la désamination des acides aminés. C'est le principal produit final du catabolisme des protéines et il constitue environ la moitié des solides urinaires totaux.

Profil Volume globulaire moyen du socle commun des EDSH

Profil Address du socle commun des EDS

Range with low and high unit UCUM encoded

Ratio with numerator and denominator unit UCUM encoded

simple quantity datatype requiring a UCUM unit

Cette extension permet de porter le code géographique du lieu de résidence tel que prévu dans les RSA du PMSI

Cette extension permet de renseigner le Groupe Homogène de Malade dans lequel le séjour a été classé en R4

Cette extension permet d'ordonnancer les items lorsque que les autres éléments présent ne permettent pas de le faire. C'est notament le cas des items de type RUM dont les dates sont parfois trop imprécises pour permettre ce ranking (granularité au jour)

Cette extension permet de formaliser la source d'information de laquelle est issue le statu vital du patient tel que renseigné dans Patien.deceased[x]

Jeu de valeurs de la CCAM correspondant aux actes médicaux pour le codage du PMSI

SELECT SNOMED CT code system values that describe the location on the body where the blood pressure was measured.

SELECT SNOMED CT code system values that describe how a blood pressure was measured.

Cette catégorisation permet de spécifier les différents éléments d'information qui doivent être fournis (variable selon le type d'item facturé)

Type d'activité physique

Le jeu de valeurs à utiliser pour coder l'élément code de la ressource FrMedicationNonproprietaryName.

Le jeu de valeurs à utiliser pour coder l'élément doseForm des ressources FrMedicationUcd, FrMedicationUcdPart ou FrMedicationNonProprietaryName.

Le jeu de valeurs à utiliser pour coder l'élément dosageInstruction.route de la ressource FrMedicationRequest.

SELECT SNOMED CT code system values that describe how the height/length was measured.

Ce ValueSet contient les GHM pour le PMSI MCO

Liste des analyses LOINC correspondant aux besoins du socle EDS et extrait du jeu de valeur circuit de la biologie.

Trois codes LOINC possibles pour l'estimation du débit de filtration glomérulaire, selon l'équation utilisée (Cockroft, MDRD ou CKD-EPI)

ValueSet reprenant la CIM10 OMS

ValueSet des code CIM10 ATIH utilisable en DA

ValueSet des code CIM10 ATIH utilisable en DP

ValueSet des code CIM10 ATIH utilisable en DR

ValueSet reprenant la CIM 10 ATIH

Codes providing the status of an observation for smoking status. Constrained to finaland entered-in-error.

Deux unités UCUM possibles pour l'estimation du débit de filtration glomérulaire. L'usage des annotations UCUM (partie entre accolades) étant déconseillé, on privilégiera l'utilisation des 'mL/min'.

Ce ValueSet contient tous les modes d'entrée pour le PMSI MCO

Ce ValueSet contient tous les modes de sortie pour le PMSI MCO

Type de statut tabagique en provenance de SNOMED CT

Type de statut tabagique en provenance de LOINC et de SNOMED CT

Type de statut tabagique en provenance de LOINC

(Clinical Focus: This set of values contains terms representing tobacco, e.g. nicotine, smoking, vaping, chew and snuff use or exposure.), (Data Element Scope: The intent of this value set is to provide encoded terms representing nicotine exposure via products that may be smoked or taken in with other methods. The scope includes non-nicotene electronic cigarette terms. The scope does not include marijuana or illicit drugs that are smoked), (Inclusion Criteria: Concepts from SCT's Tobacco Use and exposure hierarchy, electronic cigarette user hierarchy and appropriate codes from the event and situation hierarchies.), (Exclusion Criteria: Terms reflecting absence of smoking)

ValueSet des Sexe administratif du DPI

Ce ValueSet contient les codes géographiques de résidence du PMSI

ValueSet des modes d'entrée du DPI

ValueSet des modes de sortie du DPI

Ce ValueSet contient les sources d'informations sur le statut vital

Permet de préciser le cadre dans lequel in facture est émise (champ du PMSI par example)

Permet de préciser, dans un champ du PMSI, le type de facture.

ValueSet des types de séjour du DPI

ToDo

SELECT SNOMED CT code system values that describe how the weight was measured.

Fragment de CCAM permettant d'illustrer l'utilisation des codes CCAM dans les ressources procedures. Idéalement, il faudrait disposer d'une CCAM descriptive dans un serveur de terminologie FHIR. Pour l'heure, on ne dispose que d'une ccam facturante sur le SMT de l'ANS, sans ValueSet associés.

CIM 10 ATIH pour le PMSI

Typage des claim en France, dans le cadre du PMSI

CodeSystem aggrégeant les categories d'informations susceptible d'alimenter les Claim dans le système de santé français.

Cette catégorisation permet de spécifier les différents éléments d'information qui doivent être fournis (variable selon le type d'item facturé)

Groupes Homogènes de Malades.

Ce codage permet d'anonymiser le codage des communes dont la population est faible.

Système de codage des sexes administratifs du patient

CodeSystem des types de séjour

CodeSystem des modes d'entrée

CodeSystem des modes de sortie

Permet de coder la propriété RSS du PMSI MCO 'Mode d'entré'

Permet de coder la propriété RSS du PMSI MCO 'Mode de sortie'

Type de séjour

A set of codes that are defined in the Solor extension to the SNOMED CT code system. To be used until they are adopted by SNOMED CT.

Ce CodeSystem aggrège les sources desquelles peuvent provenir les informations sur le statu vital des patients en France.

CodeSystem reprenant les spécialités médicales listés par la FSM. En pratique, il s'agit des spécialités représentées par un Conseil National Professionnel au sein de la FSM. Voir ici : https://specialitesmedicales.org/la-fsm/a-propos/presentation-fsm/

Mode des claim en France, dans le cadre du PMSI

Liste des types que peuvent avoir les diagnostiques CIM-10 dans les différents résumés/factures qui peuvent être émis dans le système de santé français.

Alignement de l''expression de besoin vers le modèle physique du DPI dans le cadre de l''usage Core

Alignement de l''usage Core du modèle physique du DPI vers les ressources FHIR

Cette ressource présente les spécifications de l''alignement entre la ressource Patient vers les tables correspodantes du CDM OMOP.

Cette ressource présente les spécifications de l''alignement entre les ressources FHIR vers les tables correspodantes du CDM OMOP.

Mapping FHIR Patient resource to OMOP Death

Mapping FHIR Patient resource to OMOP Person

Mapping Observation laboratory resources to Measurement OMOP Domain

Mapping Patient resource to Location OMOP Domain

Mapping simple Observation laboratory resources to Measurement OMOP Domain

Transforms EHR logical model data to FHIR Semantic Layer resources using Bundle as container

Transforms QuestionnaireResponse based on Questionnaire Usage Variables socles into FHIR resources conforming to DM profiles

Standardisation du sexe administratif des patients pour se conformer aux exigences de FHIR

TODO

L'objectif de cet alignement est rendre possible la conversion d'un code 'gender' d'HL7 vers son équivalent dans OHDSI

Représente le taux d'ALAT du patient 9

Représente le taux d'ASAT du patient 9

Administration d'albumine du patient 9

Administration J1 de furosemide au patient 9

Administration J1 de spironolactone au patient 9

Administration J2 de furosemide au patient 9

Administration J2 de spironolactone au patient 9

Description de l'albumine

Représente l'ascite dont souffre le patient 9

Représente le taux de bilirubine totale du patient 9

Représente la cirrhose dont souffre le patient 9

Consommation d'alcool du patient 9

Exemple de réponse au questionnaire au format FHIR

Exemple simple

Représente la Fibroscopie oeso-gastroduodénale dont a bénéficié le patient 9

Description du furosémide

Représente le taux de gamma glutamyl transferase du patient 9

Prise en charge d'un infarctus du myocarde

Insuffisance respiratoire sur BPCO

Suivi diabète de type 2

Traitement d'un ulcère

Accouchement simple

Choc cardiogénique en réanimation

Surveillance d'une fièvre avec altération de l'état général

Suivi de cardiopathie

État de mal migraineux

Chirurgie d'une fracture fémorale

Patiente bénéficiant d'une ponction d'ascite évacuatrice et d'exploration de sa cirrhose

???

???

Représente le taux de PAL du patient 9

Poids du patient 9

Représente la ponction évacuatrice dont a bénéficié le patient 9

Prescription d'albumine du patient 9

Prescription de furosémide du patient 9

Prescription de furosémide du patient 9

Description du spironolactone

Représente le séjour du patient 9

Représente le taux de prothrombine du patient 9

???

Resource patient illustrant le patient 9

Exigences des variables socles pour les Entrepôts de Données de Santé Hospitalier (EDSH) au format Excel.