HdBe-FunctionalOrMentalStatus

ProfileStatusURL
HdBe-FunctionalOrMentalStatusdrafthttps://fhir.healthdata.be/StructureDefinition/LogicalModel/HdBe-FunctionalOrMentalStatus

status_name1..1CodeableConcept
status_value0..1CodeableConcept
status_date0..1dateTime
comment0..1string
medical_device0..*Reference(HdBe MedicalDevice)

functional_or_mental_status0..*
functional_or_mental_status.status_nameCodeableConcept1..1
functional_or_mental_status.status_valueCodeableConcept0..1
functional_or_mental_status.status_datedateTime0..1
functional_or_mental_status.commentstring0..1
functional_or_mental_status.medical_deviceReference(HdBe MedicalDevice)0..*



functional_or_mental_status
DefinitionRoot concept of FunctionalOrMentalStatus. This concept contains all data elements of the FunctionalOrMentalStatus information model.
Cardinality0...*
Invariants
  • ele-1:All FHIR elements must have a @value or children
    hasValue() or (children().count() > id.count())
Mappings
  • rim:n/a
functional_or_mental_status.id
DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Cardinality0...1
TypeSystem.String
Mappings
  • rim:n/a
functional_or_mental_status.extension
DefinitionMay 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.
Cardinality0...*
TypeExtension
Aliasextensions, 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.

SlicingUnordered, Open, by url(Value)
Invariants
  • ele-1:All FHIR elements must have a @value or children
    hasValue() or (children().count() > id.count())
  • ext-1:Must have either extensions or value[x], not both
    extension.exists() != value.exists()
Mappings
  • rim:n/a
  • rim:N/A
functional_or_mental_status.status_name
DefinitionCoded description of the functional or mental status or limitation. Code systems used include: * SNOMED CT * ICF (International Classification of Functioning, Disability and Health) * NOC (Nursing Outcomes Classification) * OMAHA
Cardinality1...1
TypeCodeableConcept
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
  • ele-1:All FHIR elements must have a @value or children
    hasValue() or (children().count() > id.count())
Mappings
  • rim:n/a
  • v2:CE/CNE/CWE
  • rim:CD
  • orim:fhir:CodeableConcept rdfs:subClassOf dt:CD
functional_or_mental_status.status_value
DefinitionThe extent to which the patient is limited by the functional or mental condition. If both the status name and the status value are recorded in code, then both values must come from the same code system. If the patient uses a medical device, the evaluation of the extent of the limitation will take place without this aid. The answer codes must be selected from the subselection of the code system corresponding with the request in accordance with the rules applicable to that system.
Cardinality0...1
TypeCodeableConcept
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
  • ele-1:All FHIR elements must have a @value or children
    hasValue() or (children().count() > id.count())
Mappings
  • rim:n/a
  • v2:CE/CNE/CWE
  • rim:CD
  • orim:fhir:CodeableConcept rdfs:subClassOf dt:CD
functional_or_mental_status.status_date
DefinitionDate on which the status was determined. A ‘vague’ date, such as only the year, is permitted.
Cardinality0...1
TypedateTime
Invariants
  • ele-1:All FHIR elements must have a @value or children
    hasValue() or (children().count() > id.count())
Mappings
  • rim:n/a
functional_or_mental_status.comment
DefinitionExplanatory comments as a description of the functional or mental status.
Cardinality0...1
Typestring
Comments

Note that FHIR strings SHALL NOT exceed 1MB in size

Invariants
  • ele-1:All FHIR elements must have a @value or children
    hasValue() or (children().count() > id.count())
Mappings
  • rim:n/a
functional_or_mental_status.medical_device
DefinitionMedical aid the patient has to reduce the impact of the disability or disorder.
Cardinality0...*
TypeReference(HdBe MedicalDevice)
Comments

References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.

Invariants
  • ele-1:All FHIR elements must have a @value or children
    hasValue() or (children().count() > id.count())
  • ref-1:SHALL have a contained resource if a local reference is provided
    reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
  • rim:n/a
  • rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)

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