Guide d'implémentation du GT Standards et Interopérabilité pour les EDS
0.1.0 - ci-build France flag

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

Artifacts Summary

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Structures: Logical Models

These define data models that represent the domain covered by this implementation guide in more business-friendly terms than the underlying FHIR resources.

CareSite OMOP Table

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.).

Concept OMOP Table

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.

Condition Era OMOP Table

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.
Condition Occurrence OMOP Table

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.

Cost OMOP Table

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.

Death OMOP Table

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.

Device Exposure OMOP Table

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).).

Dose Era OMOP Table

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.

Drug Era OMOP Table

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.

Drug Occurrence OMOP Table

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.

Episode Event OMOP Table

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.

Episode OMOP Table

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.

Fact Relationship OMOP Table

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).

Location OMOP Table

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

LogicalBundle

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

Measurement OMOP Table

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.

Note NLP OMOP Table

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

Note OMOP Table

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.

Observation OMOP Table

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.

Observation Period OMOP Table

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.

Payer Plan Period OMOP Table

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.

Person OMOP 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.

Procedure Occurrence OMOP Table

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.

Provider OMOP Table

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.

Specimen OMOP Table

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

Visit Detail OMOP Table

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.

Visit Occurrence OMOP Table

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.

Structures: Abstract Profiles

These are profiles on resources or data types that describe patterns used by other profiles, but cannot be instantiated directly. I.e. instances can conform to profiles based on these abstract profiles, but do not declare conformance to the abstract profiles themselves.

Profil de Claim pour le PMSI

Profil abstrait pour les invariants dans les claims du PMSI.

Profil de Claim pour le champ MCO du PMSI

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

Résultat de laboratoire

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

Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide.

Activité physique

. 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.

Blood Pressure

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

Body Height

Profil de la taille du patient du socle commun des EDS

Body Weight

Profil du poids du patient du socle commun des EDS

Consommation d'alcool

. 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.

Consommation d'autres drogues

. 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.

Consommation de tabac

Profil pour la consommation de tabac.

Fonction rénale

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

French Ucd Part Medication

Part of a multipart branded medication.

French branded name 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).

French compound Medication

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.

French non proprietary name Medication

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.

Patient

Profil Patient du socle commun des EDS

Prescription de médicaments

Profil pour les prescriptions médicamenteuses

Prise de médicaments

Profil pour la prise de médicaments

RSS du PMSI MCO

Profil pour les Résumés de Sortie Standardisé (RSS) du PMSI MCO.

Temps de céphaline activée

Profil des résultats de TCA - socle commun des EDS

Urémie

Profil des résultats d’urémie du socle commun des EDS

Structures: Data Type Profiles

These define constraints on FHIR data types for systems conforming to this implementation guide.

Address

Profil Address du socle commun des EDS

Range with UCUM quantity units

Range with low and high unit UCUM encoded

Ratio with UCUM quantity units

Ratio with numerator and denominator unit UCUM encoded

SimpleQuantity with UCUM quantity unit

simple quantity datatype requiring a UCUM unit

Terminology: Value Sets

These define sets of codes used by systems conforming to this implementation guide.

Actes CCAM pour le PMSI

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

Exercice Status Type

Type d’activité physique

French Medicinal Product only

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

French Medicinal product Dose form

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

French Route of Administration

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

Liste des analyses biologiques socle des EDS

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

Liste des analyses correspondant à l'estimation du DFG - socle des EDS

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

Liste des diagnostiques CIM-10 acceptable en DA pour les PMSI MCO et HAD
Liste des diagnostiques CIM-10 acceptable en DP pour les PMSI MCO et HAD
Liste des diagnostiques CIM-10 acceptable en DR pour les PMSI MCO et HAD
Liste des diagnostiques CIM-10 pour le PMSI
Liste des status pour l'Observation de consommation de tabac

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

Liste des unités possibles pour une estimation du débit de filtration glomérulaire - socle des EDS

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’.

Smoking Status Pack Years SCT

Type de statut tabagique en provenance de SNOMED CT

Smoking Status Type

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

Smoking Status Type from LOINC

Type de statut tabagique en provenance de LOINC

Smoking status comprehensive

(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 type fr des claims

Terminology: Code Systems

These define new code systems used by systems conforming to this implementation guide.

CCAM

CCAM ATIH pour le PMSI

CIM 10 PMSI

CIM 10 ATIH pour le PMSI

Categorie d'information pour les supporting information
mode PMSI

Mode des claim en France, dans le cadre du PMSI

type PMSI

Typage des claim en France, dans le cadre du PMSI

type de diagnostic du PMSI MCO

Terminology: Structure Maps

These define transformations to convert between data structures used by systems conforming to this implementation guide.

FHIR EDS Patient to Tables CDM OMOP

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

Mapping Observation laboratory resources to Measurement OMOP Domain

MappingObservationlaboratoryresourcestoMeasurementOMOPDomain

Mapping Patient resource to Death OMOP Domain

MappingPatientresourcetoDeathOMOPDomain

Mapping Patient resource to Location OMOP Domain

MappingPatientresourcetoLocationOMOPDomain

Mapping Patient resource to Person OMOP Domain

MappingPatientresourcetoPersonOMOPDomain

Mapping simple Observation laboratory resources to Measurement OMOP Domain

MappingsimpleObservationlaboratoryresourcestoMeasurementOMOPDomain

Terminology: Concept Maps

These define transformations to convert between codes by systems conforming with this implementation guide.

HL7 Gender to OHDSI Gender

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

LabAnalyses
LabComparator
LabUnit

Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.

alcohol-use-status-example-1

Cet exemple illustre l’usage du profil EDSObservationAlcoholUseStatus.<br /> A la date du 03/08/2023, le patient a déclaré être un consommateur d’alcohol occasionel.

assurance-maladie

assurance maladie (CPAM de Paris)

blood-pressure-example-1

Exemple de ressource pression artérielle

body-height-example-1

Exemple de ressource taille

body-weight-example-1

Exemple de ressource poids

claim-example-1

Exemple de ressource RSS

coverage-example-1

Exemple de ressource coverage

exercise-status-example-1

Cet exemple illustre l’usage du profil EDSObservationExerciceStatus.<br /> Le 03/08/2023, un Praticien hospitalier temps plein déclare que la patiente fait de l’exercice 3 fois par semaine.

exercise-status-example-2

Cet exemple illustre l’usage du profil EDSObservationExerciceStatus.<br /> Le 03/08/2023, un Praticien hospitalier temps plein déclare que la patiente fait de l’exercice 60 minutes par jour.

laboratory-fonction-renale-example-1
laboratory-tca-example-1
laboratory-uremie-example-1
organization-psl

Pitié Salpetrière

patient-example-1

Exemple de ressource patient

practitioner-role-example-1

Exemple de ressource practitioner role

smoke-use-status-example-1

Cet exemple illustre l’usage du profil EDSObservationSmokingStatus.<br /> Le 03/08/2023, la patiente déclare fumer 26 paquets de cigarette par an.

substance-use-status-example-1

Cet exemple illustre l’usage du profil EDSObservationSubstanceUseStatus.<br /> Le 03/08/2023, la patiente déclare avoir consommé d’amphetamine 3 fois dans l’année (sans ordonnance).