Extensions for Using Data Elements from FHIR R5 in FHIR STU3
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR R5 in FHIR STU3 - Downloaded Version null See the Directory of published versions

Extension: ExtensionCondition_VerificationStatus - Detailed Descriptions

Page standards status: Trial-use Maturity Level: 0

Definitions for the ext-R5-Condition.verificationStatus extension.

Guidance on how to interpret the contents of this table can be foundhere

0. Extension
Definition

R5: Condition.verificationStatus additional types (CodeableConcept) additional types from child elements (coding)


Optional Extension Element - found in all resources.

ShortR5: unconfirmed | provisional | differential | confirmed | refuted | entered-in-error additional typesOptional Extensions Element
Comments

Element Condition.verificationStatus is mapped to FHIR STU3 element Condition.verificationStatus as SourceIsBroaderThanTarget. The mappings for Condition.verificationStatus do not cover the following types: CodeableConcept. The mappings for Condition.verificationStatus do not cover the following types based on type expansion: coding. The target context Condition.verificationStatus is a modifier element, so this extension does not need to be defined as a modifier. 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. The data type is CodeableConcept because verificationStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity.

Control0..1*
This element is affected by the following invariants: ele-1
Is Modifierfalse
Invariantsele-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())
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())
2. Extension.url
Definition

Source of the definition for the extension code - a logical name or a URL.

Shortidentifies the meaning of the extension
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.

Control1..1
Typeuri
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
XML FormatIn the XML format, this property is represented as an attribute.
Fixed Valuehttp://hl7.org/fhir/5.0/StructureDefinition/extension-Condition.verificationStatus
4. Extension.value[x]
Definition

The verification status to support the clinical status of the condition. The verification status pertains to the condition, itself, not to any specific condition attribute.


Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).

Shortunconfirmed | provisional | differential | confirmed | refuted | entered-in-errorValue of extension
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. The data type is CodeableConcept because verificationStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity.

Control0..1
BindingThe codes SHALL be taken from For codes, see ConditionVerificationStatus
(required to http://hl7.org/fhir/ValueSet/condition-ver-status|3.0.2)

The verification status to support or decline the clinical status of the condition or diagnosis.

TypeCodeableConcept, 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] NoteSeeChoice of Data Typesfor further information about how to use [x]

Guidance on how to interpret the contents of this table can be foundhere

0. Extension
Definition

R5: Condition.verificationStatus additional types (CodeableConcept) additional types from child elements (coding)

ShortR5: unconfirmed | provisional | differential | confirmed | refuted | entered-in-error additional types
Comments

Element Condition.verificationStatus is mapped to FHIR STU3 element Condition.verificationStatus as SourceIsBroaderThanTarget. The mappings for Condition.verificationStatus do not cover the following types: CodeableConcept. The mappings for Condition.verificationStatus do not cover the following types based on type expansion: coding. The target context Condition.verificationStatus is a modifier element, so this extension does not need to be defined as a modifier. 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. The data type is CodeableConcept because verificationStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity.

Control0..1
Is Modifierfalse
2. Extension.url
Control1..1
Fixed Valuehttp://hl7.org/fhir/5.0/StructureDefinition/extension-Condition.verificationStatus
4. Extension.value[x]
Definition

The verification status to support the clinical status of the condition. The verification status pertains to the condition, itself, not to any specific condition attribute.

Shortunconfirmed | provisional | differential | confirmed | refuted | entered-in-error
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. The data type is CodeableConcept because verificationStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity.

Control0..1
BindingThe codes SHALL be taken from ConditionVerificationStatus
(required to http://hl7.org/fhir/ValueSet/condition-ver-status|3.0.2)

The verification status to support or decline the clinical status of the condition or diagnosis.

TypeCodeableConcept, 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] NoteSeeChoice of Data Typesfor further information about how to use [x]

Guidance on how to interpret the contents of this table can be foundhere

0. Extension
Definition

R5: Condition.verificationStatus additional types (CodeableConcept) additional types from child elements (coding)

ShortR5: unconfirmed | provisional | differential | confirmed | refuted | entered-in-error additional types
Comments

Element Condition.verificationStatus is mapped to FHIR STU3 element Condition.verificationStatus as SourceIsBroaderThanTarget. The mappings for Condition.verificationStatus do not cover the following types: CodeableConcept. The mappings for Condition.verificationStatus do not cover the following types based on type expansion: coding. The target context Condition.verificationStatus is a modifier element, so this extension does not need to be defined as a modifier. 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. The data type is CodeableConcept because verificationStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity.

Control0..1
This element is affected by the following invariants: ele-1
Is Modifierfalse
Invariantsele-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())
2. Extension.id
Definition

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

Shortxml:id (or equivalent in JSON)
Control0..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
XML FormatIn the XML format, this property is represented as an attribute.
4. Extension.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.

ShortAdditional Content defined by implementations
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.

Control0..*
TypeExtension
Alternate Namesextensions, user content
SlicingThis element introduces a set of slices on Extension.extension. The slices areUnordered and Open, and can be differentiated using the following discriminators:
  • value @ url
  • 6. Extension.url
    Definition

    Source of the definition for the extension code - a logical name or a URL.

    Shortidentifies the meaning of the extension
    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.

    Control1..1
    Typeuri
    Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
    XML FormatIn the XML format, this property is represented as an attribute.
    Fixed Valuehttp://hl7.org/fhir/5.0/StructureDefinition/extension-Condition.verificationStatus
    8. Extension.value[x]
    Definition

    The verification status to support the clinical status of the condition. The verification status pertains to the condition, itself, not to any specific condition attribute.

    Shortunconfirmed | provisional | differential | confirmed | refuted | entered-in-error
    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. The data type is CodeableConcept because verificationStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity.

    Control0..1
    BindingThe codes SHALL be taken from ConditionVerificationStatus
    (required to http://hl7.org/fhir/ValueSet/condition-ver-status|3.0.2)

    The verification status to support or decline the clinical status of the condition or diagnosis.

    TypeCodeableConcept
    [x] NoteSeeChoice of Data Typesfor further information about how to use [x]