Shared Health Specification and Guide Version 2.0 Revision F

 

3.24 StructureDefinition: Shared Health CodeableConcept

The official URL for this profile is: 

http://sharedhealth.exchange/fhir/StructureDefinition/dtprofile-codeableconcept

3.24.2 Formal Views of Profile Content

Download Excel representation

Description of Profiles, Differentials, Snapshots and how the different presentations work.

>

This structure is derived from CodeableConcept

NameCard.TypeConstraints and Usage
.  CodeableConcept 0..*inv-1: Must have coding, text or both
Definition:
A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.


Comments:
..  coding 0..*CodingDefinition:
A reference to a code defined by a terminology system.


Comments:
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labelled as UserSelected = true.

...  system 1..1uriDefinition:
The identification of the code system that defines the meaning of the symbol in the code.


Comments:
...  code 1..1codeDefinition:
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

..  text 0..1stringMax Length: 2500
Definition:
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.


Comments:
Very often the text is the same as a displayName of one of the codings.

This structure is derived from CodeableConcept

Summary

Mandatory: 0 element (2 nested mandatory elements)
Must-Support: 4 elements

This structure is derived from CodeableConcept

NameFlagsCard.TypeDescription & Constraintsdoco
.. CodeableConcept I0..*Concept - reference to a terminology or just text
inv-1: Must have coding, text or both
... id 0..1idxml:id (or equivalent in JSON)
... extension 0..*ExtensionAdditional Content defined by implementations
... coding SΣ0..*CodingCode defined by a terminology system
.... id 0..1idxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... system SΣ1..1uriIdentity of the terminology system
.... version Σ0..1stringVersion of the system - if relevant
.... code SΣ1..1codeSymbol in syntax defined by the system
.... display Σ0..1stringRepresentation defined by the system
.... userSelected Σ0..1booleanIf this coding was chosen directly by the user
... text SΣ0..1stringPlain text representation of the concept
Max Length: 2500

doco Documentation for this format

Grid View

This structure is derived from CodeableConcept

NameCard.TypeConstraints and Usage
.  CodeableConcept 0..*inv-1: Must have coding, text or both
Definition:
A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.


Comments:
..  coding 0..*CodingDefinition:
A reference to a code defined by a terminology system.


Comments:
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labelled as UserSelected = true.

...  system 1..1uriDefinition:
The identification of the code system that defines the meaning of the symbol in the code.


Comments:
...  code 1..1codeDefinition:
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

..  text 0..1stringMax Length: 2500
Definition:
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.


Comments:
Very often the text is the same as a displayName of one of the codings.

This structure is derived from CodeableConcept

Summary

Mandatory: 0 element (2 nested mandatory elements)
Must-Support: 4 elements

Differential View

This structure is derived from CodeableConcept

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. CodeableConcept I0..*Concept - reference to a terminology or just text
inv-1: Must have coding, text or both
... id 0..1idxml:id (or equivalent in JSON)
... extension 0..*ExtensionAdditional Content defined by implementations
... coding SΣ0..*CodingCode defined by a terminology system
.... id 0..1idxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... system SΣ1..1uriIdentity of the terminology system
.... version Σ0..1stringVersion of the system - if relevant
.... code SΣ1..1codeSymbol in syntax defined by the system
.... display Σ0..1stringRepresentation defined by the system
.... userSelected Σ0..1booleanIf this coding was chosen directly by the user
... text SΣ0..1stringPlain text representation of the concept
Max Length: 2500

doco Documentation for this format

 

Other representations of profile: Schematron

3.24.3 Terminology Bindings

3.24.4 Constraints

Constraints

IdPathDetailsRequirements
inv-1CodeableConceptMust have coding, text or both
: coding.exists() or text.exists()