Terminologies de Santé
1.0.0 - final-text
This page is part of the Guide d'implémentation des terminologies de Santé (v1.0.0: Release) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
Official URL: https://smt.esante.gouv.fr/fhir/ValueSet/jdv-role-informateur-cisis | Version: 20250606103857 | |||
Active as of 2025-06-06 | Responsible: Agence du Numérique en Santé(ANS) -2 - 10 Rue d'Oradour-sur-Glane, 75015 Paris | Computable Name: JdvRoleInformateurCisis | ||
Other Identifiers: OID:1.2.250.1.213.1.1.5.824 |
Jdv Role Informateur CISIS
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
Generated Narrative: ValueSet jdv-role-informateur-cisis
version: 1; Last updated: 2025-06-06 11:06:21+0000; Language: fr-FR
Profil: Shareable ValueSet
http://terminology.hl7.org/CodeSystem/v3-RoleClass
Code | Display | Définition |
CAREGIVER | aidant | A person responsible for the primary care of a patient at home. |
CON | informateur | A person or an organization (player) which provides or receives information regarding another entity (scoper). Examples; patient NOK and emergency contacts; guarantor contact; employer contact. |
ECON | personne à prévenir en cas d’urgence | An entity to be contacted in the event of an emergency. |
NOK | personne de confiance | An individual designated for notification as the next of kin for a given entity. |
PAT | aidé | A Role of a LivingSubject (player) as an actual or potential recipient of health care services from a healthcare provider organization (scoper). *Usage Note:* Communication about relationships between patients and specific healthcare practitioners (people) is not done via scoper. Instead this is generally done using the CareProvision act. This allows linkage between patient and a particular healthcare practitioner role and also allows description of the type of care involved in the relationship. |
ValueSet
Expansion performed internally based on codesystem RoleClass v4.0.0 (CodeSystem)
Ce jeu de valeur (ValueSet) contient 5 concepts
Code | Système | Display (fr-FR) | Définition |
CAREGIVER | http://terminology.hl7.org/CodeSystem/v3-RoleClass | aidant | A person responsible for the primary care of a patient at home. |
CON | http://terminology.hl7.org/CodeSystem/v3-RoleClass | informateur | A person or an organization (player) which provides or receives information regarding another entity (scoper). Examples; patient NOK and emergency contacts; guarantor contact; employer contact. |
ECON | http://terminology.hl7.org/CodeSystem/v3-RoleClass | personne à prévenir en cas d’urgence | An entity to be contacted in the event of an emergency. |
NOK | http://terminology.hl7.org/CodeSystem/v3-RoleClass | personne de confiance | An individual designated for notification as the next of kin for a given entity. |
PAT | http://terminology.hl7.org/CodeSystem/v3-RoleClass | aidé | A Role of a LivingSubject (player) as an actual or potential recipient of health care services from a healthcare provider organization (scoper). Usage Note: Communication about relationships between patients and specific healthcare practitioners (people) is not done via scoper. Instead this is generally done using the CareProvision act. This allows linkage between patient and a particular healthcare practitioner role and also allows description of the type of care involved in the relationship. |
Explanation of the columns that may appear on this page:
Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
System | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
Code | The code (used as the code in the resource instance) |
Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
Definition | An explanation of the meaning of the concept |
Comments | Additional notes about how to use the code |