HdBe-AbilityToGroom
Profile | Status | URL |
---|---|---|
HdBe-AbilityToGroom | draft | https://fhir.healthdata.be/StructureDefinition/LogicalModel/HdBe-AbilityToGroom |
ability_to_groome | ability_to_groome | ||
grooming | 1..1 | CodeableConceptBinding |
ability_to_groome | |
Definition | Root concept of the AbilityToGroom information model. This root concept contains all data elements of the AbilityToGroom information model. |
Cardinality | 0...* |
Invariants |
|
Mappings |
|
ability_to_groome.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | System.String |
Mappings |
|
ability_to_groome.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
ability_to_groome.grooming | |
Definition | Personal grooming includes tending to hair and facial hair, such as combing it, or shaving and/or trimming facial hair; skincare, *e.g.* using make-up; nailcare . |
Cardinality | 1...1 |
Type | CodeableConcept |
Binding | Grooming codes UiterlijkeVerzorging (required) |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Example instances
[CBB name] | |
---|---|
[Concept name ] | [example value] |
// example of NameInformation
## Example instances
| name_information | |
|----------------------|-------------------|
| first_names | Johanna Petronella Maria
| initials | J.P.M.
| given_name | Jo
| name_usage | Geslachtsnaam partner gevolgd door eigen geslachtsnaam
| last_name.prefix | van
| last_name.last_name | Putten
| last_name_partner.partner_prefix | van der
| last_name_partner.partner_last_name | Giessen
| titles |
zib [zib name + version](https://zibs.nl/wiki/[zib name + version(release)]) difference
Concept | Category | Description |
---|---|---|
[element.path] |
[category of change] | [Description of change]([Reference to ticket/issue/zulip chat using MarkDown link]) |
Terminology Bindings
Path | Name | Strength | URL |
---|---|---|---|
grooming | UiterlijkeVerzorging | required | https://fhir.healthdata.be/ValueSet/UiterlijkeVerzorging |