This page is part of the HSPC FHIR Implementation Guide (v0.1.0: Daft For Comment Draft) based on FHIR v1.9.0. This is the current published version. For a full list of available versions, see the Directory of published versions
Name | Flags | Card. | Type | Description & Constraints |
---|---|---|---|---|
Extension | 0..1 | |||
url | 1..1 | uri | "http://fhir.org/guides/hspc/StructureDefinition/hspc-delta-flag" | |
value[x] | 0..1 | code | Binding: DeltaFlag (required) | |
Documentation for this format |
Name | Flags | Card. | Type | Description & Constraints |
---|---|---|---|---|
Extension | I | 0..1 | Extension ext-1: Must have either extensions or value[x], not both | |
id | 0..1 | string | xml:id (or equivalent in JSON) | |
extension | 0..* | Extension | Additional Content defined by implementations | |
url | 1..1 | uri | "http://fhir.org/guides/hspc/StructureDefinition/hspc-delta-flag" | |
valueCode | 0..1 | code | Primitive Type code Binding: DeltaFlag (required) | |
Documentation for this format |
Extension(delta-flag) | |
Definition | Takes a value from the valueset listed in the model to indicate the data value in the containing model is a change from a previous instance of the same model. |
Control | 0..1 |
Comments | This model is intended to constrain values from OBX-8 in a lab result HL7 message. Because OBX-8 is overloaded to contain multiple types of data, we need a way to tell which kind of code is sent (abnormal flag, delta flag, or ordinal interpretation. |
Invariants | Defined on this element ext-1: Must have either extensions or value[x], not both (xpath: exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])) |
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. |
Control | 0..1 |
Type | string |
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. |
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. |
Extension.url | |
Definition | Source of the definition for the extension code - a logical name or a URL. |
Control | 1..1 |
Type | uri |
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://fhir.org/guides/hspc/StructureDefinition/hspc-delta-flag |
Extension.valueCode | |
Definition | A string which has at least one character and no leading or trailing whitespace and where there is no whitespace other than single spaces in the contents |
Control | 0..1 |
Type | code(code) |