Profile: CareConnect-GPC-Observation-1
| CareConnect-GPC-Observation-1 (Observation) | C | Observation | |
| id | Σ | 0..1 | id |
| meta | Σ | 0..1 | Meta |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| versionId | Σ | 0..1 | id |
| lastUpdated | Σ | 0..1 | instant |
| profile | Σ | 1..* | uri |
| security | Σ | 0..* | CodingBinding |
| tag | Σ | 0..* | Coding |
| implicitRules | Σ ?! | 0..1 | uri |
| language | 0..1 | codeBinding | |
| text | C | 0..1 | Narrative |
| contained | 0..* | Resource | |
| extension | C | 0..* | Extension |
| reason | S C | 0..* | Extension(CodeableConcept | Reference(CareConnect-Condition-1)) |
| modifierExtension | ?! C | 0..* | Extension |
| identifier | Σ | 1..* | Identifier |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| use | Σ ?! | 0..1 | codeBinding |
| type | Σ | 0..1 | CodeableConceptBinding |
| system | Σ | 1..1 | uri |
| value | Σ | 1..1 | string |
| period | Σ C | 0..1 | Period |
| assigner | Σ C | 0..1 | Reference(CareConnect-GPC-Organization-1) |
| basedOn | Σ C | 0..* | Reference(DeviceRequest | ImmunizationRecommendation | NutritionOrder | CareConnect-CarePlan-1 | CareConnect-GPC-MedicationRequest-1 | CareConnect-GPC-ProcedureRequest-1 | CareConnect-GPC-ReferralRequest-1) |
| status | Σ ?! | 1..1 | codeBinding |
| category | 0..* | CodeableConceptBinding | |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| coding | Σ | 0..* | Coding |
| snomedCT | Σ | 0..1 | Coding |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| snomedCTDescriptionID | C | 0..1 | Extension(Complex) |
| system | Σ | 1..1 | uriFixed Value |
| version | Σ | 0..0 | string |
| code | Σ | 1..1 | code |
| display | Σ | 1..1 | string |
| userSelected | Σ | 0..1 | boolean |
| text | Σ | 0..1 | string |
| code | Σ | 1..1 | CodeableConcept |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| coding | Σ | 0..* | Coding |
| snomedCT | Σ | 0..1 | Coding |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| snomedCTDescriptionID | C | 0..1 | Extension(Complex) |
| system | Σ | 1..1 | uriFixed Value |
| version | Σ | 0..0 | string |
| code | Σ | 1..1 | code |
| display | Σ | 1..1 | string |
| userSelected | Σ | 0..1 | boolean |
| text | Σ | 0..1 | string |
| subject | S Σ C | 1..1 | Reference(CareConnect-GPC-Patient-1) |
| context | S C | 0..1 | Reference(CareConnect-GPC-Encounter-1) |
| effective[x] | S Σ | 0..1 | |
| effectiveDateTime | dateTime | ||
| effectivePeriod | Period | ||
| issued | S Σ | 1..1 | instant |
| performer | S Σ C | 0..* | Reference(CareConnect-RelatedPerson-1 | CareConnect-GPC-Organization-1 | CareConnect-GPC-Patient-1 | CareConnect-GPC-Practitioner-1) |
| value[x] | S Σ C | 0..1 | |
| valueAttachment | Attachment | ||
| valueBoolean | boolean | ||
| valueCodeableConcept | CodeableConcept | ||
| valueDateTime | dateTime | ||
| valuePeriod | Period | ||
| valueQuantity | CareConnect-Quantity-1 | ||
| valueRange | Range | ||
| valueRatio | Ratio | ||
| valueSampledData | SampledData | ||
| valueString | string | ||
| valueTime | time | ||
| dataAbsentReason | S C | 0..1 | CodeableConceptBinding |
| interpretation | S | 0..1 | CodeableConceptBinding |
| comment | S | 0..1 | string |
| bodySite | S | 0..1 | CodeableConcept |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| coding | Σ | 0..* | Coding |
| snomedCT | Σ | 0..1 | CodingBinding |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| snomedCTDescriptionID | C | 0..1 | Extension(Complex) |
| system | Σ | 1..1 | uriFixed Value |
| version | Σ | 0..0 | string |
| code | Σ | 1..1 | code |
| display | Σ | 1..1 | string |
| userSelected | Σ | 0..1 | boolean |
| text | Σ | 0..1 | string |
| method | S | 0..1 | CodeableConcept |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| coding | Σ | 0..* | Coding |
| snomedCT | Σ | 0..1 | Coding |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| snomedCTDescriptionID | C | 0..1 | Extension(Complex) |
| system | Σ | 1..1 | uriFixed Value |
| version | Σ | 0..0 | string |
| code | Σ | 1..1 | code |
| display | Σ | 1..1 | string |
| userSelected | Σ | 0..1 | boolean |
| text | Σ | 0..1 | string |
| specimen | S C | 0..1 | Reference(CareConnect-GPC-Specimen-1) |
| device | S C | 0..1 | Reference(DeviceMetric | GPConnect-Device-1) |
| referenceRange | S C | 0..* | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| low | C | 0..1 | SimpleQuantity |
| high | C | 0..1 | SimpleQuantity |
| type | 0..1 | CodeableConceptBinding | |
| appliesTo | 0..* | CodeableConcept | |
| age | C | 0..1 | Range |
| text | 0..1 | string | |
| related | S Σ | 0..* | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| type | S | 0..1 | codeBinding |
| target | C | 1..1 | Reference(QuestionnaireResponse | Sequence | CareConnect-GPC-Observation-1) |
| component | S Σ | 0..* | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| code | Σ | 1..1 | CodeableConcept |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| coding | Σ | 0..* | Coding |
| snomedCT | Σ | 0..1 | Coding |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| snomedCTDescriptionID | C | 0..1 | Extension(Complex) |
| system | Σ | 1..1 | uriFixed Value |
| version | Σ | 0..0 | string |
| code | Σ | 1..1 | code |
| display | Σ | 1..1 | string |
| userSelected | Σ | 0..1 | boolean |
| text | Σ | 0..1 | string |
| value[x] | Σ | 0..1 | |
| valueAttachment | Attachment | ||
| valueCodeableConcept | CodeableConcept | ||
| valueDateTime | dateTime | ||
| valuePeriod | Period | ||
| valueQuantity | CareConnect-Quantity-1 | ||
| valueRange | Range | ||
| valueRatio | Ratio | ||
| valueSampledData | SampledData | ||
| valueString | string | ||
| valueTime | time | ||
| dataAbsentReason | S C | 0..1 | CodeableConceptBinding |
| interpretation | 0..1 | CodeableConceptBinding | |
| referenceRange | 0..* | see (referenceRange) |
| Observation | |||
| Short | Measurements and simple assertions | ||
| Definition | Measurements and simple assertions made about a patient, device or other subject. | ||
| Cardinality | 0..* | ||
| Alias | Vital Signs, Measurement, Results, Tests | ||
| Comments | Used for simple observations such as device measurements, laboratory atomic results, vital signs, height, weight, smoking status, comments, etc. Other resources are used to provide context for observations such as lab reports, etc. | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.id | |||
| Short | Logical id of this artifact | ||
| Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. | ||
| Cardinality | 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.meta | |||
| Short | Metadata about the resource | ||
| 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. | ||
| Cardinality | 0..1 | ||
| Type | Meta | ||
| Summary | True | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.meta.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| 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 | string | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.meta.extension | |||
| Short | Additional Content defined by implementations | ||
| 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. | ||
| 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) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.meta.versionId | |||
| Short | Version specific identifier | ||
| Definition | The version specific identifier, as it appears in the version portion of the URL. This values changes when the resource is created, updated, or deleted. | ||
| Cardinality | 0..1 | ||
| Type | id | ||
| Summary | True | ||
| Comments | The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.meta.lastUpdated | |||
| Short | When the resource version last changed | ||
| Definition | When the resource last changed - e.g. when the version changed. | ||
| Cardinality | 0..1 | ||
| Type | instant | ||
| Summary | True | ||
| Comments | This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.meta.profile | |||
| Short | Profiles this resource claims to conform to | ||
| Definition | A list of profiles (references to StructureDefinition resources) that this resource claims to conform to. The URL is a reference to StructureDefinition.url. | ||
| Cardinality | 1..* | ||
| Type | uri | ||
| Summary | True | ||
| Comments | It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.meta.security | |||
| Short | Security Labels applied to this resource | ||
| Definition | Security labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure. | ||
| Cardinality | 0..* | ||
| Type | Coding | ||
| Binding | Security Labels from the Healthcare Privacy and Security Classification System. | ||
| Summary | True | ||
| Comments | The security labels can be updated without changing the stated version of the resource The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.meta.tag | |||
| Short | Tags applied to this resource | ||
| Definition | Tags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource. | ||
| Cardinality | 0..* | ||
| Type | Coding | ||
| Binding | Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones" | ||
| Summary | True | ||
| Comments | The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.implicitRules | |||
| Short | A set of rules under which this content was created | ||
| 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. | ||
| Cardinality | 0..1 | ||
| Type | uri | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.language | |||
| Short | Language of the resource content | ||
| Definition | The base language in which the resource is written. | ||
| Cardinality | 0..1 | ||
| Type | code | ||
| Binding | A human language. Binding extensions
| ||
| 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). | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.text | |||
| Short | Text summary of the resource, for human interpretation | ||
| 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. | ||
| Cardinality | 0..1 | ||
| Type | Narrative | ||
| Alias | 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, dom-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.contained | |||
| Short | Contained, inline Resources | ||
| 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. | ||
| Cardinality | 0..* | ||
| Type | Resource | ||
| Alias | 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. | ||
| Mappings |
| ||
| Observation.extension | |||
| Short | Additional Content defined by implementations | ||
| 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. | ||
| 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) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.extension:reason | |||
| Short | Reason resource added/performed/given | ||
| Definition | Reason resource added/performed/given. | ||
| Cardinality | 0..* | ||
| Type | Extension(CodeableConcept | Reference(CareConnect-Condition-1)) | ||
| Must Support | True | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.modifierExtension | |||
| Short | Extensions that cannot be ignored | ||
| 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. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| 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) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.identifier | |||
| Short | Business Identifier for observation | ||
| Definition | A unique identifier assigned to this observation. | ||
| Cardinality | 1..* | ||
| Type | Identifier | ||
| Summary | True | ||
| Requirements | Allows observations to be distinguished and referenced. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.identifier.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| 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 | string | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.identifier.extension | |||
| Short | Additional Content defined by implementations | ||
| 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. | ||
| 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) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.identifier.use | |||
| Short | usual | official | temp | secondary (If known) | ||
| Definition | The purpose of this identifier. | ||
| Cardinality | 0..1 | ||
| Type | code | ||
| Binding | Identifies the purpose for this identifier, if known . | ||
| Modifier | True | ||
| Summary | True | ||
| Requirements | Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. | ||
| Comments | This is labeled as "Is Modifier" because applications should not mistake a temporary id for a permanent one. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.identifier.type | |||
| Short | Description of identifier | ||
| Definition | A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. | ||
| Cardinality | 0..1 | ||
| Type | CodeableConcept | ||
| Binding | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. | ||
| Summary | True | ||
| Requirements | Allows users to make use of identifiers when the identifier system is not known. | ||
| Comments | This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.identifier.system | |||
| Short | The namespace for the identifier value | ||
| Definition | Establishes the namespace for the value - that is, a URL that describes a set values that are unique. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Summary | True | ||
| Requirements | There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. | ||
| Comments | see http://en.wikipedia.org/wiki/Uniform_resource_identifier | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Examples | Generalhttp://www.acme.com/identifiers/patient | ||
| Mappings |
| ||
| Observation.identifier.value | |||
| Short | The value that is unique | ||
| Definition | The portion of the identifier typically relevant to the user and which is unique within the context of the system. | ||
| Cardinality | 1..1 | ||
| Type | string | ||
| Summary | True | ||
| Comments | If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Examples | General123456 | ||
| Mappings |
| ||
| Observation.identifier.period | |||
| Short | Time period when id is/was valid for use | ||
| Definition | Time period during which identifier is/was valid for use. | ||
| Cardinality | 0..1 | ||
| Type | Period | ||
| Summary | True | ||
| Comments | This is not a duration - that's a measure of time (a separate type), but a duration that occurs at a fixed value of time. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). If duration is required, specify the type as Interval|Duration. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.identifier.assigner | |||
| Short | Organization that issued id (may be just text) | ||
| Definition | Organization that issued/manages the identifier. | ||
| Cardinality | 0..1 | ||
| Type | Reference(CareConnect-GPC-Organization-1) | ||
| Summary | True | ||
| Comments | The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.basedOn | |||
| Short | Fulfills plan, proposal or order | ||
| Definition | A plan, proposal or order that is fulfilled in whole or in part by this event. | ||
| Cardinality | 0..* | ||
| Type | Reference(DeviceRequest | ImmunizationRecommendation | NutritionOrder | CareConnect-CarePlan-1 | CareConnect-GPC-MedicationRequest-1 | CareConnect-GPC-ProcedureRequest-1 | CareConnect-GPC-ReferralRequest-1) | ||
| Summary | True | ||
| Alias | Fulfills | ||
| Requirements | Allows tracing of authorization for the event and tracking whether proposals/recommendations were acted upon. | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.status | |||
| Short | registered | preliminary | final | amended + | ||
| Definition | The status of the result value. In GP systems these are most likely to be ‘final’ however ‘preliminary’ reports are possible as for example, some work can be sub-contracted to other labs. If the system is not able to determine the status of a test group header then it should default to the ‘unknown’ value. | ||
| Cardinality | 1..1 | ||
| Type | code | ||
| Binding | Codes providing the status of an observation. | ||
| Modifier | True | ||
| Summary | True | ||
| Requirements | Need to track the status of individual results. Some results are finalized before the whole report is finalized. | ||
| Comments | This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.category | |||
| Short | Classification of type of observation | ||
| Definition | A code that classifies the general type of observation being made. | ||
| Cardinality | 0..* | ||
| Type | CodeableConcept | ||
| Binding | Codes for high level observation categories. | ||
| Requirements | Used for filtering what observations are retrieved and displayed. | ||
| Comments | In addition to the required category valueset, this element allows various categorization schemes based on the owner’s definition of the category and effectively multiple categories can be used at once. The level of granularity is defined by the category concepts in the value set. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.category.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| 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 | string | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.category.extension | |||
| Short | Additional Content defined by implementations | ||
| 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. | ||
| 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) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.category.coding | |||
| Short | Code defined by a terminology system | ||
| Definition | A reference to a code defined by a terminology system. | ||
| Cardinality | 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. | ||
| Slicing | Unordered, Open, by system(Value) | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.category.coding:snomedCT | |||
| Short | Code defined by a terminology system | ||
| Definition | A reference to a code defined by a terminology system. | ||
| Cardinality | 0..1 | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.category.coding:snomedCT.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| 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 | string | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.category.coding:snomedCT.extension | |||
| Short | Additional Content defined by implementations | ||
| 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. | ||
| 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) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.category.coding:snomedCT.extension:snomedCTDescriptionID | |||
| Short | The SNOMED CT Description ID for the display | ||
| Definition | The SNOMED CT Description ID for the display. | ||
| Cardinality | 0..1 | ||
| Type | Extension(Complex) | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.category.coding:snomedCT.system | |||
| Short | Identity of the terminology system | ||
| Definition | The identification of the code system that defines the meaning of the symbol in the code. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Summary | True | ||
| Requirements | Need to be unambiguous about the source of the definition of the symbol. | ||
| Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | http://snomed.info/sct | ||
| Mappings |
| ||
| Observation.category.coding:snomedCT.version | |||
| Short | Version of the system - if relevant | ||
| Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. | ||
| Cardinality | 0..0 | ||
| Type | string | ||
| Summary | True | ||
| Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.category.coding:snomedCT.code | |||
| Short | Symbol in syntax defined by the system | ||
| Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). | ||
| Cardinality | 1..1 | ||
| Type | code | ||
| Summary | True | ||
| Requirements | Need to refer to a particular code in the system. | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.category.coding:snomedCT.display | |||
| Short | Representation defined by the system | ||
| Definition | A representation of the meaning of the code in the system, following the rules of the system. | ||
| Cardinality | 1..1 | ||
| Type | string | ||
| Summary | True | ||
| Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.category.coding:snomedCT.userSelected | |||
| Short | If this coding was chosen directly by the user | ||
| Definition | Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). | ||
| Cardinality | 0..1 | ||
| Type | boolean | ||
| Summary | True | ||
| Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. | ||
| Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.category.text | |||
| Short | Plain text representation of the concept | ||
| 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. | ||
| Cardinality | 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.code | |||
| Short | Type of observation (code / type) | ||
| Definition | Describes what was observed. Sometimes this is called the observation "name". | ||
| Cardinality | 1..1 | ||
| Type | CodeableConcept | ||
| Binding | Codes identifying names of simple observations. | ||
| Summary | True | ||
| Alias | Name | ||
| Requirements | Knowing what kind of observation is being made is essential to understanding the observation. | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.code.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| 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 | string | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.code.extension | |||
| Short | Additional Content defined by implementations | ||
| 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. | ||
| 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) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.code.coding | |||
| Short | Code defined by a terminology system | ||
| Definition | A reference to a code defined by a terminology system. | ||
| Cardinality | 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. | ||
| Slicing | Unordered, Open, by system(Value) | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.code.coding:snomedCT | |||
| Short | Code defined by a terminology system | ||
| Definition | A reference to a code defined by a terminology system. | ||
| Cardinality | 0..1 | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.code.coding:snomedCT.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| 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 | string | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.code.coding:snomedCT.extension | |||
| Short | Additional Content defined by implementations | ||
| 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. | ||
| 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) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.code.coding:snomedCT.extension:snomedCTDescriptionID | |||
| Short | The SNOMED CT Description ID for the display | ||
| Definition | The SNOMED CT Description ID for the display. | ||
| Cardinality | 0..1 | ||
| Type | Extension(Complex) | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.code.coding:snomedCT.system | |||
| Short | Identity of the terminology system | ||
| Definition | The identification of the code system that defines the meaning of the symbol in the code. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Summary | True | ||
| Requirements | Need to be unambiguous about the source of the definition of the symbol. | ||
| Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | http://snomed.info/sct | ||
| Mappings |
| ||
| Observation.code.coding:snomedCT.version | |||
| Short | Version of the system - if relevant | ||
| Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. | ||
| Cardinality | 0..0 | ||
| Type | string | ||
| Summary | True | ||
| Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.code.coding:snomedCT.code | |||
| Short | Symbol in syntax defined by the system | ||
| Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). | ||
| Cardinality | 1..1 | ||
| Type | code | ||
| Summary | True | ||
| Requirements | Need to refer to a particular code in the system. | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.code.coding:snomedCT.display | |||
| Short | Representation defined by the system | ||
| Definition | A representation of the meaning of the code in the system, following the rules of the system. | ||
| Cardinality | 1..1 | ||
| Type | string | ||
| Summary | True | ||
| Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.code.coding:snomedCT.userSelected | |||
| Short | If this coding was chosen directly by the user | ||
| Definition | Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). | ||
| Cardinality | 0..1 | ||
| Type | boolean | ||
| Summary | True | ||
| Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. | ||
| Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.code.text | |||
| Short | Plain text representation of the concept | ||
| 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. | ||
| Cardinality | 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.subject | |||
| Short | Who and/or what this is about | ||
| Definition | The patient, or group of patients, location, or device whose characteristics (direct or indirect) are described by the observation and into whose record the observation is placed. Comments: Indirect characteristics may be those of a specimen, fetus, donor, other observer (for example a relative or EMT), or any observation made about the subject. | ||
| Cardinality | 1..1 | ||
| Type | Reference(CareConnect-GPC-Patient-1) | ||
| Must Support | True | ||
| Summary | True | ||
| Requirements | Observations have no value if you don't know who or what they're about. | ||
| Comments | One would expect this element to be a cardinality of 1..1. The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated. If the target of the observation is different than the subject, the general extension observation-focal-subject. may be used. However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.context | |||
| Short | Healthcare event during which this observation is made | ||
| Definition | The healthcare event (e.g. a patient and healthcare provider interaction) during which this observation is made. | ||
| Cardinality | 0..1 | ||
| Type | Reference(CareConnect-GPC-Encounter-1) | ||
| Must Support | True | ||
| Alias | Encounter | ||
| Requirements | For some observations it may be important to know the link between an observation and a particular encounter. | ||
| Comments | This will typically be the encounter the event occurred within, but some events may be initiated prior to or after the official completion of an encounter or episode but still be tied to the context of the encounter or episode (e.g. pre-admission lab tests). | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.effective[x] | |||
| Short | Clinically relevant time/time-period for observation | ||
| Definition | The time or time-period the observed value is asserted as being true. For biological subjects - e.g. human patients - this is usually called the "physiologically relevant time". This is usually either the time of the procedure or of specimen collection, but very often the source of the date/time is not known, only the date/time itself. | ||
| Cardinality | 0..1 | ||
| Type | dateTime | Period | ||
| Must Support | True | ||
| Summary | True | ||
| Alias | Occurrence | ||
| Requirements | Knowing when an observation was deemed true is important to its relevance as well as determining trends. | ||
| Comments | At least a date should be present unless this observation is a historical report. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.issued | |||
| Short | Date/Time this was made available | ||
| Definition | The date and time this observation was made available to providers, typically after the results have been reviewed and verified. | ||
| Cardinality | 1..1 | ||
| Type | instant | ||
| Must Support | True | ||
| Summary | True | ||
| Comments | Updated when the result is updated. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.performer | |||
| Short | Who is responsible for the observation | ||
| Definition | Who was responsible for asserting the observed value as "true". | ||
| Cardinality | 0..* | ||
| Type | Reference(CareConnect-RelatedPerson-1 | CareConnect-GPC-Organization-1 | CareConnect-GPC-Patient-1 | CareConnect-GPC-Practitioner-1) | ||
| Must Support | True | ||
| Summary | True | ||
| Requirements | May give a degree of confidence in the observation and also indicates where follow-up questions should be directed. | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.value[x] | |||
| Short | Actual result | ||
| Definition | The information determined as a result of making the observation, if the information has a simple value. | ||
| Cardinality | 0..1 | ||
| Type | Attachment | boolean | CodeableConcept | dateTime | Period | CareConnect-Quantity-1 | Range | Ratio | SampledData | string | time | ||
| Must Support | True | ||
| Summary | True | ||
| Requirements | An observation exists to have a value, though it may not if it is in error, or if it represents a group of observations. | ||
| Comments | Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is "'value' + the type name" with a capital on the first letter of the type). If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text. A value set is bound to the ValueCodeableConcept element. For further discussion and examples see the notes section below. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, obs-7 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.dataAbsentReason | |||
| Short | Why the result is missing | ||
| Definition | Provides a reason why the expected value in the element Observation.value[x] is missing. | ||
| Cardinality | 0..1 | ||
| Type | CodeableConcept | ||
| Binding | Codes specifying why the result (Observation.value[x]) is missing. | ||
| Must Support | True | ||
| Requirements | For many results it is necessary to handle exceptional values in measurements. | ||
| Comments | Null or exceptional values can be represented two ways in FHIR Observations. One way is to simply include them in the value set and represent the exceptions in the value. For example, measurement values for a serology test could be "detected", "not detected", "inconclusive", or "specimen unsatisfactory". The alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values. For example, the dataAbsentReason code "error" could be used when the measurement was not completed. Note that an observation may only be reported if there are values to report. For example differential cell counts values may be reported only when > 0. Because of these options, use-case agreements are required to interpret general observations for null or exceptional values. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, obs-6 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.interpretation | |||
| Short | High, low, normal, etc. | ||
| Definition | A human readable clinical summary relating to a test result and/or additional notes provided by the laboratory e.g. the specimen has haemolysed or has leaked | ||
| Cardinality | 0..1 | ||
| Type | CodeableConcept | ||
| Binding | Codes identifying interpretations of observations. | ||
| Must Support | True | ||
| Alias | Abnormal Flag | ||
| Requirements | For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.comment | |||
| Short | Comments about result | ||
| Definition | May include statements about significant, unexpected or unreliable values, or information about the source of the value where this may be relevant to the interpretation of the result. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Must Support | True | ||
| Requirements | Need to be able to provide free text additional information. | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.bodySite | |||
| Short | Observed body part | ||
| Definition | Indicates the site on the subject's body where the observation was made (i.e. the target site). | ||
| Cardinality | 0..1 | ||
| Type | CodeableConcept | ||
| Binding | Codes describing anatomical locations. May include laterality. | ||
| Must Support | True | ||
| Comments | Only used if not implicit in code found in Observation.code. In many systems, this may be represented as a related observation instead of an inline component. If the use case requires BodySite to be handled as a separate resource (e.g. to identify and track separately) then use the standard extension body-site-instance. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.bodySite.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| 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 | string | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.bodySite.extension | |||
| Short | Additional Content defined by implementations | ||
| 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. | ||
| 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) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.bodySite.coding | |||
| Short | Code defined by a terminology system | ||
| Definition | A reference to a code defined by a terminology system. | ||
| Cardinality | 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. | ||
| Slicing | Unordered, Open, by system(Value) | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.bodySite.coding:snomedCT | |||
| Short | Code defined by a terminology system | ||
| Definition | A reference to a code defined by a terminology system. | ||
| Cardinality | 0..1 | ||
| Type | Coding | ||
| Binding | A code from the SNOMED Clinical Terminology UK with the expression (<<442083009 |anatomical or acquired body structure|). | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.bodySite.coding:snomedCT.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| 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 | string | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.bodySite.coding:snomedCT.extension | |||
| Short | Additional Content defined by implementations | ||
| 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. | ||
| 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) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.bodySite.coding:snomedCT.extension:snomedCTDescriptionID | |||
| Short | The SNOMED CT Description ID for the display | ||
| Definition | The SNOMED CT Description ID for the display. | ||
| Cardinality | 0..1 | ||
| Type | Extension(Complex) | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.bodySite.coding:snomedCT.system | |||
| Short | Identity of the terminology system | ||
| Definition | The identification of the code system that defines the meaning of the symbol in the code. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Summary | True | ||
| Requirements | Need to be unambiguous about the source of the definition of the symbol. | ||
| Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | http://snomed.info/sct | ||
| Mappings |
| ||
| Observation.bodySite.coding:snomedCT.version | |||
| Short | Version of the system - if relevant | ||
| Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. | ||
| Cardinality | 0..0 | ||
| Type | string | ||
| Summary | True | ||
| Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.bodySite.coding:snomedCT.code | |||
| Short | Symbol in syntax defined by the system | ||
| Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). | ||
| Cardinality | 1..1 | ||
| Type | code | ||
| Summary | True | ||
| Requirements | Need to refer to a particular code in the system. | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.bodySite.coding:snomedCT.display | |||
| Short | Representation defined by the system | ||
| Definition | A representation of the meaning of the code in the system, following the rules of the system. | ||
| Cardinality | 1..1 | ||
| Type | string | ||
| Summary | True | ||
| Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.bodySite.coding:snomedCT.userSelected | |||
| Short | If this coding was chosen directly by the user | ||
| Definition | Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). | ||
| Cardinality | 0..1 | ||
| Type | boolean | ||
| Summary | True | ||
| Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. | ||
| Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.bodySite.text | |||
| Short | Plain text representation of the concept | ||
| 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. | ||
| Cardinality | 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.method | |||
| Short | How it was done | ||
| Definition | Indicates the mechanism used to perform the observation. | ||
| Cardinality | 0..1 | ||
| Type | CodeableConcept | ||
| Binding | Methods for simple observations. | ||
| Must Support | True | ||
| Requirements | In some cases, method can impact results and is thus used for determining whether results can be compared or determining significance of results. | ||
| Comments | Only used if not implicit in code for Observation.code. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.method.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| 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 | string | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.method.extension | |||
| Short | Additional Content defined by implementations | ||
| 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. | ||
| 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) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.method.coding | |||
| Short | Code defined by a terminology system | ||
| Definition | A reference to a code defined by a terminology system. | ||
| Cardinality | 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. | ||
| Slicing | Unordered, Open, by system(Value) | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.method.coding:snomedCT | |||
| Short | Code defined by a terminology system | ||
| Definition | A reference to a code defined by a terminology system. | ||
| Cardinality | 0..1 | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.method.coding:snomedCT.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| 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 | string | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.method.coding:snomedCT.extension | |||
| Short | Additional Content defined by implementations | ||
| 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. | ||
| 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) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.method.coding:snomedCT.extension:snomedCTDescriptionID | |||
| Short | The SNOMED CT Description ID for the display | ||
| Definition | The SNOMED CT Description ID for the display. | ||
| Cardinality | 0..1 | ||
| Type | Extension(Complex) | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.method.coding:snomedCT.system | |||
| Short | Identity of the terminology system | ||
| Definition | The identification of the code system that defines the meaning of the symbol in the code. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Summary | True | ||
| Requirements | Need to be unambiguous about the source of the definition of the symbol. | ||
| Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | http://snomed.info/sct | ||
| Mappings |
| ||
| Observation.method.coding:snomedCT.version | |||
| Short | Version of the system - if relevant | ||
| Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. | ||
| Cardinality | 0..0 | ||
| Type | string | ||
| Summary | True | ||
| Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.method.coding:snomedCT.code | |||
| Short | Symbol in syntax defined by the system | ||
| Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). | ||
| Cardinality | 1..1 | ||
| Type | code | ||
| Summary | True | ||
| Requirements | Need to refer to a particular code in the system. | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.method.coding:snomedCT.display | |||
| Short | Representation defined by the system | ||
| Definition | A representation of the meaning of the code in the system, following the rules of the system. | ||
| Cardinality | 1..1 | ||
| Type | string | ||
| Summary | True | ||
| Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.method.coding:snomedCT.userSelected | |||
| Short | If this coding was chosen directly by the user | ||
| Definition | Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). | ||
| Cardinality | 0..1 | ||
| Type | boolean | ||
| Summary | True | ||
| Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. | ||
| Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.method.text | |||
| Short | Plain text representation of the concept | ||
| 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. | ||
| Cardinality | 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.specimen | |||
| Short | Specimen used for this observation | ||
| Definition | The specimen that was used when this observation was made. | ||
| Cardinality | 0..1 | ||
| Type | Reference(CareConnect-GPC-Specimen-1) | ||
| Must Support | True | ||
| Comments | Should only be used if not implicit in code found in | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.device | |||
| Short | (Measurement) Device | ||
| Definition | The device used to generate the observation data. | ||
| Cardinality | 0..1 | ||
| Type | Reference(DeviceMetric | GPConnect-Device-1) | ||
| Must Support | True | ||
| Comments | An extension should be used if further typing of the device is needed. Devices used to support obtaining an observation can be represented using either an extension or through the Observation.related element. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.referenceRange | |||
| Short | Provides guide for interpretation | ||
| Definition | Guidance on how to interpret the value by comparison to a normal or recommended range. | ||
| Cardinality | 0..* | ||
| Type | BackboneElement | ||
| Must Support | True | ||
| Requirements | Knowing what values are considered "normal" can help evaluate the significance of a particular result. Need to be able to provide multiple reference ranges for different contexts. | ||
| Comments | Most observations only have one generic reference range. Systems MAY choose to restrict to only supplying the relevant reference range based on knowledge about the patient (e.g., specific to the patient's age, gender, weight and other factors), but this may not be possible or appropriate. Whenever more than one reference range is supplied, the differences between them SHOULD be provided in the reference range and/or age properties. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.referenceRange.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| 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 | string | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.referenceRange.extension | |||
| Short | Additional Content defined by implementations | ||
| 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. | ||
| 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) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.referenceRange.modifierExtension | |||
| Short | Extensions that cannot be ignored | ||
| 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. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| Summary | True | ||
| Alias | 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.referenceRange.low | |||
| Short | Low Range, if relevant | ||
| Definition | The value of the low bound of the reference range. The low bound of the reference range endpoint is inclusive of the value (e.g. reference range is >=5 - <=9). If the low bound is omitted, it is assumed to be meaningless (e.g. reference range is <=2.3). | ||
| Cardinality | 0..1 | ||
| Type | SimpleQuantity | ||
| Comments | The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, obs-3 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.referenceRange.high | |||
| Short | High Range, if relevant | ||
| Definition | The value of the high bound of the reference range. The high bound of the reference range endpoint is inclusive of the value (e.g. reference range is >=5 - <=9). If the high bound is omitted, it is assumed to be meaningless (e.g. reference range is >= 2.3). | ||
| Cardinality | 0..1 | ||
| Type | SimpleQuantity | ||
| Comments | The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, obs-3 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.referenceRange.type | |||
| Short | Reference range qualifier | ||
| Definition | Codes to indicate the what part of the targeted reference population it applies to. For example, the normal or therapeutic range. | ||
| Cardinality | 0..1 | ||
| Type | CodeableConcept | ||
| Binding | Code for the meaning of a reference range. | ||
| Requirements | Need to be able to say what kind of reference range this is - normal, recommended, therapeutic, etc, - for proper interpretation. | ||
| Comments | This SHOULD be populated if there is more than one range. If this element is not present then the normal range is assumed. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.referenceRange.appliesTo | |||
| Short | Reference range population | ||
| Definition | Codes to indicate the target population this reference range applies to. For example, a reference range may be based on the normal population or a particular sex or race. | ||
| Cardinality | 0..* | ||
| Type | CodeableConcept | ||
| Binding | Codes identifying the population the reference range applies to. | ||
| Requirements | Need to be able to identify the target population for proper interpretation. | ||
| Comments | This SHOULD be populated if there is more than one range. If this element is not present then the normal population is assumed. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.referenceRange.age | |||
| Short | Applicable age range, if relevant | ||
| Definition | The age at which this reference range is applicable. This is a neonatal age (e.g. number of weeks at term) if the meaning says so. | ||
| Cardinality | 0..1 | ||
| Type | Range | ||
| Requirements | Some analytes vary greatly over age. | ||
| Comments | The stated low and high value are assumed to have arbitrarily high precision when it comes to determining which values are in the range. I.e. 1.99 is not in the range 2 -> 3. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.referenceRange.text | |||
| Short | Text based reference range in an observation | ||
| Definition | Text based reference range in an observation which may be used when a quantitative range is not appropriate for an observation. An example would be a reference value of "Negative" or a list or table of 'normals'. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.related | |||
| Short | Resource related to this observation | ||
| Definition | A reference to another resource (usually another Observation) whose relationship is defined by the relationship type code. | ||
| Cardinality | 0..* | ||
| Type | BackboneElement | ||
| Must Support | True | ||
| Summary | True | ||
| Requirements | Normally, an observation will have either a value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and a set of related observations or sometimes a QuestionnaireResponse from which the measure is derived. | ||
| Comments | For a discussion on the ways Observations can assembled in groups together see Notes below. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.related.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| 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 | string | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.related.extension | |||
| Short | Additional Content defined by implementations | ||
| 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. | ||
| 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) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.related.modifierExtension | |||
| Short | Extensions that cannot be ignored | ||
| 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. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| Summary | True | ||
| Alias | 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.related.type | |||
| Short | has-member | derived-from | sequel-to | replaces | qualified-by | interfered-by | ||
| Definition | A code specifying the kind of relationship that exists with the target resource. | ||
| Cardinality | 0..1 | ||
| Type | code | ||
| Binding | Codes specifying how two observations are related. | ||
| Must Support | True | ||
| Requirements | A relationship type SHOULD be provided. | ||
| Comments | The "derived-from" type is the only logical choice when referencing the QuestionnaireAnswer resource. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.related.target | |||
| Short | Resource that is related to this one | ||
| Definition | A reference to the observation or QuestionnaireResponse resource that is related to this observation. | ||
| Cardinality | 1..1 | ||
| Type | Reference(QuestionnaireResponse | Sequence | CareConnect-GPC-Observation-1) | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.component | |||
| Short | Component results | ||
| Definition | Some observations have multiple component observations. These component observations are expressed as separate code value pairs that share the same attributes. Examples include systolic and diastolic component observations for blood pressure measurement and multiple component observations for genetics observations. | ||
| Cardinality | 0..* | ||
| Type | BackboneElement | ||
| Must Support | True | ||
| Summary | True | ||
| Requirements | Component observations share the same attributes in the Observation resource as the primary observation and are always treated a part of a single observation (they are not separable). However, the reference range for the primary observation value is not inherited by the component values and is required when appropriate for each component observation. | ||
| Comments | For a discussion on the ways Observations can be assembled in groups together see Notes below. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.component.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| 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 | string | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.component.extension | |||
| Short | Additional Content defined by implementations | ||
| 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. | ||
| 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) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.component.modifierExtension | |||
| Short | Extensions that cannot be ignored | ||
| 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. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| Summary | True | ||
| Alias | 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.component.code | |||
| Short | Type of component observation (code / type) | ||
| Definition | Describes what was observed. Sometimes this is called the observation "code". | ||
| Cardinality | 1..1 | ||
| Type | CodeableConcept | ||
| Binding | Codes identifying names of simple observations. | ||
| Summary | True | ||
| Requirements | Knowing what kind of observation is being made is essential to understanding the observation. | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.component.code.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| 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 | string | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.component.code.extension | |||
| Short | Additional Content defined by implementations | ||
| 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. | ||
| 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) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.component.code.coding | |||
| Short | Code defined by a terminology system | ||
| Definition | A reference to a code defined by a terminology system. | ||
| Cardinality | 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. | ||
| Slicing | Unordered, Open, by system(Value) | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.component.code.coding:snomedCT | |||
| Short | Code defined by a terminology system | ||
| Definition | A reference to a code defined by a terminology system. | ||
| Cardinality | 0..1 | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.component.code.coding:snomedCT.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| 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 | string | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.component.code.coding:snomedCT.extension | |||
| Short | Additional Content defined by implementations | ||
| 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. | ||
| 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) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.component.code.coding:snomedCT.extension:snomedCTDescriptionID | |||
| Short | The SNOMED CT Description ID for the display | ||
| Definition | The SNOMED CT Description ID for the display. | ||
| Cardinality | 0..1 | ||
| Type | Extension(Complex) | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.component.code.coding:snomedCT.system | |||
| Short | Identity of the terminology system | ||
| Definition | The identification of the code system that defines the meaning of the symbol in the code. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Summary | True | ||
| Requirements | Need to be unambiguous about the source of the definition of the symbol. | ||
| Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | http://snomed.info/sct | ||
| Mappings |
| ||
| Observation.component.code.coding:snomedCT.version | |||
| Short | Version of the system - if relevant | ||
| Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. | ||
| Cardinality | 0..0 | ||
| Type | string | ||
| Summary | True | ||
| Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.component.code.coding:snomedCT.code | |||
| Short | Symbol in syntax defined by the system | ||
| Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). | ||
| Cardinality | 1..1 | ||
| Type | code | ||
| Summary | True | ||
| Requirements | Need to refer to a particular code in the system. | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.component.code.coding:snomedCT.display | |||
| Short | Representation defined by the system | ||
| Definition | A representation of the meaning of the code in the system, following the rules of the system. | ||
| Cardinality | 1..1 | ||
| Type | string | ||
| Summary | True | ||
| Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.component.code.coding:snomedCT.userSelected | |||
| Short | If this coding was chosen directly by the user | ||
| Definition | Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). | ||
| Cardinality | 0..1 | ||
| Type | boolean | ||
| Summary | True | ||
| Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. | ||
| Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.component.code.text | |||
| Short | Plain text representation of the concept | ||
| 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. | ||
| Cardinality | 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.component.value[x] | |||
| Short | Actual component result | ||
| Definition | The information determined as a result of making the observation, if the information has a simple value. | ||
| Cardinality | 0..1 | ||
| Type | Attachment | CodeableConcept | dateTime | Period | CareConnect-Quantity-1 | Range | Ratio | SampledData | string | time | ||
| Summary | True | ||
| Requirements | An observation exists to have a value, though it may not if it is in error, or if it represents a group of observations. | ||
| Comments | Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the Observation.code defines a coded value. For boolean values use valueCodeableConcept and select codes from http://hl7.org/fhir/ValueSet/v2-0136 (these "yes/no" concepts can be mapped to the display name "true/false" or other mutually exclusive terms that may be needed"). The element, Observation.value[x], has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueRatio, valueChoice, valuePeriod, valueSampleData, or valueString (the name format is "'value' + the type name" with a capital on the first letter of the type). | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.component.dataAbsentReason | |||
| Short | Why the component result is missing | ||
| Definition | Provides a reason why the expected value in the element Observation.value[x] is missing. | ||
| Cardinality | 0..1 | ||
| Type | CodeableConcept | ||
| Binding | Codes specifying why the result (Observation.value[x]) is missing. | ||
| Must Support | True | ||
| Requirements | For many results it is necessary to handle exceptional values in measurements. | ||
| Comments | "Null" or exceptional values can be represented two ways in FHIR Observations. One way is to simply include them in the value set and represent the exceptions in the value. For example, measurement values for a serology test could be "detected", "not detected", "inconclusive", or "test not done". The alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values. For example, the dataAbsentReason code "error" could be used when the measurement was not completed. Because of these options, use-case agreements are required to interpret general observations for exceptional values. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, obs-6 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.component.interpretation | |||
| Short | High, low, normal, etc. | ||
| Definition | The assessment made based on the result of the observation. Intended as a simple compact code often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Otherwise known as abnormal flag. | ||
| Cardinality | 0..1 | ||
| Type | CodeableConcept | ||
| Binding | Codes identifying interpretations of observations. | ||
| Alias | Abnormal Flag | ||
| Requirements | For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. | ||
| Comments | The component interpretation applies only to the individual component value. For an overall interpretation all components together use thes Observation.interpretation element. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Observation.component.referenceRange | |||
| Short | Provides guide for interpretation of component result | ||
| Definition | Guidance on how to interpret the value by comparison to a normal or recommended range. | ||
| Cardinality | 0..* | ||
| Type | see (referenceRange) | ||
| Requirements | Knowing what values are considered "normal" can help evaluate the significance of a particular result. Need to be able to provide multiple reference ranges for different contexts. | ||
| Comments | Most observations only have one generic reference range. Systems MAY choose to restrict to only supplying the relevant reference range based on knowledge about the patient (e.g., specific to the patient's age, gender, weight and other factors), but this may not be possible or appropriate. Whenever more than one reference range is supplied, the differences between them SHOULD be provided in the reference range and/or age properties. | ||
| Mappings |
| ||
Background
The Observation profile is used for carry data for a number of concepts. They include:
- Uncategorised data / general observations e.g. BMI, weight, height, smoking status, Special Patient Notes, etc.
- Blood pressure readings
- Test result group headers
- Individual test results
- Test result filing comments
Where applicable, any differences in how the element is used and populated is highlighted in the guidance below.
Data model element usage
| Element | Use | CareConnect (STU3) | UK Core (R4) | NHS Digital (R4) |
|---|---|---|---|---|
| id | ||||
| meta.versionId | ||||
| meta.lastUpdated | ||||
| meta.profile | ||||
| meta.security | ||||
| meta.tag | ||||
| extension(reason) | ||||
| identifier | ||||
| basedOn | ||||
| status | ||||
| category | ||||
| code | ||||
| subject | ||||
| context | ||||
| effectiveDateTime | ||||
| issued | ||||
| performer | ||||
| dataAbsentReason | ||||
| interpretation | ||||
| comment | ||||
| bodySite | ||||
| method | ||||
| device | ||||
| referenceRange | ||||
| related | ||||
| component |
id
Usage
Optional
Guidance
The id is the logical identifier for the CareConnect-GPC-Observation-1 profile.
Example
<id value="bfa6215a-e433-4729-9e41-510730df6423" />
meta.versionId
Usage
Optional
Guidance
The population of the meta.versionId element could be useful if sending an adendum of something previously sent to help the consumer (receiver) in understanding there is a "newer" version.
Example
<meta> <versionId value="1" /> </meta>
meta.lastUpdated
Usage
Optional
Guidance
The meta.lastUpdated element could be useful alongside the meta.versionIdelement could be useful if sending an adendum of something previously sent to help the consumer (receiver) in understanding there is a "newer" version.
Example
<meta> <lastUpdated value="2022-10-28T08:06:00+00:00" /> </meta>
meta.profile
Usage
Mandatory
Guidance
The meta.profile contains a fixed value of the URL for the CareConnect-GPC-Observation-1 profile.
Example
<meta> <profile value="https://fhir.nhs.uk/STU3/StructureDefinition/CareConnect-GPC-Observation-1" /> </meta>
meta.security
Usage
Optional
Guidance
The security label(s) applicable to the resource.
See Resources not to be disclosed to a patient for more details on how to populate the element.
Example
<meta> <security> <system value="http://hl7.org/fhir/v3/ActCode"/> <code value="NOPAT"/> <display value="no disclosure to patient, family or caregivers without attending provider's authorization"/> </security> </meta>
meta.tag
Usage
Optional
Guidance
A use-case for the meta.tag element within GP Connect has not been defined.
Example
<meta> <tag> <coding> <system value="http://hl7.org/fhir/common-tags" /> <code value="actionable" /> <display value="Actionable" /> </coding> </tag> </meta>
extension(reason)
Usage
Required
Guidance
A reference to the Condition the Observation relates to - if relevant.
Example
<extension> <url value="https://fhir.nhs.uk/STU3/StructureDefinition/Extension-CareConnect-GPC-ReasonCondition-1" /> <valueReference value="condition-77492" /> </extension>
identifier
Usage
Mandatory
Guidance
The identifier element MUST be populated with a globally unique and persistent identifier (that is, it doesn’t change between requests and therefore stored with the source data). This MUST be scoped by a provider specific namespace for the identifier.
Where consuming systems are integrating data from this resource to their local system, they MUST also persist this identifier at the same time.
Example
<identifier> <system value="https://foo.bar/id/observation" /> <value value="782bdd5a-9c18-4454-aea8-0a23f8355873" /> </identifier>
basedOn
Usage
Optional
Guidance
A use-case for the basedOn element within GP Connect has not been defined.
Example
<basedOn> <reference value="careplan-3493821" /> </basedOn>
status
Usage
Mandatory
Guidance
Test Group Header
The status of the test group header.
In GP systems, these are most likely to be final. However, preliminary reports are possible as, for example, some work can be sub-contracted to other labs. If the system is not able to determine the status of a test group header then it should default to the unknown value.
Individual Test Result
The status of the test result.
In GP systems, these are most likely to be final. However, preliminary reports are possible as, for example, some work can be sub-contracted to other labs. If the system is not able to determine the status of a test group header then it should default to the unknown value.
Filing Comments
For filing comments this is a set value of unknown.
Observations including Blood Pressure
Fixed value of final.
The code system for this status can be found using the link below:
http://hl7.org/fhir/observation-status
Example
<status value="final" />
category
Usage
Optional
Guidance
Individual Test Result
The general type of test result. A default value of Laboratory should be used if a more specific value is not available - for example, pathology, microbiology, and so on.
Other use cases
This element is not used.
Example
<category> <coding> <system value="http://terminology.hl7.org/CodeSystem/observation-category" /> <code value="vital-signs" /> <display value="Vital Signs" /> </coding> </category>
code
Usage
Mandatory
Guidance
Test Group Header
The clinical code that represents the name of the test group - for example, Full blood count.
Individual Test Result
The clinical code that represents the name of the test result or test analyte.
Filing Comments
Fixed value of 37331000000100 for Comment note.
Observations
The clinical code that represents the data within the observation.
For free text without any clinical code set to 37331000000100 Comment note.
Blood Pressure
The clinical code that represents the header or panel of the blood pressure.
Where there is an appropriate header code for a recognised triple recorded in the providing GP system this MUST be populated here.
If there is no header/panel code and only the code(s) for systolic and/or diastolic components are recorded, then this MUST be populated with the SNOMED codes conceptID ‘75367002’ and the descriptionID of the preferred term ‘125176019’ which has the description ‘Blood pressure’ and is an observable entity.
Example
<code> <coding> <system value="http://snomed.info/sct" /> <code value="37331000000100" /> <display value="Comment note (record artifact)" /> </coding> </code>
subject
Usage
Mandatory
Guidance
A reference to the patient for whom the observation is for.
Profile: CareConnect-GPC-Patient-1
Example
<subject> <reference value="patient-3999890" /> </subject>
context
Usage
Required
Guidance
A reference to the CareConnect-GPC-Encounter-1 profile, representing the consultation context in which the uncategorised data was recorded.
Profile: CareConnect-GPC-Encounter-1
Example
<context> <reference value="encounter-1230fdf" /> </context>
effective[x]
Usage
Required
Guidance
Test Group Header
The date and time when the test was performed.
Individual Test Result
The date and time when the test was performed.
Filing Comments
The dateTime when the ‘Test report’, ‘Test group’ or ‘Test result’ was filed into the patient record.
Observations including Blood Pressure
The date / time the observation took place - or the clinically relevant date / time for the observation.
Example
<effectiveDateTime value="2022-10-24T09:03:00Z" />
issued
Usage
Mandatory
Guidance
Test Group Header
The date and time that the result was issued by the laboratory or other report provider.
Is this is not provided for a test group header result then it should inherit the date from the DiagnosticReport.
Individual Test Result
The date and time that the result was issued by the laboratory or other report provider.
Is this is not provided for a test group header result then it should inherit the date from the DiagnosticReport.
Filing Comments
The date time that the time/comment was recorded in the GP system.
Observations including Blood Pressure
The audit trail timestamp representing when the data was recorded.
Example
<issued value="2022-10-24T109:05:00Z" />
performer
Usage
Required
Guidance
A reference to a CareConnect-GPC-Practitioner-1 profile, representting the clinician responsible for making the observation.
Where the observation was performed at another organisation, then a reference to a CareConnect-GPC-Organization MUST be populated in the performer element. This will be in addition to the clinical practitioner, if both are available.
If neither the performing organisation, or the clinical practitioner are known, then this MUST be populated with the details of the person who recorded the data in the system.
Example
<context> <reference value="practitioner-9090arke3" /> <reference value="organization-0012sa2k" /> </context>
value[x]
Usage
Required
Guidance
Test Group Header
N/A
Individual Test Result
The value of the test. This may be in the form of, but is not limited to, one of the following datatypes: a quantity, string or an attachment.
Filing Comments
Where a ‘Test group’ or ‘Test result’ has been filed the value should match the code from the ‘Test group header’ or ‘Test result’ resource respectively.
Observations
The value of the observation. This may be in any of the forms defined in the profile.
Where applicable the value MUST use the units specified as part of the FHIR vital signs specification.
Blood Pressure
N/A
Example
<valueQuantity> <value value="16" /> <unit value="breaths per minute" /> <system value="http://unitsofmeasure.org" /> <code value="{resps}/min" /> </valueQuantity>
dataAbsentReason
Usage
Required
Guidance
Individual Test Result
Provides a reason why the expected value in the element Observation.value[x] is missing.
Example
<dataAbsentReason> <system value="http://hl7.org/fhir/ValueSet/observation-valueabsentreason" /> <code value="unsupported" /> <display value="Unsupported" /> </dataAbsentReason>
interpretation
Usage
Required
Guidance
Test Group Header
A human-readable clinical summary relating to a test result and/or additional notes provided by the laboratory - for example, the specimen has haemolysed or has leaked.
Individual Test Result
A human-readable clinical summary relating to a test result and/or additional notes provided by the laboratory - for example, the specimen has haemolysed or has leaked.
Filing Comments
N/A
Observations including Blood Pressure
A human-readable clinical summary relating to a test result and/or additional notes provided by the laboratory - for example, the specimen has haemolysed or has leaked.
Codes identifying interpretations of observations.
CareConnect Observation Interpretation
Example
<interpretation> <system value="http://terminology.hl7.org/CodeSystem/v2-0078" /> <code value="DET" /> <display value="Detected" /> </interpretation>
comment
Usage
Required
Guidance
Test Group Header
Notes that relate to the test group header that were written by the performing organization.
For example, the sample has haemolysed or has leaked.
Individual Test Result
Lab notes in addition to the interpretation. For example, the sample has haemolysed or has leaked.
Filing Comments
Notes added by the GP practice clinician about the ‘Test report’, ‘Test group’ or ‘Test result’ that has been filed into the patient record.
Observations including Blood Pressure
This MUST include any qualifiers to the code element that were present in the sending system. These should be reported as a code and value pair.
It MUST also include any text relating to the observation.
Example
<comment value="Pellentesque vestibulum, quam vel mattis tempus, metus lorem finibus lectus, non tempor diam massa non purus.">
bodySite
Usage
Required
Guidance
Test Group Header
N/A
Individual Test Result
The body part that was tested/observed.
Filing Comments
N/A
Observations including Blood Pressure
This MAY be populated where a suitably coded body site is captured with an appropriate terminology. Alternatively, the comment can be populated as described above.
Example
<bodySite> <coding> <system value="http://snomed.info/sct" /> <code value="10547007" /> <display value="Otic route (qualifier value)" /> </coding> </bodySite>
method
Usage
Required
Guidance
Individual Test Result
Indicates the mechanism used to perform the observation.
Example
<method> <coding> <system value="http://snomed.info/sct" /> <code value="754181000000108" /> <display value="Assessment for syringing of ear (procedure)" /> </coding> </method>
specimen
Usage
Required
Guidance
Test Group Header & Individual Test Result
A reference to the specimen that was used when this observation was made, using the CareConnect-GPC-Specimen-1 FHIR profile.
Example
<context> <reference value="specimen-dd0021" /> </context>
device
Usage
Required
Guidance
A reference to the device that was used when this observation was made, using the GPConnect-Device-1 or the DeviceMetric FHIR profile.
Example
<device> <reference value="device-ph4s21" /> </device>
referenceRange
Usage
Required
Guidance
The reference range provides a guide for interpretation of the results.
<) or greater than (>) operators, then it should be written to the referenceRange.text element as these operators are not supported in this context.
Value Set: referencerange-meaning
Value Set: referencerange-appliesto
Example
<referenceRange> <low> <value value="133" /> <unit value="millimole per liter" /> <system value="http://unitsofmeasure.org" /> <code value="mmol/L" /> </low> <high> <value value="146" /> <unit value="millimole per liter" /> <system value="http://unitsofmeasure.org" /> <code value="mmol/L" /> </high> <type> <coding> <code value="normal" /> <system value="http://hl7.org/fhir/ValueSet/referencerange-meaning" /> <display value="Normal Range" /> </coding> </type> <appliesTo> <code value="1747-5" /> <system value="http://hl7.org/fhir/ValueSet/referencerange-appliesto" /> <display value="Beaver" /> </appliesTo> </referenceRange>
Example - low and high with value and unit
<referenceRange> <low> <value value="2" /> <unit value="micromole per liter" /> </low> <high> <value value="5" /> <unit value="micromole per liter" /> </high> </referenceRange>
Example - high only, with value and unit
<referenceRange> <high> <value value="5" /> <code value="U/L" /> </high> </referenceRange>
Example - text only
<referenceRange> <text> <value value="< 200.000 mg/L" /> </text> </referenceRange>
component
Usage
Required
Guidance
Observations
This MAY be used for the component part of a blood pressure that is recorded as a triple or to carry qualifying data to the main observation code.
This MAY be used for inbound referrals.
Blood Pressure
Systolic component
component.code - The clinical code that represents systolic part of the blood pressure.
component.valueQuantity - The value of the observation. This MUST be a ‘quantity’ data type and the units used MUST be ‘mm[Hg]’.
component.dateAbsentReason - If there is no code or value in this component, then a data absent reason may be populated.
component.interpretation - A human-readable clinical summary relating to a test result and/or additional notes provided by the laboratory - for example, the specimen has haemolysed or has leaked.
component.referenceRange - The reference range provides a guide for interpretation of the results.
Where a reference range contains a less than < or greater than > operator it should be written to the referenceRange.text element as these operators are not supported in this context.
Diastolic component
component.code - The clinical code that represents systolic part of the blood pressure.
component.valueQuantity - The value of the observation. This MUST be a ‘quantity’ data type and the units used MUST be ‘mm[Hg]’.
component.dateAbsentReason - If there is no code or value in this component, then a data absent reason may be populated.
component.interpretation - A human-readable clinical summary relating to a test result and/or additional notes provided by the laboratory - for example, the specimen has haemolysed or has leaked.
component.referenceRange - The reference range provides a guide for interpretation of the results.
Where a reference range contains a less than < or greater than > operator it should be written to the referenceRange.text element as these operators are not supported in this context.
Example
<component> <code> <coding> <system value="http://snomed.info/sct" /> <code value="1091811000000102" /> <display value="Diastolic arterial pressure (observable entity)" /> </coding> </code> <referenceRange> <low> <code value="mm[Hg]" /> <system value="http://unitsofmeasure.org" /> <unit value="millimeter of mercury" /> <value value="60" /> </low> <high> <code value="mm[Hg]" /> <system value="http://unitsofmeasure.org" /> <unit value="millimeter of mercury" /> <value value="80" /> </high> <type> <coding> <code value="normal" /> <system value="http://hl7.org/fhir/ValueSet/referencerange-meaning" /> <display value="Normal Range" /> </coding> </type> </referenceRange> <valueQuantity> <code value="mm[Hg]" /> <system value="http://unitsofmeasure.org" /> <unit value="millimeter of mercury" /> <value value="92" /> </valueQuantity> <interpretation> <system value="http://terminology.hl7.org/CodeSystem/v2-0078" /> <code value="H" /> <display value="High" /> </interpretation> </component>