RIVO Noord Zorgviewer MVP2 Implementation Guide
0.2.1 - CI build
RIVO Noord Zorgviewer MVP2 Implementation Guide - Local Development build (v0.2.1). See the Directory of published versions
Draft as of 2023-03-22 |
Definitions for the Condition resource profile.
Guidance on how to interpret the contents of this table can be found here.
1. Condition | |
2. Condition.clinicalStatus | |
Must Support | true |
3. Condition.code | |
Binding | The codes SHALL be taken from http://snomed.info/sct/?fhir_vs=refset/31000147101; other codes may be used where these codes are not suitableThe codes SHALL be taken from ProbleemNaamCodelijst; other codes may be used where these codes are not suitable De DHD Thesaurus diagnose. The problem name defines the problem. |
Must Support | true |
4. Condition.code.text | |
Control | 0..? |
Must Support | true |
5. Condition.bodySite | |
Must Support | true |
6. Condition.onset[x] | |
Control | 10..1 |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Must Support | true |
Invariants | Defined on this element zv-con-1: At least one of Condition.onsetDateTime or Condition.onsetPeriod SHALL be present (: onsetDateTime.exists() or onsetPeriod.exists()) |
7. Condition.abatementDateTime | |
Must Support | true |
8. Condition.note | |
Must Support | true |
Guidance on how to interpret the contents of this table can be found here.
1. Condition | |
Definition | A problem describes a situation with regard to an individual’s health and/or welfare. This situation can be described by the person involved (the patient) themselves (in the form of a complaint) or by their healthcare provider (in the form of a diagnosis, for example). A clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern. |
Control | 0..* |
Alternate Names | Concern, Probleem |
Invariants | Defined on this element con-3: Condition.clinicalStatus SHALL be present if verificationStatus is not entered-in-error (: verificationStatus='entered-in-error' or clinicalStatus.exists()) con-4: If condition is abated, then clinicalStatus must be either inactive, resolved, or remission (: abatement.empty() or (abatement as boolean).not() or clinicalStatus='resolved' or clinicalStatus='remission' or clinicalStatus='inactive') dom-1: If the resource is contained in another resource, it SHALL NOT contain any narrative (: contained.text.empty()) dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources (: contained.contained.empty()) dom-3: If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource (: contained.where(('#'+id in %resource.descendants().reference).not()).empty()) dom-4: If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated (: contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()) |
2. Condition.implicitRules | |
Definition | A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. |
Control | 0..1 |
Type | uri |
Is Modifier | true |
Summary | true |
Comments | Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. |
3. Condition.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Alternate Names | 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. |
4. Condition.clinicalStatus | |
Definition | The problem status describes the condition of the problem:
The clinical status of the condition. |
Control | 10..1 This element is affected by the following invariants: con-3, con-4 |
Binding | The codes SHALL be taken from Condition Clinical Status Codes |
Type | code |
Is Modifier | true |
Must Support | true |
Summary | true |
Alternate Names | ProbleemStatus |
Comments | This element is labeled as a modifier because the status contains codes that mark the condition as not currently valid or of concern. |
5. Condition.clinicalStatus.extension:ProblemStatusCodelist | |
SliceName | ProblemStatusCodelist |
Definition | Describes the condition of the problem, use this extension to include the original HCIM code |
Control | 0..* This element is affected by the following invariants: ele-1 |
Type | Extension(Zib extension code specification) (Extension Type: CodeableConcept) |
Alternate Names | Bevat de specifieke code conform de zib, bij een FHIR-element die een verplichte koppeling heeft met een bepaalde FHIR waardelijst of een FHIR element die niet gecodeerd is gedefinieerd, terwijl de zib dit wel doet., Probleemstatus |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) |
6. Condition.clinicalStatus.extension:ProblemStatusCodelist.url | |
Definition | Source of the definition for the extension code - a logical name or a URL. |
Control | 1..1 |
Type | uri |
XML Representation | In the XML format, this property is represented as an attribute. |
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. |
Fixed Value | http://nictiz.nl/fhir/StructureDefinition/code-specification |
7. Condition.clinicalStatus.extension:ProblemStatusCodelist.value[x] | |
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). |
Control | 10..1 |
Type | Choice of: CodeableConcept, date, dateTime, Meta, code, string, Address, Attachment, integer, oid, Count, instant, ContactPoint, HumanName, Money, Identifier, Coding, markdown, SampledData, Ratio, id, positiveInt, Age, Distance, Reference, Period, Quantity, Duration, Range, uri, Annotation, boolean, base64Binary, Signature, unsignedInt, time, Timing, decimal |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Slicing | This element introduces a set of slices on Condition.clinicalStatus.extension.value[x]. The slices are unordered and Closed, and can be differentiated using the following discriminators:
|
8. Condition.clinicalStatus.extension:ProblemStatusCodelist.value[x]:valueCodeableConcept | |
SliceName | valueCodeableConcept |
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). |
Control | 10..1 |
Binding | The codes SHALL be taken from ProbleemStatusCodelijst; other codes may be used where these codes are not suitableFor codes, see (unbound) ProbleemStatusCodelijs |
Type | Choice of: CodeableConcept, date, dateTime, Meta, code, string, Address, Attachment, integer, oid, Count, instant, ContactPoint, HumanName, Money, Identifier, Coding, markdown, SampledData, Ratio, id, positiveInt, Age, Distance, Reference, Period, Quantity, Duration, Range, uri, Annotation, boolean, base64Binary, Signature, unsignedInt, time, Timing, decimal |
[x] Note | See Choice of Data Types for further information about how to use [x] |
9. Condition.verificationStatus | |
Definition | Clinical status of the problem or the diagnosis. The verification status to support the clinical status of the condition. |
Control | 0..1 This element is affected by the following invariants: con-3 |
Binding | The codes SHALL be taken from ConditionVerificationStatus |
Type | code |
Is Modifier | true |
Summary | true |
Alternate Names | VerificatieStatus |
Comments | verificationStatus is not required. For example, when a patient has abdominal pain in the ED, there is not likely going to be a verification status. This element is labeled as a modifier because the status contains the code refuted and entered-in-error that mark the Condition as not currently valid. |
Default Value | unknown |
10. Condition.verificationStatus.extension:VerificatieStatusCodelijst | |
SliceName | VerificatieStatusCodelijst |
Definition | Describes the verification status of the problem, use this extension to include the original HCIM code |
Control | 0..1 This element is affected by the following invariants: ele-1 |
Type | Extension(Zib extension code specification) (Extension Type: CodeableConcept) |
Alternate Names | Bevat de specifieke code conform de zib, bij een FHIR-element die een verplichte koppeling heeft met een bepaalde FHIR waardelijst of een FHIR element die niet gecodeerd is gedefinieerd, terwijl de zib dit wel doet., VerificatieStatusCodelijst |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) |
11. Condition.verificationStatus.extension:VerificatieStatusCodelijst.url | |
Definition | Source of the definition for the extension code - a logical name or a URL. |
Control | 1..1 |
Type | uri |
XML Representation | In the XML format, this property is represented as an attribute. |
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. |
Fixed Value | http://nictiz.nl/fhir/StructureDefinition/code-specification |
12. Condition.verificationStatus.extension:VerificatieStatusCodelijst.value[x] | |
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). |
Control | 10..1 |
Type | Choice of: CodeableConcept, date, dateTime, Meta, code, string, Address, Attachment, integer, oid, Count, instant, ContactPoint, HumanName, Money, Identifier, Coding, markdown, SampledData, Ratio, id, positiveInt, Age, Distance, Reference, Period, Quantity, Duration, Range, uri, Annotation, boolean, base64Binary, Signature, unsignedInt, time, Timing, decimal |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Slicing | This element introduces a set of slices on Condition.verificationStatus.extension.value[x]. The slices are unordered and Closed, and can be differentiated using the following discriminators:
|
13. Condition.verificationStatus.extension:VerificatieStatusCodelijst.value[x]:valueCodeableConcept | |
SliceName | valueCodeableConcept |
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). |
Control | 10..1 |
Binding | The codes SHALL be taken from VerificatieStatusCodelijst; other codes may be used where these codes are not suitableFor codes, see (unbound) VerificatieStatusCodelijs |
Type | Choice of: CodeableConcept, date, dateTime, Meta, code, string, Address, Attachment, integer, oid, Count, instant, ContactPoint, HumanName, Money, Identifier, Coding, markdown, SampledData, Ratio, id, positiveInt, Age, Distance, Reference, Period, Quantity, Duration, Range, uri, Annotation, boolean, base64Binary, Signature, unsignedInt, time, Timing, decimal |
[x] Note | See Choice of Data Types for further information about how to use [x] |
14. Condition.code | |
Definition | The problem name defines the problem. Depending on the setting, different code systems can be used. The ProblemNameCodelist provides an overview of the possible code systems. Identification of the condition, problem or diagnosis. |
Control | 10..1 |
Binding | The codes SHALL be taken from http://snomed.info/sct/?fhir_vs=refset/31000147101; other codes may be used where these codes are not suitableFor example codes, see Condition/Problem/Diagnosis Codes De DHD Thesaurus diagnose. Identification of the condition or diagnosis. |
Type | CodeableConcept |
Must Support | true |
Summary | true |
Requirements | 0..1 to account for primarily narrative only resources. |
Alternate Names | type, ProbleemNaam |
15. Condition.code.text | |
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. |
Control | 0..1 |
Type | string |
Must Support | true |
Summary | true |
Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. |
Comments | Very often the text is the same as a displayName of one of the codings. |
16. Condition.bodySite | |
Definition | Anatomical location which is the focus of the procedure. The anatomical location where this condition manifests itself. |
Control | 0..* |
Binding | The codes SHALL be taken from ProbleemAnatomischeLocatieCodelijst; other codes may be used where these codes are not suitableFor example codes, see SNOMED CT Body Structures ProbleemAnatomischeLocatieCodelijst Codes describing anatomical locations. May include laterality. |
Type | CodeableConcept |
Must Support | true |
Summary | true |
Alternate Names | ProbleemAnatomischeLocatie |
Comments | Only used if not implicit in code found in Condition.code. If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension body-site-instance. May be a summary code, or a reference to a very precise definition of the location, or both. |
17. Condition.bodySite.extension:Laterality | |
SliceName | Laterality |
Definition | Laterality adds information about body side to the anatomic location, e.g. left |
Control | 0..1 |
Type | Extension(BodySite Qualifier) (Extension Type: CodeableConcept) |
Alternate Names | ProbleemLateraliteit |
18. Condition.bodySite.extension:Laterality.url | |
Definition | Source of the definition for the extension code - a logical name or a URL. |
Control | 1..1 |
Type | uri |
XML Representation | In the XML format, this property is represented as an attribute. |
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. |
Fixed Value | http://nictiz.nl/fhir/StructureDefinition/BodySite-Qualifier |
19. Condition.bodySite.extension:Laterality.value[x] | |
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). |
Control | 0..1 |
Type | Choice of: CodeableConcept, date, dateTime, Meta, code, string, Address, Attachment, integer, oid, Count, instant, ContactPoint, HumanName, Money, Identifier, Coding, markdown, SampledData, Ratio, id, positiveInt, Age, Distance, Reference, Period, Quantity, Duration, Range, uri, Annotation, boolean, base64Binary, Signature, unsignedInt, time, Timing, decimal |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Slicing | This element introduces a set of slices on Condition.bodySite.extension.value[x]. The slices are unordered and Closed, and can be differentiated using the following discriminators:
|
20. Condition.bodySite.extension:Laterality.value[x]:valueCodeableConcept | |
SliceName | valueCodeableConcept |
Definition | Qualifier to refine the anatomical location. These include qualifiers for laterality, relative location, directionality, number, and plane. Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). |
Control | 0..1 |
Binding | The codes SHALL be taken from ProbleemLateraliteitCodelijst; other codes may be used where these codes are not suitableFor codes, see (unbound) ProblemLateralityCodelis |
Type | Choice of: CodeableConcept, date, dateTime, Meta, code, string, Address, Attachment, integer, oid, Count, instant, ContactPoint, HumanName, Money, Identifier, Coding, markdown, SampledData, Ratio, id, positiveInt, Age, Distance, Reference, Period, Quantity, Duration, Range, uri, Annotation, boolean, base64Binary, Signature, unsignedInt, time, Timing, decimal |
[x] Note | See Choice of Data Types for further information about how to use [x] |
21. Condition.subject | |
Definition | Indicates the patient or group who the condition record is associated with. |
Control | 1..1 |
Type | Reference(nl-core-patient|Patient|Group) |
Summary | true |
Requirements | Group is typically used for veterinary or public health use cases. |
Alternate Names | patient |
22. Condition.onset[x] | |
Definition | Estimated or actual date or date-time the condition began, in the opinion of the clinician. |
Control | 10..1 |
Type | Choice of: dateTime, string, Period, Range, Age |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Must Support | true |
Summary | true |
Comments | Age is generally used when the patient reports an age at which the Condition began to occur. |
Invariants | Defined on this element zv-con-1: At least one of Condition.onsetDateTime or Condition.onsetPeriod SHALL be present (: onsetDateTime.exists() or onsetPeriod.exists()) |
Slicing | This element introduces a set of slices on Condition.onset[x]. The slices are unordered and Closed, and can be differentiated using the following discriminators:
|
23. Condition.onset[x]:onsetDateTime | |
SliceName | onsetDateTime |
Definition | Start of the disorder to which the problem applies. Especially in symptoms in which it takes longer for the final diagnosis, it is important to know not only the date of the diagnosis, but also how long the patient has had the disorder. A ‘vague’ date, such as only the year or the month and the year, is permitted. Estimated or actual date or date-time the condition began, in the opinion of the clinician. |
Control | 0..1 |
Type | Choice of: dateTime, string, Period, Range, Age |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Summary | true |
Alternate Names | ProbleemBeginDatum |
Comments | Age is generally used when the patient reports an age at which the Condition began to occur. |
24. Condition.abatement[x] | |
Definition | The date or estimated date that the condition resolved or went into remission. This is called "abatement" because of the many overloaded connotations associated with "remission" or "resolution" - Conditions are never really resolved, but they can abate. |
Control | 0..1 This element is affected by the following invariants: con-4 |
Type | Choice of: dateTime, boolean, string, Period, Range, Age |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Comments | There is no explicit distinction between resolution and remission because in many cases the distinction is not clear. Age is generally used when the patient reports an age at which the Condition abated. If there is no abatement element, it is unknown whether the condition has resolved or entered remission; applications and users should generally assume that the condition is still valid. When abatementString exists, it implies the condition is abated. |
Slicing | This element introduces a set of slices on Condition.abatement[x]. The slices are unordered and Closed, and can be differentiated using the following discriminators:
|
25. Condition.abatement[x]:abatementDateTime | |
SliceName | abatementDateTime |
Definition | Date on which the disorder to which the problem applies, is considered not to be present anymore. This date does not need to be the same as the date of the change in problem status. A ‘vague’ date, such as only the year or the month and the year, is permitted. The date or estimated date that the condition resolved or went into remission. This is called "abatement" because of the many overloaded connotations associated with "remission" or "resolution" - Conditions are never really resolved, but they can abate. |
Control | 0..1 This element is affected by the following invariants: con-4 |
Type | Choice of: dateTime, boolean, string, Period, Range, Age |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Must Support | true |
Alternate Names | ProbleemEindDatum |
Comments | There is no explicit distinction between resolution and remission because in many cases the distinction is not clear. Age is generally used when the patient reports an age at which the Condition abated. If there is no abatement element, it is unknown whether the condition has resolved or entered remission; applications and users should generally assume that the condition is still valid. When abatementString exists, it implies the condition is abated. |
26. Condition.note | |
Definition | Comment by the one who determined or updated the Problem. Additional information about the Condition. This is a general notes/comments entry for description of the Condition, its diagnosis and prognosis. |
Control | 0..* |
Type | Annotation |
Must Support | true |
Alternate Names | Toelichting |
Guidance on how to interpret the contents of this table can be found here.
1. Condition | |||||
Definition | A problem describes a situation with regard to an individual’s health and/or welfare. This situation can be described by the person involved (the patient) themselves (in the form of a complaint) or by their healthcare provider (in the form of a diagnosis, for example). | ||||
Control | 0..* | ||||
Alternate Names | Concern, Probleem | ||||
2. Condition.id | |||||
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. | ||||
Control | 0..1 | ||||
Type | id | ||||
Summary | true | ||||
Comments | The only time that a resource does not have an id is when it is being submitted to the server using a create operation. | ||||
3. Condition.meta | |||||
Definition | The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource. | ||||
Control | 0..1 | ||||
Type | Meta | ||||
Summary | true | ||||
4. Condition.implicitRules | |||||
Definition | A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. | ||||
Control | 0..1 | ||||
Type | uri | ||||
Is Modifier | true | ||||
Summary | true | ||||
Comments | Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. | ||||
5. Condition.language | |||||
Definition | The base language in which the resource is written. | ||||
Control | 0..1 | ||||
Binding | The codes SHALL be taken from Common Languages; other codes may be used where these codes are not suitable
A human language
| ||||
Type | code | ||||
Comments | Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). | ||||
6. Condition.text | |||||
Definition | A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. | ||||
Control | 0..1 This element is affected by the following invariants: dom-1 | ||||
Type | Narrative | ||||
Alternate Names | narrative, html, xhtml, display | ||||
Comments | Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later. | ||||
7. Condition.contained | |||||
Definition | These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. | ||||
Control | 0..* | ||||
Type | Resource | ||||
Alternate Names | inline resources, anonymous resources, contained resources | ||||
Comments | This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. | ||||
8. Condition.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the resource. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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. | ||||
9. Condition.modifierExtension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Is Modifier | true | ||||
Alternate Names | 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. | ||||
10. Condition.identifier | |||||
Definition | This records identifiers associated with this condition that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate (e.g. in CDA documents, or in written / printed documentation). | ||||
Note | This is a business identifier, not a resource identifier (see discussion) | ||||
Control | 0..* | ||||
Type | Identifier | ||||
Summary | true | ||||
Requirements | Need to allow connection to a wider workflow. | ||||
11. Condition.clinicalStatus | |||||
Definition | The problem status describes the condition of the problem:
| ||||
Control | 1..1 This element is affected by the following invariants: con-3, con-4 | ||||
Binding | The codes SHALL be taken from Condition Clinical Status Codes | ||||
Type | code | ||||
Is Modifier | true | ||||
Must Support | true | ||||
Summary | true | ||||
Alternate Names | ProbleemStatus | ||||
Comments | This element is labeled as a modifier because the status contains codes that mark the condition as not currently valid or of concern. | ||||
12. Condition.clinicalStatus.id | |||||
Definition | unique id for the element within a resource (for internal references) | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
13. Condition.clinicalStatus.extension | |||||
Definition | An Extension | ||||
Control | 0..* | ||||
Type | Extension | ||||
Slicing | This element introduces a set of slices on Condition.clinicalStatus.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
14. Condition.clinicalStatus.extension:ProblemStatusCodelist | |||||
SliceName | ProblemStatusCodelist | ||||
Definition | Describes the condition of the problem, use this extension to include the original HCIM code | ||||
Control | 0..* This element is affected by the following invariants: ele-1 | ||||
Type | Extension(Zib extension code specification) (Extension Type: CodeableConcept) | ||||
Alternate Names | Bevat de specifieke code conform de zib, bij een FHIR-element die een verplichte koppeling heeft met een bepaalde FHIR waardelijst of een FHIR element die niet gecodeerd is gedefinieerd, terwijl de zib dit wel doet., Probleemstatus | ||||
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) | ||||
15. Condition.clinicalStatus.extension:ProblemStatusCodelist.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
16. Condition.clinicalStatus.extension:ProblemStatusCodelist.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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 | This element introduces a set of slices on Condition.clinicalStatus.extension.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
17. Condition.clinicalStatus.extension:ProblemStatusCodelist.url | |||||
Definition | Source of the definition for the extension code - a logical name or a URL. | ||||
Control | 1..1 | ||||
Type | uri | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. | ||||
Fixed Value | http://nictiz.nl/fhir/StructureDefinition/code-specification | ||||
18. Condition.clinicalStatus.extension:ProblemStatusCodelist.value[x] | |||||
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||||
Control | 1..1 | ||||
Type | CodeableConcept | ||||
[x] Note | See Choice of Data Types for further information about how to use [x] | ||||
Slicing | This element introduces a set of slices on Condition.clinicalStatus.extension.value[x]. The slices are unordered and Closed, and can be differentiated using the following discriminators:
| ||||
19. Condition.clinicalStatus.extension:ProblemStatusCodelist.value[x]:valueCodeableConcept | |||||
SliceName | valueCodeableConcept | ||||
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||||
Control | 1..1 | ||||
Binding | The codes SHALL be taken from ProbleemStatusCodelijst; other codes may be used where these codes are not suitable ProbleemStatusCodelijs | ||||
Type | CodeableConcept | ||||
[x] Note | See Choice of Data Types for further information about how to use [x] | ||||
20. Condition.clinicalStatus.value | |||||
Definition | Primitive value for code | ||||
Control | 0..1 | ||||
Type | code | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
21. Condition.verificationStatus | |||||
Definition | Clinical status of the problem or the diagnosis. | ||||
Control | 0..1 This element is affected by the following invariants: con-3 | ||||
Binding | The codes SHALL be taken from ConditionVerificationStatus | ||||
Type | code | ||||
Is Modifier | true | ||||
Summary | true | ||||
Alternate Names | VerificatieStatus | ||||
Comments | verificationStatus is not required. For example, when a patient has abdominal pain in the ED, there is not likely going to be a verification status. This element is labeled as a modifier because the status contains the code refuted and entered-in-error that mark the Condition as not currently valid. | ||||
Default Value | unknown | ||||
22. Condition.verificationStatus.id | |||||
Definition | unique id for the element within a resource (for internal references) | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
23. Condition.verificationStatus.extension | |||||
Definition | An Extension | ||||
Control | 0..* | ||||
Type | Extension | ||||
Slicing | This element introduces a set of slices on Condition.verificationStatus.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
24. Condition.verificationStatus.extension:VerificatieStatusCodelijst | |||||
SliceName | VerificatieStatusCodelijst | ||||
Definition | Describes the verification status of the problem, use this extension to include the original HCIM code | ||||
Control | 0..1 This element is affected by the following invariants: ele-1 | ||||
Type | Extension(Zib extension code specification) (Extension Type: CodeableConcept) | ||||
Alternate Names | Bevat de specifieke code conform de zib, bij een FHIR-element die een verplichte koppeling heeft met een bepaalde FHIR waardelijst of een FHIR element die niet gecodeerd is gedefinieerd, terwijl de zib dit wel doet., VerificatieStatusCodelijst | ||||
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) | ||||
25. Condition.verificationStatus.extension:VerificatieStatusCodelijst.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
26. Condition.verificationStatus.extension:VerificatieStatusCodelijst.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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 | This element introduces a set of slices on Condition.verificationStatus.extension.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
27. Condition.verificationStatus.extension:VerificatieStatusCodelijst.url | |||||
Definition | Source of the definition for the extension code - a logical name or a URL. | ||||
Control | 1..1 | ||||
Type | uri | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. | ||||
Fixed Value | http://nictiz.nl/fhir/StructureDefinition/code-specification | ||||
28. Condition.verificationStatus.extension:VerificatieStatusCodelijst.value[x] | |||||
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||||
Control | 1..1 | ||||
Type | CodeableConcept | ||||
[x] Note | See Choice of Data Types for further information about how to use [x] | ||||
Slicing | This element introduces a set of slices on Condition.verificationStatus.extension.value[x]. The slices are unordered and Closed, and can be differentiated using the following discriminators:
| ||||
29. Condition.verificationStatus.extension:VerificatieStatusCodelijst.value[x]:valueCodeableConcept | |||||
SliceName | valueCodeableConcept | ||||
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||||
Control | 1..1 | ||||
Binding | The codes SHALL be taken from VerificatieStatusCodelijst; other codes may be used where these codes are not suitable VerificatieStatusCodelijs | ||||
Type | CodeableConcept | ||||
[x] Note | See Choice of Data Types for further information about how to use [x] | ||||
30. Condition.verificationStatus.value | |||||
Definition | Primitive value for code | ||||
Control | 0..1 | ||||
Type | code | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
31. Condition.category | |||||
Definition | The type of problem; see the profile description. | ||||
Control | 0..* | ||||
Binding | The codes SHALL be taken from ProbleemTypeCodelijst; other codes may be used where these codes are not suitable The type of problem | ||||
Type | CodeableConcept | ||||
Alternate Names | ProbleemType | ||||
Comments | The categorization is often highly contextual and may appear poorly differentiated or not very useful in other contexts. | ||||
32. Condition.severity | |||||
Definition | A subjective assessment of the severity of the condition as evaluated by the clinician. | ||||
Control | 0..1 | ||||
Binding | The codes SHOULD be taken from Condition/Diagnosis Severity A subjective assessment of the severity of the condition as evaluated by the clinician | ||||
Type | CodeableConcept | ||||
Comments | Coding of the severity with a terminology is preferred, where possible. | ||||
33. Condition.code | |||||
Definition | The problem name defines the problem. Depending on the setting, different code systems can be used. The ProblemNameCodelist provides an overview of the possible code systems. | ||||
Control | 1..1 | ||||
Binding | The codes SHALL be taken from http://snomed.info/sct/?fhir_vs=refset/31000147101; other codes may be used where these codes are not suitable De DHD Thesaurus diagnose | ||||
Type | CodeableConcept | ||||
Must Support | true | ||||
Summary | true | ||||
Requirements | 0..1 to account for primarily narrative only resources. | ||||
Alternate Names | type, ProbleemNaam | ||||
34. Condition.code.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
35. Condition.code.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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 | This element introduces a set of slices on Condition.code.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
36. Condition.code.coding | |||||
Definition | A reference to a code defined by a terminology system. | ||||
Control | 0..* | ||||
Type | Coding | ||||
Summary | true | ||||
Requirements | Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. | ||||
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 labeled as UserSelected = true. | ||||
37. Condition.code.text | |||||
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. | ||||
Control | 0..1 | ||||
Type | string | ||||
Must Support | true | ||||
Summary | true | ||||
Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. | ||||
Comments | Very often the text is the same as a displayName of one of the codings. | ||||
38. Condition.bodySite | |||||
Definition | Anatomical location which is the focus of the procedure. | ||||
Control | 0..* | ||||
Binding | The codes SHALL be taken from ProbleemAnatomischeLocatieCodelijst; other codes may be used where these codes are not suitable ProbleemAnatomischeLocatieCodelijs | ||||
Type | CodeableConcept | ||||
Must Support | true | ||||
Summary | true | ||||
Alternate Names | ProbleemAnatomischeLocatie | ||||
Comments | Only used if not implicit in code found in Condition.code. If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension body-site-instance. May be a summary code, or a reference to a very precise definition of the location, or both. | ||||
39. Condition.bodySite.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
40. Condition.bodySite.extension | |||||
Definition | An Extension | ||||
Control | 0..* | ||||
Type | Extension | ||||
Slicing | This element introduces a set of slices on Condition.bodySite.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
41. Condition.bodySite.extension:Laterality | |||||
SliceName | Laterality | ||||
Definition | Laterality adds information about body side to the anatomic location, e.g. left | ||||
Control | 0..1 | ||||
Type | Extension(BodySite Qualifier) (Extension Type: CodeableConcept) | ||||
Alternate Names | ProbleemLateraliteit | ||||
42. Condition.bodySite.extension:Laterality.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
43. Condition.bodySite.extension:Laterality.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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 | This element introduces a set of slices on Condition.bodySite.extension.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
44. Condition.bodySite.extension:Laterality.url | |||||
Definition | Source of the definition for the extension code - a logical name or a URL. | ||||
Control | 1..1 | ||||
Type | uri | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. | ||||
Fixed Value | http://nictiz.nl/fhir/StructureDefinition/BodySite-Qualifier | ||||
45. Condition.bodySite.extension:Laterality.value[x] | |||||
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||||
Control | 0..1 | ||||
Type | CodeableConcept | ||||
[x] Note | See Choice of Data Types for further information about how to use [x] | ||||
Slicing | This element introduces a set of slices on Condition.bodySite.extension.value[x]. The slices are unordered and Closed, and can be differentiated using the following discriminators:
| ||||
46. Condition.bodySite.extension:Laterality.value[x]:valueCodeableConcept | |||||
SliceName | valueCodeableConcept | ||||
Definition | Qualifier to refine the anatomical location. These include qualifiers for laterality, relative location, directionality, number, and plane. | ||||
Control | 0..1 | ||||
Binding | The codes SHALL be taken from ProbleemLateraliteitCodelijst; other codes may be used where these codes are not suitable ProblemLateralityCodelis | ||||
Type | CodeableConcept | ||||
[x] Note | See Choice of Data Types for further information about how to use [x] | ||||
47. Condition.bodySite.coding | |||||
Definition | A reference to a code defined by a terminology system. | ||||
Control | 0..* | ||||
Type | Coding | ||||
Summary | true | ||||
Requirements | Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. | ||||
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 labeled as UserSelected = true. | ||||
48. Condition.bodySite.text | |||||
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. | ||||
Control | 0..1 | ||||
Type | string | ||||
Summary | true | ||||
Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. | ||||
Comments | Very often the text is the same as a displayName of one of the codings. | ||||
49. Condition.subject | |||||
Definition | Indicates the patient or group who the condition record is associated with. | ||||
Control | 1..1 | ||||
Type | Reference(nl-core-patient) | ||||
Summary | true | ||||
Requirements | Group is typically used for veterinary or public health use cases. | ||||
Alternate Names | patient | ||||
50. Condition.context | |||||
Definition | Encounter during which the condition was first asserted. | ||||
Control | 0..1 | ||||
Type | Reference(Zib Encounter|nl-core-episodeofcare) | ||||
Summary | true | ||||
Alternate Names | encounter | ||||
Comments | This record indicates the encounter this particular record is associated with. In the case of a "new" diagnosis reflecting ongoing/revised information about the condition, this might be distinct from the first encounter in which the underlying condition was first "known". | ||||
51. Condition.onset[x] | |||||
Definition | Estimated or actual date or date-time the condition began, in the opinion of the clinician. | ||||
Control | 1..1 | ||||
Type | dateTime | ||||
[x] Note | See Choice of Data Types for further information about how to use [x] | ||||
Must Support | true | ||||
Summary | true | ||||
Comments | Age is generally used when the patient reports an age at which the Condition began to occur. | ||||
Invariants | Defined on this element zv-con-1: At least one of Condition.onsetDateTime or Condition.onsetPeriod SHALL be present (: onsetDateTime.exists() or onsetPeriod.exists()) | ||||
Slicing | This element introduces a set of slices on Condition.onset[x]. The slices are unordered and Closed, and can be differentiated using the following discriminators:
| ||||
52. Condition.onset[x]:onsetDateTime | |||||
SliceName | onsetDateTime | ||||
Definition | Start of the disorder to which the problem applies. Especially in symptoms in which it takes longer for the final diagnosis, it is important to know not only the date of the diagnosis, but also how long the patient has had the disorder. A ‘vague’ date, such as only the year or the month and the year, is permitted. | ||||
Control | 0..1 | ||||
Type | dateTime | ||||
[x] Note | See Choice of Data Types for further information about how to use [x] | ||||
Summary | true | ||||
Alternate Names | ProbleemBeginDatum | ||||
Comments | Age is generally used when the patient reports an age at which the Condition began to occur. | ||||
53. Condition.abatement[x] | |||||
Definition | The date or estimated date that the condition resolved or went into remission. This is called "abatement" because of the many overloaded connotations associated with "remission" or "resolution" - Conditions are never really resolved, but they can abate. | ||||
Control | 0..1 This element is affected by the following invariants: con-4 | ||||
Type | dateTime | ||||
[x] Note | See Choice of Data Types for further information about how to use [x] | ||||
Comments | There is no explicit distinction between resolution and remission because in many cases the distinction is not clear. Age is generally used when the patient reports an age at which the Condition abated. If there is no abatement element, it is unknown whether the condition has resolved or entered remission; applications and users should generally assume that the condition is still valid. When abatementString exists, it implies the condition is abated. | ||||
Slicing | This element introduces a set of slices on Condition.abatement[x]. The slices are unordered and Closed, and can be differentiated using the following discriminators:
| ||||
54. Condition.abatement[x]:abatementDateTime | |||||
SliceName | abatementDateTime | ||||
Definition | Date on which the disorder to which the problem applies, is considered not to be present anymore. This date does not need to be the same as the date of the change in problem status. A ‘vague’ date, such as only the year or the month and the year, is permitted. | ||||
Control | 0..1 This element is affected by the following invariants: con-4 | ||||
Type | dateTime | ||||
[x] Note | See Choice of Data Types for further information about how to use [x] | ||||
Must Support | true | ||||
Alternate Names | ProbleemEindDatum | ||||
Comments | There is no explicit distinction between resolution and remission because in many cases the distinction is not clear. Age is generally used when the patient reports an age at which the Condition abated. If there is no abatement element, it is unknown whether the condition has resolved or entered remission; applications and users should generally assume that the condition is still valid. When abatementString exists, it implies the condition is abated. | ||||
55. Condition.assertedDate | |||||
Definition | The date on which the existance of the Condition was first asserted or acknowledged. | ||||
Control | 0..1 | ||||
Type | dateTime | ||||
Summary | true | ||||
Comments | The assertedDate represents the date when this particular Condition record was created in the EHR, not the date of the most recent update in terms of when severity, abatement, etc. were specified. The date of the last record modification can be retrieved from the resource metadata. | ||||
56. Condition.asserter | |||||
Definition | Individual who is making the condition statement. | ||||
Control | 0..1 | ||||
Type | Reference(nl-core-relatedperson|nl-core-patient|nl-core-practitioner) | ||||
Summary | true | ||||
57. Condition.asserter.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
58. Condition.asserter.extension | |||||
Definition | An Extension | ||||
Control | 0..* | ||||
Type | Extension | ||||
Slicing | This element introduces a set of slices on Condition.asserter.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
59. Condition.asserter.extension:practitionerRole | |||||
SliceName | practitionerRole | ||||
Definition | Optional Extension Element - found in all resources. | ||||
Control | 0..1 | ||||
Type | Extension(PractitionerRole Reference) (Extension Type: Reference) | ||||
60. Condition.asserter.reference | |||||
Definition | A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. | ||||
Control | 0..1 This element is affected by the following invariants: ref-1 | ||||
Type | string | ||||
Summary | true | ||||
Comments | Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. | ||||
61. Condition.asserter.identifier | |||||
Definition | An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. | ||||
Note | This is a business identifier, not a resource identifier (see discussion) | ||||
Control | 0..1 | ||||
Type | Identifier | ||||
Summary | true | ||||
Comments | When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. | ||||
62. Condition.asserter.display | |||||
Definition | Plain text narrative that identifies the resource in addition to the resource reference. | ||||
Control | 0..1 | ||||
Type | string | ||||
Summary | true | ||||
Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. | ||||
63. Condition.stage | |||||
Definition | Clinical stage or grade of a condition. May include formal severity assessments. | ||||
Control | 0..1 | ||||
Type | BackboneElement | ||||
Invariants | Defined on this element con-1: Stage SHALL have summary or assessment (: summary.exists() or assessment.exists()) ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) | ||||
64. Condition.stage.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
65. Condition.stage.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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. | ||||
66. Condition.stage.modifierExtension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Is Modifier | true | ||||
Summary | true | ||||
Alternate Names | extensions, user content, modifiers | ||||
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. | ||||
67. Condition.stage.summary | |||||
Definition | A simple summary of the stage such as "Stage 3". The determination of the stage is disease-specific. | ||||
Control | 0..1 This element is affected by the following invariants: con-1 | ||||
Binding | For example codes, see Condition Stage Codes describing condition stages (e.g. Cancer stages) | ||||
Type | CodeableConcept | ||||
68. Condition.stage.assessment | |||||
Definition | Reference to a formal record of the evidence on which the staging assessment is based. | ||||
Control | 0..* This element is affected by the following invariants: con-1 | ||||
Type | Reference(ClinicalImpression|DiagnosticReport|Observation) | ||||
69. Condition.evidence | |||||
Definition | Supporting Evidence / manifestations that are the basis on which this condition is suspected or confirmed. | ||||
Control | 0..* | ||||
Type | BackboneElement | ||||
Comments | The evidence may be a simple list of coded symptoms/manifestations, or references to observations or formal assessments, or both. | ||||
Invariants | Defined on this element con-2: evidence SHALL have code or details (: code.exists() or detail.exists()) ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) | ||||
70. Condition.evidence.id | |||||
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Control | 0..1 | ||||
Type | string | ||||
XML Representation | In the XML format, this property is represented as an attribute. | ||||
71. Condition.evidence.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Alternate Names | 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. | ||||
72. Condition.evidence.modifierExtension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Is Modifier | true | ||||
Summary | true | ||||
Alternate Names | extensions, user content, modifiers | ||||
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. | ||||
73. Condition.evidence.code | |||||
Definition | A manifestation or symptom that led to the recording of this condition. | ||||
Control | 0..* This element is affected by the following invariants: con-2 | ||||
Binding | For example codes, see Manifestation and Symptom Codes Codes that describe the manifestation or symptoms of a condition | ||||
Type | CodeableConcept | ||||
Summary | true | ||||
74. Condition.evidence.detail | |||||
Definition | Links to other relevant information, including pathology reports. | ||||
Control | 0..* This element is affected by the following invariants: con-2 | ||||
Type | Reference(Resource) | ||||
Summary | true | ||||
75. Condition.note | |||||
Definition | Comment by the one who determined or updated the Problem. | ||||
Control | 0..* | ||||
Type | Annotation | ||||
Must Support | true | ||||
Alternate Names | Toelichting |