CH EKM (R4)
0.0.1 - ci-build
CH EKM (R4)
0.0.1 - ci-build
CH EKM (R4), published by Federal Office of Public Health FOPH. This guide is not an authorized publication; it is the continuous build for version 0.0.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/ahdis/ch-ekm/ and changes regularly. See the Directory of published versions
| Official URL: http://fhir.ch/ig/ch-ekm/ValueSet/ChEkmExposureRelationshipType | Version: 0.0.1 | |||
| Active as of 2026-06-02 | Computable Name: ChEkmExposureRelationshipType | |||
Copyright/Legal: CC0-1.0 |
||||
This CH EKM value set includes the codes for the type of relationship to a sexual contact partner (Art der Beziehung).
References
http://fhir.ch/ig/ch-ekm/CodeSystem/ch-ekm-relationship-type version 📦0.0.1
Expansion performed internally based on codesystem CH EKM Relationship Type v0.0.1 (CodeSystem)
This value set contains 4 concepts
| System | Code | Display (en) | Definition | JSON | XML |
http://fhir.ch/ig/ch-ekm/CodeSystem/ch-ekm-relationship-type | steady-partner | Steady partner | Fester Partner. | ||
http://fhir.ch/ig/ch-ekm/CodeSystem/ch-ekm-relationship-type | non-steady-partner | Non-steady partner | Nicht fester Partner. | ||
http://fhir.ch/ig/ch-ekm/CodeSystem/ch-ekm-relationship-type | offered-paid-sex | Offered paid sex | Angebot von bezahltem Sex. | ||
http://fhir.ch/ig/ch-ekm/CodeSystem/ch-ekm-relationship-type | used-paid-sex | Used paid sex | Inanspruchnahme von bezahltem Sex. |
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 |