CodeableConcept (10)

#NameSourceVerDescription
1AS CodeableConceptTimed Datatype Profileans.fhir.fr.annuaire#1.0.0-ballot-2R4Datatype profile créé à partir CodeableConcept dans le cadre de l'Annuaire Santé pour ajouter une extension Period au type CodeableConcept.
2BeObservationCodeableConcepthl7.fhir.be.core-clinical#currentR4This is a supporting profile, only to give guidelines how to express a few of the typical coding systems. In general, it shall be noted SNOMED-CT is the preferred national terminology. Other coding systems remain allowed or MAY be preferred in specific flows (e.g. the use of LOINC codes to express a laboratory test.)
3BeObservationCodeableConceptehealthplatform.be.r4.federalprofiles#1.3.3-betaR4This is a supporting profile, only to give guidelines how to express a few of the typical coding systems. In general, it shall be noted SNOMED-CT is the preferred national terminology. Other coding systems remain allowed or MAY be preferred in specific flows (e.g. the use of LOINC codes to express a laboratory test.)
4CH ELM CodeableConceptch.fhir.ig.ch-elm#currentR4This profile represents the constraint applied to the CodeableConcept data type by this IG to use the 'CH ELM CodeableConcept' data type profile.
5Codeable Concept (CZ)ncez.cz.fhir.core#currentR4This profile represents the constraint applied to the CodeableConcept data type by the Czech national FHIR Core Implementation Guide to use the CZ_Coding data type profile.
6Codeable Concept (IPS)hl7.fhir.uv.ips#currentR4This profile represents the constraint applied to the CodeableConcept data type by the International Patient Summary (IPS) FHIR Implementation Guide to use the Coding-uv-ips data type profile.
7Codeable Concept (PS-CA)ca.infoway.io.psca#1.0.1-alpha3R4This profile represents the constraint applied to the CodeableConcept data type by the PS-CA project to use the [PS-CA Coding](http://fhir.infoway-inforoute.ca/io/psca/StructureDefinition/Coding-ca-ps) data type profile in a way that is informed by the constraints of the [CodeableConcept IPS-UV profile](http://hl7.org/fhir/uv/ips/StructureDefinition-CodeableConcept-uv-ips.html) but removes the overarching expectation that all patient summary creators must demonstrate they can support codings for conformance.
8CodeableConcept-IEHRfhir.uv.researchdatasharing#currentR4
9Saner Measured Item Descriptionhl7.fhir.uv.saner#currentR4A CodeableConcept describing the item to be counted in terms of the type of FHIR Resource to count, and subtype of item identified by that resource
10TW CodeableConcepttw.gov.mohw.twcore#0.1.1R4此臺灣CodeableConcept Profile說明本IG如何進一步定義FHIR的CodeableConcept資料類型以呈現CodeableConcept [[*FMM1*](http://build.fhir.org/versions.html#maturity)]
1 2 3 4 5 6 7 8 9 10
CodeableConcept D
CodeableConcept.id D
CodeableConcept.extension S C D
CodeableConcept.coding S C (3) S (4) C D S C (3) D
CodeableConcept.coding.code C (2) C (3)
CodeableConcept.coding.system C F (2) F (3) C F (2)
CodeableConcept.text C D
S: There is slicing defined in the element(s)
C: There is cardinality erstrictions defined in the element(s)
I: There is invariants defined in the element(s)
F: There is a fixed or pattern value defined in the element(s)
D: There is document provided in the element(s)
B: There is terminology bindings defined in the element(s)
M: At least one of the element(s) has must-support = true
(N): The number of elements if > 1

Produced 08 Sep 2023