Glioblastoma (GBM)
Executive summary
This algorithm measures glioblastoma.
Resource Overview
Resource Name | FHIR Resource Type | Link to profile | Link to example |
---|---|---|---|
Service | HealthcareService | Link | Link |
Heartbeat | Observation | Link | Link |
Algorithm | Device | Link | Link |
Endpoint | Endpoint | Link | Link |
Input | Parameter | Link | Link |
Output | Parameter | Link | Link |
Links
- Website: https://ship-ai.ikim.nrw/
Description
Algorithm - FHIR Model
Profile
OmiDevice (Device) | C | Device | There are no (further) constraints on this element Element idDeviceShort description Item used in healthcare DefinitionA type of a manufactured item that is used in the provision of healthcare without being substantially changed through that activity. The device may be a medical or non-medical device.
| |||
id | Σ | 0..1 | string | There are no (further) constraints on this element Element idDevice.idShort description Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. | ||
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idDevice.metaShort description Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
| ||
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idDevice.implicitRulesShort description A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
| ||
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idDevice.languageShort description Language of the resource content DefinitionThe base language in which the resource is written. 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). A human language.
| |||
text | 0..1 | Narrative | There are no (further) constraints on this element Element idDevice.textShort description Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource and can 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. 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 information is added later.
| |||
contained | 0..* | Resource | There are no (further) constraints on this element Element idDevice.containedShort description Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese 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. 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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
| |||
extension | S C | 0..* | Extension | Element idDevice.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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. Unordered, Open, by url(Value) Constraints
| ||
buildHashExtension | S C | 0..1 | Extension(Complex) | Element idDevice.extension:buildHashExtensionShort description Build Hash Extension Alternate namesextensions, user content DefinitionExtension holding a hash value and some information about the hash type. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttp://omi.de/fhir/registry/StructureDefinition/build-hash-extension ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
inputParameters | S C | 0..1 | Extension(canonical()) | Element idDevice.extension:inputParametersShort description Service Input Parameter Extension Alternate namesextensions, user content DefinitionExtension to link input parameters to the HealthcareService resource. 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. http://omi.de/fhir/registry/StructureDefinition/input-parameter-extension ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
outputParameters | S C | 0..1 | Extension(canonical()) | Element idDevice.extension:outputParametersShort description Service Output Parameter Extension Alternate namesextensions, user content DefinitionExtension to link output parameters to the HealthcareService resource. 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. http://omi.de/fhir/registry/StructureDefinition/output-parameter-extension ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
doiExtension | S C | 0..* | Extension(Complex) | Element idDevice.extension:doiExtensionShort description DOI extension Alternate namesextensions, user content DefinitionHolds a Document Object Identifier (DOI) and a citation string of an algorithm. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttp://omi.de/fhir/registry/StructureDefinition/doi-extension ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
resolutionRequirementExtension | S C | 0..1 | Extension(Complex) | Element idDevice.extension:resolutionRequirementExtensionShort description MRT resolution requirement extension Alternate namesextensions, user content DefinitionDefines the minimum, recommended and max resolution for an algorithm. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttp://omi.de/fhir/registry/StructureDefinition/mrt-resolution-requirement-extension ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
algorithmSymbolExtension | S C | 0..1 | Extension(base64Binary) | Element idDevice.extension:algorithmSymbolExtensionShort description AlgorithmSymbolExtension Alternate namesextensions, user content DefinitionExtension to capture the PNG symbol of an algorithm. 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. http://omi.de/fhir/registry/StructureDefinition/AlgorithmSymbolExtension ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
deidentificationParameters | S C | 0..1 | Extension(Reference(OmiDeidentificationParameters)) | Element idDevice.extension:deidentificationParametersShort description Algorithm Deidentification Parameters Extension Alternate namesextensions, user content DefinitionDocuments the deidentification parameters for an algorithm. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Reference(OmiDeidentificationParameters)) Extension URLhttp://omi.de/fhir/registry/StructureDefinition/deidentification-extension ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
softwareLicenseExtension | S C | 0..1 | Extension(CodeableConcept) | Element idDevice.extension:softwareLicenseExtensionShort description Software License Extension Alternate namesextensions, user content DefinitionExtension holding software license information. 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. http://omi.de/fhir/registry/StructureDefinition/software-license-extension ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
modifierExtension | ?! C | 0..* | Extension | There are no (further) constraints on this element Element idDevice.modifierExtensionShort description Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay 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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
identifier | S | 0..* | IdentifierPattern | Element idDevice.identifierShort description Instance identifier DefinitionUnique instance identifiers assigned to a device by manufacturers other organizations or owners. The barcode string from a barcode present on a device label or package may identify the instance, include names given to the device in local usage, or may identify the type of device. If the identifier identifies the type of device, Device.type element should be used.
{ "system": "http://omi.de/fhir/registry/sid/device" }Mappings
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idDevice.identifier.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDevice.identifier.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
| ||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idDevice.identifier.useShort description usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known .
| ||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idDevice.identifier.typeShort description Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. 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. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible) Constraints
| ||
system | S Σ | 0..1 | uriPattern | There are no (further) constraints on this element Element idDevice.identifier.systemShort description The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. 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. Identifier.system is always case sensitive.
http://omi.de/fhir/registry/sid/deviceExamples General http://www.acme.com/identifiers/patientMappings
| ||
value | S Σ | 0..1 | string | There are no (further) constraints on this element Element idDevice.identifier.valueShort description The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. 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. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456Mappings
| ||
period | Σ | 0..1 | Period | There are no (further) constraints on this element Element idDevice.identifier.periodShort description Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use.
| ||
assigner | Σ | 0..1 | Reference(Organization) | There are no (further) constraints on this element Element idDevice.identifier.assignerShort description Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. 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.
| ||
definition | 0..1 | Reference(DeviceDefinition) | There are no (further) constraints on this element Element idDevice.definitionShort description The reference to the definition for the device DefinitionThe reference to the definition for the device.
| |||
udiCarrier | Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element idDevice.udiCarrierShort description Unique Device Identifier (UDI) Barcode string DefinitionUnique device identifier (UDI) assigned to device label or package. Note that the Device may include multiple udiCarriers as it either may include just the udiCarrier for the jurisdiction it is sold, or for multiple jurisdictions it could have been sold. UDI may identify an unique instance of a device, or it may only identify the type of the device. See UDI mappings for a complete mapping of UDI parts to Device.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idDevice.udiCarrier.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDevice.udiCarrier.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idDevice.udiCarrier.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
deviceIdentifier | Σ | 0..1 | string | There are no (further) constraints on this element Element idDevice.udiCarrier.deviceIdentifierShort description Mandatory fixed portion of UDI Alternate namesDI DefinitionThe device identifier (DI) is a mandatory, fixed portion of a UDI that identifies the labeler and the specific version or model of a device.
| ||
issuer | 0..1 | uri | There are no (further) constraints on this element Element idDevice.udiCarrier.issuerShort description UDI Issuing Organization Alternate namesBarcode System DefinitionOrganization that is charged with issuing UDIs for devices. For example, the US FDA issuers include :
| |||
jurisdiction | 0..1 | uri | There are no (further) constraints on this element Element idDevice.udiCarrier.jurisdictionShort description Regional UDI authority DefinitionThe identity of the authoritative source for UDI generation within a jurisdiction. All UDIs are globally unique within a single namespace with the appropriate repository uri as the system. For example, UDIs of devices managed in the U.S. by the FDA, the value is http://hl7.org/fhir/NamingSystem/fda-udi. Allows a recipient of a UDI to know which database will contain the UDI-associated metadata.
| |||
carrierAIDC | Σ | 0..1 | base64Binary | There are no (further) constraints on this element Element idDevice.udiCarrier.carrierAIDCShort description UDI Machine Readable Barcode String Alternate namesAutomatic Identification and Data Capture DefinitionThe full UDI carrier of the Automatic Identification and Data Capture (AIDC) technology representation of the barcode string as printed on the packaging of the device - e.g., a barcode or RFID. Because of limitations on character sets in XML and the need to round-trip JSON data through XML, AIDC Formats SHALL be base64 encoded. The AIDC form of UDIs should be scanned or otherwise used for the identification of the device whenever possible to minimize errors in records resulting from manual transcriptions. If separate barcodes for DI and PI are present, concatenate the string with DI first and in order of human readable expression on label.
| ||
carrierHRF | Σ | 0..1 | string | There are no (further) constraints on this element Element idDevice.udiCarrier.carrierHRFShort description UDI Human Readable Barcode String Alternate namesHuman Readable Form DefinitionThe full UDI carrier as the human readable form (HRF) representation of the barcode string as printed on the packaging of the device. If separate barcodes for DI and PI are present, concatenate the string with DI first and in order of human readable expression on label.
| ||
entryType | 0..1 | codeBinding | There are no (further) constraints on this element Element idDevice.udiCarrier.entryTypeShort description barcode | rfid | manual + DefinitionA coded entry to indicate how the data was entered. Supports a way to distinguish hand entered from machine read data. Codes to identify how UDI data was entered.
| |||
status | S Σ ?! | 1..1 | codeBinding | Element idDevice.statusShort description Is this algorithm still available DefinitionStatus of the Device availability. This element is labeled as a modifier because the status contains the codes inactive and entered-in-error that mark the device (record)as not currently valid. The availability status of the device.
| ||
statusReason | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idDevice.statusReasonShort description online | paused | standby | offline | not-ready | transduc-discon | hw-discon | off DefinitionReason for the dtatus of the Device availability. The availability status reason of the device. FHIRDeviceStatusReason (extensible) Constraints
| |||
distinctIdentifier | 0..1 | string | There are no (further) constraints on this element Element idDevice.distinctIdentifierShort description The distinct identification string Alternate namesDistinct Identification Code (DIC) DefinitionThe distinct identification string as required by regulation for a human cell, tissue, or cellular and tissue-based product. For example, this applies to devices in the United States regulated under Code of Federal Regulation 21CFR§1271.290(c).
| |||
manufacturer | 0..1 | string | There are no (further) constraints on this element Element idDevice.manufacturerShort description Name of device manufacturer DefinitionA name of the manufacturer.
| |||
manufactureDate | S | 0..1 | dateTime | There are no (further) constraints on this element Element idDevice.manufactureDateShort description Date when the device was made DefinitionThe date and time when the device was manufactured.
| ||
expirationDate | 0..1 | dateTime | There are no (further) constraints on this element Element idDevice.expirationDateShort description Date and time of expiry of this device (if applicable) DefinitionThe date and time beyond which this device is no longer valid or should not be used (if applicable).
| |||
lotNumber | 0..1 | string | There are no (further) constraints on this element Element idDevice.lotNumberShort description Lot number of manufacture DefinitionLot number assigned by the manufacturer.
| |||
serialNumber | 0..1 | string | There are no (further) constraints on this element Element idDevice.serialNumberShort description Serial number assigned by the manufacturer DefinitionThe serial number assigned by the organization when the device was manufactured. Alphanumeric Maximum 20.
| |||
deviceName | S | 2..* | BackboneElement | Element idDevice.deviceNameShort description The name of the device as given by the manufacturer DefinitionThis represents the manufacturer's name of the device as provided by the device, from a UDI label, or by a person describing the Device. This typically would be used when a person provides the name(s) or when the device represents one of the names available from DeviceDefinition. Unordered, Open, by type(Pattern) Constraints
| ||
(All Slices) | The requirements in this element apply to all slices | |||||
id | 0..1 | string | There are no (further) constraints on this element Element idDevice.deviceName.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDevice.deviceName.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idDevice.deviceName.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
name | 1..1 | string | There are no (further) constraints on this element Element idDevice.deviceName.nameShort description The name of the device Alternate namesΣ DefinitionThe name of the device.
| |||
type | 1..1 | codeBinding | There are no (further) constraints on this element Element idDevice.deviceName.typeShort description udi-label-name | user-friendly-name | patient-reported-name | manufacturer-name | model-name | other DefinitionThe type of deviceName. UDILabelName | UserFriendlyName | PatientReportedName | ManufactureDeviceName | ModelName. The type of name the device is referred by.
| |||
user-friendly-name | S | 1..1 | BackboneElement | There are no (further) constraints on this element Element idDevice.deviceName:user-friendly-nameShort description The name of the device as given by the manufacturer DefinitionThis represents the manufacturer's name of the device as provided by the device, from a UDI label, or by a person describing the Device. This typically would be used when a person provides the name(s) or when the device represents one of the names available from DeviceDefinition.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idDevice.deviceName:user-friendly-name.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDevice.deviceName:user-friendly-name.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idDevice.deviceName:user-friendly-name.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
name | 1..1 | string | There are no (further) constraints on this element Element idDevice.deviceName:user-friendly-name.nameShort description The name of the device Alternate namesΣ DefinitionThe name of the device.
| |||
type | 1..1 | codeBindingPattern | Element idDevice.deviceName:user-friendly-name.typeShort description udi-label-name | user-friendly-name | patient-reported-name | manufacturer-name | model-name | other DefinitionThe type of deviceName. UDILabelName | UserFriendlyName | PatientReportedName | ManufactureDeviceName | ModelName. The type of name the device is referred by.
user-friendly-nameMappings
| |||
model-name | S | 1..1 | BackboneElement | There are no (further) constraints on this element Element idDevice.deviceName:model-nameShort description The name of the device as given by the manufacturer DefinitionThis represents the manufacturer's name of the device as provided by the device, from a UDI label, or by a person describing the Device. This typically would be used when a person provides the name(s) or when the device represents one of the names available from DeviceDefinition.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idDevice.deviceName:model-name.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDevice.deviceName:model-name.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idDevice.deviceName:model-name.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
name | 1..1 | string | There are no (further) constraints on this element Element idDevice.deviceName:model-name.nameShort description The name of the device Alternate namesΣ DefinitionThe name of the device.
| |||
type | 1..1 | codeBindingPattern | Element idDevice.deviceName:model-name.typeShort description udi-label-name | user-friendly-name | patient-reported-name | manufacturer-name | model-name | other DefinitionThe type of deviceName. UDILabelName | UserFriendlyName | PatientReportedName | ManufactureDeviceName | ModelName. The type of name the device is referred by.
model-nameMappings
| |||
modelNumber | 0..1 | string | There are no (further) constraints on this element Element idDevice.modelNumberShort description The model number for the device DefinitionThe model number for the device.
| |||
partNumber | 0..1 | string | There are no (further) constraints on this element Element idDevice.partNumberShort description The part number of the device DefinitionThe part number of the device. Alphanumeric Maximum 20.
| |||
type | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idDevice.typeShort description The kind or type of device DefinitionThe kind or type of device. Codes to identify medical devices.
| |||
specialization | 0..* | BackboneElement | There are no (further) constraints on this element Element idDevice.specializationShort description The capabilities supported on a device, the standards to which the device conforms for a particular purpose, and used for the communication DefinitionThe capabilities supported on a device, the standards to which the device conforms for a particular purpose, and used for the communication.
| |||
id | 0..1 | string | There are no (further) constraints on this element Element idDevice.specialization.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDevice.specialization.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idDevice.specialization.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
systemType | 1..1 | CodeableConcept | There are no (further) constraints on this element Element idDevice.specialization.systemTypeShort description The standard that is used to operate and communicate Alternate namesΣ DefinitionThe standard that is used to operate and communicate.
| |||
version | 0..1 | string | There are no (further) constraints on this element Element idDevice.specialization.versionShort description The version of the standard that is used to operate and communicate DefinitionThe version of the standard that is used to operate and communicate.
| |||
version | 0..* | BackboneElement | There are no (further) constraints on this element Element idDevice.versionShort description The actual design of the device or software version running on the device DefinitionThe actual design of the device or software version running on the device.
| |||
id | 0..1 | string | There are no (further) constraints on this element Element idDevice.version.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDevice.version.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idDevice.version.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
type | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idDevice.version.typeShort description The type of the device version Alternate namesΣ DefinitionThe type of the device version.
| |||
component | 0..1 | Identifier | There are no (further) constraints on this element Element idDevice.version.componentShort description A single component of the device version DefinitionA single component of the device version.
| |||
value | 1..1 | string | There are no (further) constraints on this element Element idDevice.version.valueShort description The version text DefinitionThe version text.
| |||
property | S | 0..* | BackboneElement | Element idDevice.propertyShort description The actual configuration settings of a device as it actually operates, e.g., regulation status, time properties DefinitionThe actual configuration settings of a device as it actually operates, e.g., regulation status, time properties. Unordered, Open, by type(Pattern) Constraints
| ||
(All Slices) | The requirements in this element apply to all slices | |||||
id | 0..1 | string | There are no (further) constraints on this element Element idDevice.property.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDevice.property.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idDevice.property.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
type | S | 1..1 | CodeableConcept | There are no (further) constraints on this element Element idDevice.property.typeShort description Code that specifies the property DeviceDefinitionPropetyCode (Extensible) DefinitionCode that specifies the property DeviceDefinitionPropetyCode (Extensible).
| ||
valueQuantity | 0..* | Quantity | There are no (further) constraints on this element Element idDevice.property.valueQuantityShort description Property value as a quantity DefinitionProperty value as a quantity.
| |||
valueCode | S | 0..* | CodeableConcept | There are no (further) constraints on this element Element idDevice.property.valueCodeShort description Property value as a code, e.g., NTP4 (synced to NTP) DefinitionProperty value as a code, e.g., NTP4 (synced to NTP).
| ||
maturityLevel | S | 0..1 | BackboneElement | There are no (further) constraints on this element Element idDevice.property:maturityLevelShort description The actual configuration settings of a device as it actually operates, e.g., regulation status, time properties DefinitionThe actual configuration settings of a device as it actually operates, e.g., regulation status, time properties.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idDevice.property:maturityLevel.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDevice.property:maturityLevel.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idDevice.property:maturityLevel.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
type | S | 1..1 | CodeableConceptPattern | Element idDevice.property:maturityLevel.typeShort description Code that specifies the property DeviceDefinitionPropetyCode (Extensible) DefinitionCode that specifies the property DeviceDefinitionPropetyCode (Extensible).
{ "coding": [ { "system": "http://snomed.info/sct", "code": "246102003" } ] } | ||
valueQuantity | 0..* | Quantity | There are no (further) constraints on this element Element idDevice.property:maturityLevel.valueQuantityShort description Property value as a quantity DefinitionProperty value as a quantity.
| |||
valueCode | S | 1..* | CodeableConceptBinding | Element idDevice.property:maturityLevel.valueCodeShort description Property value as a code, e.g., NTP4 (synced to NTP) DefinitionProperty value as a code, e.g., NTP4 (synced to NTP).
| ||
supportedModality | S | 0..* | BackboneElement | There are no (further) constraints on this element Element idDevice.property:supportedModalityShort description The actual configuration settings of a device as it actually operates, e.g., regulation status, time properties DefinitionThe actual configuration settings of a device as it actually operates, e.g., regulation status, time properties.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idDevice.property:supportedModality.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDevice.property:supportedModality.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idDevice.property:supportedModality.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
type | S | 1..1 | CodeableConceptPattern | Element idDevice.property:supportedModality.typeShort description Code that specifies the property DeviceDefinitionPropetyCode (Extensible) DefinitionCode that specifies the property DeviceDefinitionPropetyCode (Extensible).
{ "coding": [ { "system": "http://snomed.info/sct", "code": "360037004" } ] } | ||
valueQuantity | 0..* | Quantity | There are no (further) constraints on this element Element idDevice.property:supportedModality.valueQuantityShort description Property value as a quantity DefinitionProperty value as a quantity.
| |||
valueCode | S | 1..* | CodeableConceptBinding | Element idDevice.property:supportedModality.valueCodeShort description Property value as a code, e.g., NTP4 (synced to NTP) DefinitionProperty value as a code, e.g., NTP4 (synced to NTP).
| ||
supportedLaterality | S | 0..* | BackboneElement | There are no (further) constraints on this element Element idDevice.property:supportedLateralityShort description The actual configuration settings of a device as it actually operates, e.g., regulation status, time properties DefinitionThe actual configuration settings of a device as it actually operates, e.g., regulation status, time properties.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idDevice.property:supportedLaterality.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDevice.property:supportedLaterality.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idDevice.property:supportedLaterality.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
type | S | 1..1 | CodeableConceptPattern | Element idDevice.property:supportedLaterality.typeShort description Code that specifies the property DeviceDefinitionPropetyCode (Extensible) DefinitionCode that specifies the property DeviceDefinitionPropetyCode (Extensible).
{ "coding": [ { "system": "http://snomed.info/sct", "code": "272741003" } ] } | ||
valueQuantity | 0..* | Quantity | There are no (further) constraints on this element Element idDevice.property:supportedLaterality.valueQuantityShort description Property value as a quantity DefinitionProperty value as a quantity.
| |||
valueCode | S | 1..* | CodeableConceptBinding | Element idDevice.property:supportedLaterality.valueCodeShort description Property value as a code, e.g., NTP4 (synced to NTP) DefinitionProperty value as a code, e.g., NTP4 (synced to NTP). https://dicom.nema.org/medical/dicom/current/output/chtml/part16/sect_CID_244.html (required) Constraints
| ||
imageReconstructionPlane | S | 0..* | BackboneElement | There are no (further) constraints on this element Element idDevice.property:imageReconstructionPlaneShort description The actual configuration settings of a device as it actually operates, e.g., regulation status, time properties DefinitionThe actual configuration settings of a device as it actually operates, e.g., regulation status, time properties.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idDevice.property:imageReconstructionPlane.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDevice.property:imageReconstructionPlane.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idDevice.property:imageReconstructionPlane.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
type | S | 1..1 | CodeableConceptPattern | Element idDevice.property:imageReconstructionPlane.typeShort description Code that specifies the property DeviceDefinitionPropetyCode (Extensible) DefinitionCode that specifies the property DeviceDefinitionPropetyCode (Extensible).
{ "coding": [ { "system": "http://snomed.info/sct", "code": "260225008" } ] } | ||
valueQuantity | 0..* | Quantity | There are no (further) constraints on this element Element idDevice.property:imageReconstructionPlane.valueQuantityShort description Property value as a quantity DefinitionProperty value as a quantity.
| |||
valueCode | S | 1..* | CodeableConceptBinding | Element idDevice.property:imageReconstructionPlane.valueCodeShort description Property value as a code, e.g., NTP4 (synced to NTP) DefinitionProperty value as a code, e.g., NTP4 (synced to NTP). CrosssectionalScanPlaneOrientation (required) Constraints
| ||
supportedBodySite | S | 0..* | BackboneElement | There are no (further) constraints on this element Element idDevice.property:supportedBodySiteShort description The actual configuration settings of a device as it actually operates, e.g., regulation status, time properties DefinitionThe actual configuration settings of a device as it actually operates, e.g., regulation status, time properties.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idDevice.property:supportedBodySite.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDevice.property:supportedBodySite.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idDevice.property:supportedBodySite.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
type | S | 1..1 | CodeableConceptPattern | Element idDevice.property:supportedBodySite.typeShort description Code that specifies the property DeviceDefinitionPropetyCode (Extensible) DefinitionCode that specifies the property DeviceDefinitionPropetyCode (Extensible).
{ "coding": [ { "system": "http://snomed.info/sct", "code": "123037004" } ] } | ||
valueQuantity | 0..* | Quantity | There are no (further) constraints on this element Element idDevice.property:supportedBodySite.valueQuantityShort description Property value as a quantity DefinitionProperty value as a quantity.
| |||
valueCode | S | 1..* | CodeableConceptBinding | Element idDevice.property:supportedBodySite.valueCodeShort description Property value as a code, e.g., NTP4 (synced to NTP) DefinitionProperty value as a code, e.g., NTP4 (synced to NTP). SNOMEDCTBodyStructures (required) Constraints
| ||
AIServiceType | S | 0..* | BackboneElement | There are no (further) constraints on this element Element idDevice.property:AIServiceTypeShort description The actual configuration settings of a device as it actually operates, e.g., regulation status, time properties DefinitionThe actual configuration settings of a device as it actually operates, e.g., regulation status, time properties.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idDevice.property:AIServiceType.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDevice.property:AIServiceType.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idDevice.property:AIServiceType.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
type | S | 1..1 | CodeableConceptPattern | Element idDevice.property:AIServiceType.typeShort description Code that specifies the property DeviceDefinitionPropetyCode (Extensible) DefinitionCode that specifies the property DeviceDefinitionPropetyCode (Extensible).
{ "coding": [ { "system": "http://snomed.info/sct", "code": "410656007" } ] } | ||
valueQuantity | 0..* | Quantity | There are no (further) constraints on this element Element idDevice.property:AIServiceType.valueQuantityShort description Property value as a quantity DefinitionProperty value as a quantity.
| |||
valueCode | S | 1..* | CodeableConceptBinding | Element idDevice.property:AIServiceType.valueCodeShort description Property value as a code, e.g., NTP4 (synced to NTP) DefinitionProperty value as a code, e.g., NTP4 (synced to NTP).
| ||
patient | 0..1 | Reference(Patient) | There are no (further) constraints on this element Element idDevice.patientShort description Patient to whom Device is affixed DefinitionPatient information, If the device is affixed to a person. If the device is implanted in a patient, then need to associate the device to the patient.
| |||
owner | S | 0..1 | Reference(OmiOrganization) | Element idDevice.ownerShort description Organization responsible for device DefinitionAn organization that is responsible for the provision and ongoing maintenance of the device.
| ||
contact | S | 0..1 | ContactPoint | There are no (further) constraints on this element Element idDevice.contactShort description Details for human/organization for support DefinitionContact details for an organization or a particular human that is responsible for the device. used for troubleshooting etc.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idDevice.contact.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDevice.contact.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
| ||
system | S Σ C | 0..1 | codeBindingPattern | Element idDevice.contact.systemShort description phone | fax | email | pager | url | sms | other DefinitionTelecommunications form for contact point - what communications system is required to make use of the contact. Telecommunications form for contact point. The cardinality or value of this element may be affected by these constraints: cpt-2 Constraints
| ||
value | S Σ | 1..1 | string | There are no (further) constraints on this element Element idDevice.contact.valueShort description The actual contact point details DefinitionThe actual contact point details, in a form that is meaningful to the designated communication system (i.e. phone number or email address). Need to support legacy numbers that are not in a tightly controlled format. Additional text data such as phone extension numbers, or notes about use of the contact are sometimes included in the value.
| ||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idDevice.contact.useShort description home | work | temp | old | mobile - purpose of this contact point DefinitionIdentifies the purpose for the contact point. Need to track the way a person uses this contact, so a user can choose which is appropriate for their purpose. Applications can assume that a contact is current unless it explicitly says that it is temporary or old. Use of contact point.
| ||
rank | Σ | 0..1 | positiveInt | There are no (further) constraints on this element Element idDevice.contact.rankShort description Specify preferred order of use (1 = highest) DefinitionSpecifies a preferred order in which to use a set of contacts. ContactPoints with lower rank values are more preferred than those with higher rank values. Note that rank does not necessarily follow the order in which the contacts are represented in the instance.
| ||
period | Σ | 0..1 | Period | There are no (further) constraints on this element Element idDevice.contact.periodShort description Time period when the contact point was/is in use DefinitionTime period when the contact point was/is in use.
| ||
location | 0..1 | Reference(Location) | There are no (further) constraints on this element Element idDevice.locationShort description Where the device is found DefinitionThe place where the device can be found. Device.location can be used to track device location.
| |||
url | 0..1 | uri | There are no (further) constraints on this element Element idDevice.urlShort description Network address to contact device DefinitionA network address on which the device may be contacted directly. If the device is running a FHIR server, the network address should be the Base URL from which a conformance statement may be retrieved.
| |||
note | S | 0..* | Annotation | There are no (further) constraints on this element Element idDevice.noteShort description Device notes and comments DefinitionDescriptive information, usage information or implantation information that is not captured in an existing element.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idDevice.note.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDevice.note.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
| ||
deviceNoteTypeExtension | S C | 0..1 | Extension(CodeableConcept) | Element idDevice.note.extension:deviceNoteTypeExtensionShort description DeviceNoteTypeExtension Alternate namesextensions, user content DefinitionExtension for the note field in the Device resource. 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. http://omi.de/fhir/registry/StructureDefinition/DeviceNoteTypeExtension ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
author[x] | Σ | 0..1 | There are no (further) constraints on this element Element idDevice.note.author[x]Short description Individual responsible for the annotation DefinitionThe individual responsible for making the annotation. Organization is used when there's no need for specific attribution as to who made the comment.
| |||
authorString | string | There are no (further) constraints on this element Data type | ||||
authorReference | Reference(Practitioner | Patient | RelatedPerson | Organization) | There are no (further) constraints on this element Data typeReference(Practitioner | Patient | RelatedPerson | Organization) | ||||
time | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idDevice.note.timeShort description When the annotation was made DefinitionIndicates when this particular annotation was made.
| ||
text | S Σ | 1..1 | markdown | There are no (further) constraints on this element Element idDevice.note.textShort description The annotation - text content (as markdown) DefinitionThe text of the annotation in markdown format.
| ||
safety | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element idDevice.safetyShort description Safety Characteristics of Device DefinitionProvides additional safety characteristics about a medical device. For example devices containing latex.
| ||
parent | 0..1 | Reference(Device) | There are no (further) constraints on this element Element idDevice.parentShort description The parent device DefinitionThe parent device.
|
Example
Device |
id : GbmAlgorithm |
meta |
profile : http://omi.de/fhir/registry/StructureDefinition/algorithm-device |
extension |
extension |
url : hash |
value : b7edda3172c39fe8754d607f2182047479b05d31406009cdcf1183970f5397a4 |
extension |
url : type |
value |
coding |
code : SHA-256 |
system : http://terminology.hl7.org/CodeSystem/v3-IntegrityCheckAlgorithm |
display : secure hash algorithm - 256 |
url : http://omi.de/fhir/registry/StructureDefinition/build-hash-extension |
extension |
url : http://omi.de/fhir/registry/StructureDefinition/deidentification-extension |
value |
reference : Parameters/GbmDeidentification |
extension |
url : http://omi.de/fhir/registry/StructureDefinition/input-parameter-extension |
value : http://omi.de/fhir/registry/StructureDefinition/GbmServiceInputParameters |
extension |
url : http://omi.de/fhir/registry/StructureDefinition/output-parameter-extension |
value : http://omi.de/fhir/registry/StructureDefinition/GbmServiceOutputParameters |
extension |
extension |
extension |
value |
value : 1 |
url : resolutionx |
extension |
value |
value : 1.25 |
url : resolutiony |
extension |
value |
value : 1.75 |
url : resolutionz |
extension |
url : qualifier |
value |
code : C25570 |
system : http://ncicb.nci.nih.gov/xml/owl/EVS/Thesaurus.owl |
display : Minimum |
url : minres |
url : http://omi.de/fhir/registry/StructureDefinition/mrt-resolution-requirement-extension |
identifier |
system : http://omi.de/fhir/registry/sid/device |
value : 3b6bed46-442d-4f28-bdf6-ab01ea005a59 |
version |
value : 0.1.0 (da9a697) |
deviceName |
type : user-friendly-name |
name : Glioblastoma |
deviceName |
type : model-name |
name : Glioblastoma |
property |
valueCode |
coding |
code : CT |
system : http://dicom.nema.org/resources/ontology/DCM |
display : Computed Tomography |
type |
coding |
code : 360037004 |
system : http://snomed.info/sct |
property |
valueCode |
coding |
code : diagnostics |
system : http://omi.de/fhir/registry/CodeSystem/ai-service-type-codesystem |
display : Diagnostics |
type |
coding |
code : 410656007 |
system : http://snomed.info/sct |
property |
valueCode |
coding |
code : LVL3 |
system : http://omi.de/fhir/registry/CodeSystem/maturity-level-codesystem |
display : LEVEL 3 |
type |
coding |
code : 246102003 |
system : http://snomed.info/sct |
status : active |
owner |
reference : Organization/ShipAI |
HealthcareService - FHIR Model
Profile
OmiHealthcareService (HealthcareService) | C | HealthcareService | There are no (further) constraints on this element Element idHealthcareServiceShort description The details of a healthcare service available at a location DefinitionThe details of a healthcare service available at a location.
| |||
id | Σ | 0..1 | string | There are no (further) constraints on this element Element idHealthcareService.idShort description Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. | ||
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idHealthcareService.metaShort description Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
| ||
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idHealthcareService.implicitRulesShort description A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
| ||
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idHealthcareService.languageShort description Language of the resource content DefinitionThe base language in which the resource is written. 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). A human language.
| |||
text | 0..1 | Narrative | There are no (further) constraints on this element Element idHealthcareService.textShort description Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource and can 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. 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 information is added later.
| |||
contained | 0..* | Resource | There are no (further) constraints on this element Element idHealthcareService.containedShort description Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese 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. 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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
| |||
extension | S C | 1..* | Extension | Element idHealthcareService.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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. Unordered, Open, by url(Value) Constraints
| ||
serviceToHeartBeatObservationLinkExtension | S C | 1..1 | Extension(Reference(HeartbeatObservationProfile)) | Element idHealthcareService.extension:serviceToHeartBeatObservationLinkExtensionShort description HealthcareService to Heartbeat Link Extension Alternate namesextensions, user content DefinitionLinks a service to heartbeat parameters. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Reference(HeartbeatObservationProfile)) Extension URLhttp://omi.de/fhir/registry/StructureDefinition/service-to-heart-beat-observation-link-extension ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
serviceToAlgorithmLinkExtension | S C | 0..* | Extension(Reference(OmiDevice)) | Element idHealthcareService.extension:serviceToAlgorithmLinkExtensionShort description Algorithm to Service Link Extension Alternate namesextensions, user content DefinitionLinks a service to a algorithm. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Reference(OmiDevice)) Extension URLhttp://omi.de/fhir/registry/StructureDefinition/service-to-algorithm-link-extension ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
softwareLicenseExtension | S C | 0..1 | Extension(CodeableConcept) | Element idHealthcareService.extension:softwareLicenseExtensionShort description Software License Extension Alternate namesextensions, user content DefinitionExtension holding software license information. 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. http://omi.de/fhir/registry/StructureDefinition/software-license-extension ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
modifierExtension | ?! C | 0..* | Extension | There are no (further) constraints on this element Element idHealthcareService.modifierExtensionShort description Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay 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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
identifier | S Σ | 0..* | IdentifierPattern | Element idHealthcareService.identifierShort description External identifiers for this item DefinitionExternal identifiers for this item.
{ "system": "http://omi.de/fhir/registry/sid/healthcare-service" }Mappings
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idHealthcareService.identifier.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idHealthcareService.identifier.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
| ||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idHealthcareService.identifier.useShort description usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known .
| ||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idHealthcareService.identifier.typeShort description Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. 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. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible) Constraints
| ||
system | S Σ | 0..1 | uriPattern | There are no (further) constraints on this element Element idHealthcareService.identifier.systemShort description The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. 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. Identifier.system is always case sensitive.
http://omi.de/fhir/registry/sid/healthcare-serviceExamples General http://www.acme.com/identifiers/patientMappings
| ||
value | S Σ | 0..1 | string | There are no (further) constraints on this element Element idHealthcareService.identifier.valueShort description The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. 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. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456Mappings
| ||
period | Σ | 0..1 | Period | There are no (further) constraints on this element Element idHealthcareService.identifier.periodShort description Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use.
| ||
assigner | Σ | 0..1 | Reference(Organization) | There are no (further) constraints on this element Element idHealthcareService.identifier.assignerShort description Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. 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.
| ||
active | S Σ ?! | 0..1 | boolean | There are no (further) constraints on this element Element idHealthcareService.activeShort description Whether this HealthcareService record is in active use DefinitionThis flag is used to mark the record to not be used. This is not used when a center is closed for maintenance, or for holidays, the notAvailable period is to be used for this. This element is labeled as a modifier because it may be used to mark that the resource was created in error. This resource is generally assumed to be active if no value is provided for the active element
| ||
providedBy | S Σ | 0..1 | Reference(OmiOrganization) | Element idHealthcareService.providedByShort description Organization that provides this service DefinitionThe organization that provides this healthcare service. This property is recommended to be the same as the Location's managingOrganization, and if not provided should be interpreted as such. If the Location does not have a managing Organization, then this property should be populated.
| ||
category | S Σ | 1..* | CodeableConceptPattern | Element idHealthcareService.categoryShort description Broad category of service being performed or delivered Alternate namesservice category DefinitionIdentifies the broad category of service being performed or delivered. Selecting a Service Category then determines the list of relevant service types that can be selected in the primary service type. A category of the service(s) that could be provided.
{ "coding": [ { "system": "http://ncicb.nci.nih.gov/xml/owl/EVS/Thesaurus.owl", "code": "C16309", "display": "Artificial Intelligence" } ] }Mappings
| ||
type | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element idHealthcareService.typeShort description Type of service that may be delivered or performed Alternate namesservice type DefinitionThe specific type of service that may be delivered or performed. Additional details about where the content was created (e.g. clinical specialty).
| ||
specialty | Σ | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idHealthcareService.specialtyShort description Specialties handled by the HealthcareService DefinitionCollection of specialties handled by the service site. This is more of a medical term. A specialty that a healthcare service may provide. PracticeSettingCodeValueSet (preferred) Constraints
| ||
location | Σ | 0..* | Reference(Location) | There are no (further) constraints on this element Element idHealthcareService.locationShort description Location(s) where service may be provided DefinitionThe location(s) where this healthcare service may be provided.
| ||
name | S Σ | 0..1 | string | There are no (further) constraints on this element Element idHealthcareService.nameShort description Description of service as presented to a consumer while searching DefinitionFurther description of the service as it would be presented to a consumer while searching.
| ||
comment | Σ | 0..1 | string | There are no (further) constraints on this element Element idHealthcareService.commentShort description Additional description and/or any specific issues not covered elsewhere DefinitionAny additional description of the service and/or any specific issues not covered by the other attributes, which can be displayed as further detail under the serviceName. Would expect that a user would not see this information on a search results, and it would only be available when viewing the complete details of the service.
| ||
extraDetails | 0..1 | markdown | There are no (further) constraints on this element Element idHealthcareService.extraDetailsShort description Extra details about the service that can't be placed in the other fields DefinitionExtra details about the service that can't be placed in the other fields.
| |||
photo | Σ | 0..1 | Attachment | There are no (further) constraints on this element Element idHealthcareService.photoShort description Facilitates quick identification of the service DefinitionIf there is a photo/symbol associated with this HealthcareService, it may be included here to facilitate quick identification of the service in a list.
| ||
telecom | 0..* | ContactPoint | There are no (further) constraints on this element Element idHealthcareService.telecomShort description Contacts related to the healthcare service DefinitionList of contacts related to this specific healthcare service. If this is empty, then refer to the location's contacts.
| |||
coverageArea | 0..* | Reference(Location) | There are no (further) constraints on this element Element idHealthcareService.coverageAreaShort description Location(s) service is intended for/available to DefinitionThe location(s) that this service is available to (not where the service is provided). The locations referenced by the coverage area can include both specific locations, including areas, and also conceptual domains too (mode = kind), such as a physical area (tri-state area) and some other attribute (covered by Example Care Organization). These types of Locations are often not managed by any specific organization. This could also include generic locations such as "in-home".
| |||
serviceProvisionCode | 0..* | CodeableConcept | There are no (further) constraints on this element Element idHealthcareService.serviceProvisionCodeShort description Conditions under which service is available/offered DefinitionThe code(s) that detail the conditions under which the healthcare service is available/offered. The provision means being commissioned by, contractually obliged or financially sourced. Types of costings that may apply to this healthcare service, such if the service may be available for free, some discounts available, or fees apply. The code(s) that detail the conditions under which the healthcare service is available/offered. ServiceProvisionConditions (example) Constraints
| |||
eligibility | 0..* | BackboneElement | There are no (further) constraints on this element Element idHealthcareService.eligibilityShort description Specific eligibility requirements required to use the service DefinitionDoes this service have specific eligibility requirements that need to be met in order to use the service?
| |||
id | 0..1 | string | There are no (further) constraints on this element Element idHealthcareService.eligibility.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idHealthcareService.eligibility.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idHealthcareService.eligibility.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idHealthcareService.eligibility.codeShort description Coded value for the eligibility DefinitionCoded value for the eligibility. Coded values underwhich a specific service is made available.
| |||
comment | 0..1 | markdown | There are no (further) constraints on this element Element idHealthcareService.eligibility.commentShort description Describes the eligibility conditions for the service DefinitionDescribes the eligibility conditions for the service. The description of service eligibility should, in general, not exceed one or two paragraphs. It should be sufficient for a prospective consumer to determine if they are likely to be eligible or not. Where eligibility requirements and conditions are complex, it may simply be noted that an eligibility assessment is required. Where eligibility is determined by an outside source, such as an Act of Parliament, this should be noted, preferably with a reference to a commonly available copy of the source document such as a web page.
| |||
program | 0..* | CodeableConcept | There are no (further) constraints on this element Element idHealthcareService.programShort description Programs that this service is applicable to DefinitionPrograms that this service is applicable to. Programs are often defined externally to an Organization, commonly by governments; e.g. Home and Community Care Programs, Homeless Program, …. Government or local programs that this service applies to.
| |||
characteristic | 0..* | CodeableConcept | There are no (further) constraints on this element Element idHealthcareService.characteristicShort description Collection of characteristics (attributes) DefinitionCollection of characteristics (attributes). These could be such things as is wheelchair accessible. A custom attribute that could be provided at a service (e.g. Wheelchair accessibiliy).
| |||
communication | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idHealthcareService.communicationShort description The language that this service is offered in DefinitionSome services are specifically made available in multiple languages, this property permits a directory to declare the languages this is offered in. Typically this is only provided where a service operates in communities with mixed languages used. When using this property it indicates that the service is available with this language, it is not derived from the practitioners, and not all are required to use this language, just that this language is available while scheduling. A human language.
| |||
referralMethod | 0..* | CodeableConcept | There are no (further) constraints on this element Element idHealthcareService.referralMethodShort description Ways that the service accepts referrals DefinitionWays that the service accepts referrals, if this is not provided then it is implied that no referral is required. The methods of referral can be used when referring to a specific HealthCareService resource.
| |||
appointmentRequired | 0..1 | boolean | There are no (further) constraints on this element Element idHealthcareService.appointmentRequiredShort description If an appointment is required for access to this service DefinitionIndicates whether or not a prospective consumer will require an appointment for a particular service at a site to be provided by the Organization. Indicates if an appointment is required for access to this service.
| |||
availableTime | 0..* | BackboneElement | There are no (further) constraints on this element Element idHealthcareService.availableTimeShort description Times the Service Site is available DefinitionA collection of times that the Service Site is available. More detailed availability information may be provided in associated Schedule/Slot resources.
| |||
id | 0..1 | string | There are no (further) constraints on this element Element idHealthcareService.availableTime.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idHealthcareService.availableTime.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idHealthcareService.availableTime.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
daysOfWeek | 0..* | codeBinding | There are no (further) constraints on this element Element idHealthcareService.availableTime.daysOfWeekShort description mon | tue | wed | thu | fri | sat | sun DefinitionIndicates which days of the week are available between the start and end Times. The days of the week.
| |||
allDay | 0..1 | boolean | There are no (further) constraints on this element Element idHealthcareService.availableTime.allDayShort description Always available? e.g. 24 hour service DefinitionIs this always available? (hence times are irrelevant) e.g. 24 hour service.
| |||
availableStartTime | 0..1 | time | There are no (further) constraints on this element Element idHealthcareService.availableTime.availableStartTimeShort description Opening time of day (ignored if allDay = true) DefinitionThe opening time of day. Note: If the AllDay flag is set, then this time is ignored. The time zone is expected to be for where this HealthcareService is provided at.
| |||
availableEndTime | 0..1 | time | There are no (further) constraints on this element Element idHealthcareService.availableTime.availableEndTimeShort description Closing time of day (ignored if allDay = true) DefinitionThe closing time of day. Note: If the AllDay flag is set, then this time is ignored. The time zone is expected to be for where this HealthcareService is provided at.
| |||
notAvailable | 0..* | BackboneElement | There are no (further) constraints on this element Element idHealthcareService.notAvailableShort description Not available during this time due to provided reason DefinitionThe HealthcareService is not available during this period of time due to the provided reason.
| |||
id | 0..1 | string | There are no (further) constraints on this element Element idHealthcareService.notAvailable.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idHealthcareService.notAvailable.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idHealthcareService.notAvailable.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
description | 1..1 | string | There are no (further) constraints on this element Element idHealthcareService.notAvailable.descriptionShort description Reason presented to the user explaining why time not available DefinitionThe reason that can be presented to the user as to why this time is not available.
| |||
during | 0..1 | Period | There are no (further) constraints on this element Element idHealthcareService.notAvailable.duringShort description Service not available from this date DefinitionService is not available (seasonally or for a public holiday) from this date.
| |||
availabilityExceptions | 0..1 | string | There are no (further) constraints on this element Element idHealthcareService.availabilityExceptionsShort description Description of availability exceptions DefinitionA description of site availability exceptions, e.g. public holiday availability. Succinctly describing all possible exceptions to normal site availability as details in the available Times and not available Times.
| |||
endpoint | S | 0..* | Reference(OmiAiEndpoint) | Element idHealthcareService.endpointShort description Technical endpoints providing access to electronic services operated for the healthcare service DefinitionTechnical endpoints providing access to services operated for the specific healthcare services defined at this resource.
|
Example
Device |
id : GbmAlgorithm |
meta |
profile : http://omi.de/fhir/registry/StructureDefinition/algorithm-device |
extension |
extension |
url : hash |
value : b7edda3172c39fe8754d607f2182047479b05d31406009cdcf1183970f5397a4 |
extension |
url : type |
value |
coding |
code : SHA-256 |
system : http://terminology.hl7.org/CodeSystem/v3-IntegrityCheckAlgorithm |
display : secure hash algorithm - 256 |
url : http://omi.de/fhir/registry/StructureDefinition/build-hash-extension |
extension |
url : http://omi.de/fhir/registry/StructureDefinition/deidentification-extension |
value |
reference : Parameters/GbmDeidentification |
extension |
url : http://omi.de/fhir/registry/StructureDefinition/input-parameter-extension |
value : http://omi.de/fhir/registry/StructureDefinition/GbmServiceInputParameters |
extension |
url : http://omi.de/fhir/registry/StructureDefinition/output-parameter-extension |
value : http://omi.de/fhir/registry/StructureDefinition/GbmServiceOutputParameters |
extension |
extension |
extension |
value |
value : 1 |
url : resolutionx |
extension |
value |
value : 1.25 |
url : resolutiony |
extension |
value |
value : 1.75 |
url : resolutionz |
extension |
url : qualifier |
value |
code : C25570 |
system : http://ncicb.nci.nih.gov/xml/owl/EVS/Thesaurus.owl |
display : Minimum |
url : minres |
url : http://omi.de/fhir/registry/StructureDefinition/mrt-resolution-requirement-extension |
identifier |
system : http://omi.de/fhir/registry/sid/device |
value : 3b6bed46-442d-4f28-bdf6-ab01ea005a59 |
version |
value : 0.1.0 (da9a697) |
deviceName |
type : user-friendly-name |
name : Glioblastoma |
deviceName |
type : model-name |
name : Glioblastoma |
property |
valueCode |
coding |
code : CT |
system : http://dicom.nema.org/resources/ontology/DCM |
display : Computed Tomography |
type |
coding |
code : 360037004 |
system : http://snomed.info/sct |
property |
valueCode |
coding |
code : diagnostics |
system : http://omi.de/fhir/registry/CodeSystem/ai-service-type-codesystem |
display : Diagnostics |
type |
coding |
code : 410656007 |
system : http://snomed.info/sct |
property |
valueCode |
coding |
code : LVL3 |
system : http://omi.de/fhir/registry/CodeSystem/maturity-level-codesystem |
display : LEVEL 3 |
type |
coding |
code : 246102003 |
system : http://snomed.info/sct |
status : active |
owner |
reference : Organization/ShipAI |
Heartbeat - FHIR Model
HeartbeatObservationProfile (Observation) | C | Observation | There are no (further) constraints on this element Element idObservationShort description Measurements and simple assertions Alternate namesVital Signs, Measurement, Results, Tests DefinitionMeasurements and simple assertions made about a patient, device or other subject. 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 laboratory reports, etc.
| |||
id | Σ | 0..1 | string | There are no (further) constraints on this element Element idObservation.idShort description Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. | ||
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idObservation.metaShort description Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
| ||
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idObservation.implicitRulesShort description A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
| ||
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idObservation.languageShort description Language of the resource content DefinitionThe base language in which the resource is written. 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). A human language.
| |||
text | 0..1 | Narrative | There are no (further) constraints on this element Element idObservation.textShort description Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource and can 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. 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 information is added later.
| |||
contained | 0..* | Resource | There are no (further) constraints on this element Element idObservation.containedShort description Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese 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. 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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
| |||
extension | C | 0..* | Extension | Element idObservation.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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. Unordered, Open, by url(Value) Constraints
| ||
buildHashExtension | S C | 0..1 | Extension(Complex) | Element idObservation.extension:buildHashExtensionShort description Build Hash Extension Alternate namesextensions, user content DefinitionExtension holding a hash value and some information about the hash type. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttp://omi.de/fhir/registry/StructureDefinition/build-hash-extension ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
modifierExtension | ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.modifierExtensionShort description Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay 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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
identifier | Σ | 0..* | Identifier | There are no (further) constraints on this element Element idObservation.identifierShort description Business Identifier for observation DefinitionA unique identifier assigned to this observation. Allows observations to be distinguished and referenced.
| ||
basedOn | Σ | 0..* | Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest) | There are no (further) constraints on this element Element idObservation.basedOnShort description Fulfills plan, proposal or order Alternate namesFulfills DefinitionA plan, proposal or order that is fulfilled in whole or in part by this event. For example, a MedicationRequest may require a patient to have laboratory test performed before it is dispensed. Allows tracing of authorization for the event and tracking whether proposals/recommendations were acted upon. Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest) Constraints
| ||
partOf | Σ | 0..* | Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy) | There are no (further) constraints on this element Element idObservation.partOfShort description Part of referenced event Alternate namesContainer DefinitionA larger event of which this particular Observation is a component or step. For example, an observation as part of a procedure. To link an Observation to an Encounter use Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy) Constraints
| ||
status | Σ ?! | 1..1 | codeBinding | There are no (further) constraints on this element Element idObservation.statusShort description registered | preliminary | final | amended + DefinitionThe status of the result value. Need to track the status of individual results. Some results are finalized before the whole report is finalized. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. Codes providing the status of an observation.
| ||
category | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.categoryShort description Classification of type of observation DefinitionA code that classifies the general type of observation being made. Used for filtering what observations are retrieved and displayed. 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. Codes for high level observation categories. ObservationCategoryCodes (preferred) Constraints
| |||
code | Σ | 1..1 | CodeableConceptPattern | Element idObservation.codeShort description Type of observation (code / type) Alternate namesName DefinitionDescribes what was observed. Sometimes this is called the observation "name". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and, if present, component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://ncicb.nci.nih.gov/xml/owl/EVS/Thesaurus.owl", "code": "C0449438", "display": "Status" } ] }Mappings
| ||
subject | Σ | 0..1 | Reference(Patient | Group | Device | Location) | There are no (further) constraints on this element Element idObservation.subjectShort description Who and/or what the observation is about DefinitionThe patient, or group of patients, location, or device this observation is about and into whose record the observation is placed. If the actual focus of the observation is different from the subject (or a sample of, part, or region of the subject), the Observations have no value if you don't know who or what they're about. 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. Reference(Patient | Group | Device | Location) Constraints
| ||
focus | Σ | 0..* | Reference(Resource) | There are no (further) constraints on this element Element idObservation.focusShort description What the observation is about, when it is not about the subject of record DefinitionThe actual focus of an observation when it is not the patient of record representing something or someone associated with the patient such as a spouse, parent, fetus, or donor. For example, fetus observations in a mother's record. The focus of an observation could also be an existing condition, an intervention, the subject's diet, another observation of the subject, or a body structure such as tumor or implanted device. An example use case would be using the Observation resource to capture whether the mother is trained to change her child's tracheostomy tube. In this example, the child is the patient of record and the mother is the focus. Typically, an observation is made about the subject - a patient, or group of patients, location, or device - and the distinction between the subject and what is directly measured for an observation is specified in the observation code itself ( e.g., "Blood Glucose") and does not need to be represented separately using this element. Use
| ||
encounter | Σ | 0..1 | Reference(Encounter) | There are no (further) constraints on this element Element idObservation.encounterShort description Healthcare event during which this observation is made Alternate namesContext DefinitionThe healthcare event (e.g. a patient and healthcare provider interaction) during which this observation is made. For some observations it may be important to know the link between an observation and a particular encounter. 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 but still be tied to the context of the encounter (e.g. pre-admission laboratory tests).
| ||
effective[x] | Σ | 0..1 | There are no (further) constraints on this element Element idObservation.effective[x]Short description Clinically relevant time/time-period for observation Alternate namesOccurrence DefinitionThe 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. Knowing when an observation was deemed true is important to its relevance as well as determining trends. At least a date should be present unless this observation is a historical report. For recording imprecise or "fuzzy" times (For example, a blood glucose measurement taken "after breakfast") use the Timing datatype which allow the measurement to be tied to regular life events.
| |||
effectiveDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
effectivePeriod | Period | There are no (further) constraints on this element Data type | ||||
effectiveTiming | Timing | There are no (further) constraints on this element Data type | ||||
effectiveInstant | instant | There are no (further) constraints on this element Data type | ||||
issued | Σ | 0..1 | instant | There are no (further) constraints on this element Element idObservation.issuedShort description Date/Time this version was made available DefinitionThe date and time this version of the observation was made available to providers, typically after the results have been reviewed and verified. For Observations that don’t require review and verification, it may be the same as the
| ||
performer | Σ | 0..* | Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson) | There are no (further) constraints on this element Element idObservation.performerShort description Who is responsible for the observation DefinitionWho was responsible for asserting the observed value as "true". May give a degree of confidence in the observation and also indicates where follow-up questions should be directed. Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson) Constraints
| ||
value[x] | Σ C | 0..1 | There are no (further) constraints on this element Element idObservation.value[x]Short description Actual result DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. An observation may have; 1) a single value here, 2) both a value and a set of related or component values, or 3) only a set of related or component values. 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 additional guidance, see the Notes section below. The cardinality or value of this element may be affected by these constraints: obs-7 Constraints
| |||
valueQuantity | Quantity | There are no (further) constraints on this element Data type | ||||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
valueString | string | There are no (further) constraints on this element Data type | ||||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||||
valueInteger | integer | There are no (further) constraints on this element Data type | ||||
valueRange | Range | There are no (further) constraints on this element Data type | ||||
valueRatio | Ratio | There are no (further) constraints on this element Data type | ||||
valueSampledData | SampledData | There are no (further) constraints on this element Data type | ||||
valueTime | time | There are no (further) constraints on this element Data type | ||||
valueDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.dataAbsentReasonShort description Why the result is missing DefinitionProvides a reason why the expected value in the element Observation.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. 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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
note | 0..* | Annotation | There are no (further) constraints on this element Element idObservation.noteShort description Comments about the observation DefinitionComments about the observation or the results. Need to be able to provide free text additional information. May include general statements about the observation, or statements about significant, unexpected or unreliable results values, or information about its source when relevant to its interpretation.
| |||
bodySite | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idObservation.bodySiteShort description Observed body part DefinitionIndicates the site on the subject's body where the observation was made (i.e. the target site). 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 bodySite. Codes describing anatomical locations. May include laterality. SNOMEDCTBodyStructures (example) Constraints
| |||
method | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idObservation.methodShort description How it was done DefinitionIndicates the mechanism used to perform the observation. In some cases, method can impact results and is thus used for determining whether results can be compared or determining significance of results. Only used if not implicit in code for Observation.code. Methods for simple observations.
| |||
specimen | 0..1 | Reference(Specimen) | There are no (further) constraints on this element Element idObservation.specimenShort description Specimen used for this observation DefinitionThe specimen that was used when this observation was made. Should only be used if not implicit in code found in
| |||
device | 0..1 | Reference(Device | DeviceMetric) | There are no (further) constraints on this element Element idObservation.deviceShort description (Measurement) Device DefinitionThe device used to generate the observation data. Note that this is not meant to represent a device involved in the transmission of the result, e.g., a gateway. Such devices may be documented using the Provenance resource where relevant. Reference(Device | DeviceMetric) Constraints
| |||
referenceRange | C | 0..* | BackboneElement | There are no (further) constraints on this element Element idObservation.referenceRangeShort description Provides guide for interpretation DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. Multiple reference ranges are interpreted as an "OR". In other words, to represent two distinct target populations, two 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. 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 might 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.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.referenceRange.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.referenceRange.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.referenceRange.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
low | C | 0..1 | SimpleQuantity | There are no (further) constraints on this element Element idObservation.referenceRange.lowShort description Low Range, if relevant DefinitionThe 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). The cardinality or value of this element may be affected by these constraints: obs-3 Constraints
| ||
high | C | 0..1 | SimpleQuantity | There are no (further) constraints on this element Element idObservation.referenceRange.highShort description High Range, if relevant DefinitionThe 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). The cardinality or value of this element may be affected by these constraints: obs-3 Constraints
| ||
type | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.referenceRange.typeShort description Reference range qualifier DefinitionCodes to indicate the what part of the targeted reference population it applies to. For example, the normal or therapeutic range. Need to be able to say what kind of reference range this is - normal, recommended, therapeutic, etc., - for proper interpretation. This SHOULD be populated if there is more than one range. If this element is not present then the normal range is assumed. Code for the meaning of a reference range. ObservationReferenceRangeMeaningCodes (preferred) Constraints
| |||
appliesTo | 0..* | CodeableConcept | There are no (further) constraints on this element Element idObservation.referenceRange.appliesToShort description Reference range population DefinitionCodes 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. Multiple Need to be able to identify the target population for proper interpretation. This SHOULD be populated if there is more than one range. If this element is not present then the normal population is assumed. Codes identifying the population the reference range applies to. ObservationReferenceRangeAppliesToCodes (example) Constraints
| |||
age | 0..1 | Range | There are no (further) constraints on this element Element idObservation.referenceRange.ageShort description Applicable age range, if relevant DefinitionThe 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. Some analytes vary greatly over age.
| |||
text | 0..1 | string | There are no (further) constraints on this element Element idObservation.referenceRange.textShort description Text based reference range in an observation DefinitionText 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".
| |||
hasMember | Σ | 0..* | Reference(Observation | QuestionnaireResponse | MolecularSequence) | There are no (further) constraints on this element Element idObservation.hasMemberShort description Related resource that belongs to the Observation group DefinitionThis observation is a group observation (e.g. a battery, a panel of tests, a set of vital sign measurements) that includes the target as a member of the group. When using this element, an observation will typically have either a value or a set of related resources, although both may be present in some cases. For a discussion on the ways Observations can assembled in groups together, see Notes below. Note that a system may calculate results from QuestionnaireResponse into a final score and represent the score as an Observation. Reference(Observation | QuestionnaireResponse | MolecularSequence) Constraints
| ||
derivedFrom | Σ | 0..* | Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence) | There are no (further) constraints on this element Element idObservation.derivedFromShort description Related measurements the observation is made from DefinitionThe target resource that represents a measurement from which this observation value is derived. For example, a calculated anion gap or a fetal measurement based on an ultrasound image. All the reference choices that are listed in this element can represent clinical observations and other measurements that may be the source for a derived value. The most common reference will be another Observation. For a discussion on the ways Observations can assembled in groups together, see Notes below. Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence) Constraints
| ||
component | Σ | 0..* | BackboneElement | Element idObservation.componentShort description Component results DefinitionSome 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. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below. Unordered, Open, by code(Pattern) Constraints
| ||
(All Slices) | The requirements in this element apply to all slices | |||||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConcept | There are no (further) constraints on this element Element idObservation.component.codeShort description Type of component observation (code / type) DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
| ||
value[x] | Σ | 0..1 | There are no (further) constraints on this element Element idObservation.component.value[x]Short description Actual component result DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below.
| |||
valueQuantity | Quantity | There are no (further) constraints on this element Data type | ||||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
valueString | string | There are no (further) constraints on this element Data type | ||||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||||
valueInteger | integer | There are no (further) constraints on this element Data type | ||||
valueRange | Range | There are no (further) constraints on this element Data type | ||||
valueRatio | Ratio | There are no (further) constraints on this element Data type | ||||
valueSampledData | SampledData | There are no (further) constraints on this element Data type | ||||
valueTime | time | There are no (further) constraints on this element Data type | ||||
valueDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
statuscode | Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idObservation.component:statuscodeShort description Component results DefinitionSome 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. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:statuscode.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:statuscode.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:statuscode.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | Element idObservation.component:statuscode.codeShort description Type of component observation (code / type) DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://omi.de/fhir/registry/sid/component-codes", "code": "statuscode" } ] }Mappings
| ||
value[x] | Σ | 1..1 | Element idObservation.component:statuscode.value[x]Short description Actual component result DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below. Unordered, Open, by $this(Type) Constraints
| |||
valueQuantity | Quantity | There are no (further) constraints on this element Data type | ||||
valueString | string | There are no (further) constraints on this element Data type | ||||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||||
valueInteger | integer | There are no (further) constraints on this element Data type | ||||
valueRange | Range | There are no (further) constraints on this element Data type | ||||
valueRatio | Ratio | There are no (further) constraints on this element Data type | ||||
valueSampledData | SampledData | There are no (further) constraints on this element Data type | ||||
valueTime | time | There are no (further) constraints on this element Data type | ||||
valueDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
valueCodeableConcept | Σ | 1..1 | CodeableConceptBinding | Element idObservation.component:statuscode.value[x]:valueCodeableConceptShort description Actual component result DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below. AiServiceStatusCodesVS (required) Constraints
| ||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:statuscode.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:statuscode.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:statuscode.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
queue-length | Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idObservation.component:queue-lengthShort description Component results DefinitionSome 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. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:queue-length.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:queue-length.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:queue-length.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | Element idObservation.component:queue-length.codeShort description Type of component observation (code / type) DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://omi.de/fhir/registry/sid/component-codes", "code": "queue-length" } ] }Mappings
| ||
value[x] | Σ | 1..1 | Element idObservation.component:queue-length.value[x]Short description Actual component result DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below. Unordered, Open, by $this(Type) Constraints
| |||
valueQuantity | Quantity | There are no (further) constraints on this element Data type | ||||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
valueString | string | There are no (further) constraints on this element Data type | ||||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||||
valueRange | Range | There are no (further) constraints on this element Data type | ||||
valueRatio | Ratio | There are no (further) constraints on this element Data type | ||||
valueSampledData | SampledData | There are no (further) constraints on this element Data type | ||||
valueTime | time | There are no (further) constraints on this element Data type | ||||
valueDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
valueInteger | Σ | 1..1 | integer | Element idObservation.component:queue-length.value[x]:valueIntegerShort description Actual component result DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below.
| ||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:queue-length.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:queue-length.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:queue-length.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
estimated-waiting-time | Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idObservation.component:estimated-waiting-timeShort description Component results DefinitionSome 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. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:estimated-waiting-time.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:estimated-waiting-time.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:estimated-waiting-time.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | Element idObservation.component:estimated-waiting-time.codeShort description Type of component observation (code / type) DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://omi.de/fhir/registry/sid/component-codes", "code": "estimated-waiting-time" } ] }Mappings
| ||
value[x] | Σ | 1..1 | Element idObservation.component:estimated-waiting-time.value[x]Short description Actual component result DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below. Unordered, Open, by $this(Type) Constraints
| |||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
valueString | string | There are no (further) constraints on this element Data type | ||||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||||
valueInteger | integer | There are no (further) constraints on this element Data type | ||||
valueRange | Range | There are no (further) constraints on this element Data type | ||||
valueRatio | Ratio | There are no (further) constraints on this element Data type | ||||
valueSampledData | SampledData | There are no (further) constraints on this element Data type | ||||
valueTime | time | There are no (further) constraints on this element Data type | ||||
valueDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
valueQuantity | Σ | 1..1 | Quantity | Element idObservation.component:estimated-waiting-time.value[x]:valueQuantityShort description Actual component result DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:estimated-waiting-time.value[x]:valueQuantity.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:estimated-waiting-time.value[x]:valueQuantity.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
| ||
value | Σ | 0..1 | decimal | There are no (further) constraints on this element Element idObservation.component:estimated-waiting-time.value[x]:valueQuantity.valueShort description Numerical value (with implicit precision) DefinitionThe value of the measured amount. The value includes an implicit precision in the presentation of the value. Precision is handled implicitly in almost all cases of measurement. The implicit precision in the value should always be honored. Monetary values have their own rules for handling precision (refer to standard accounting text books).
| ||
comparator | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idObservation.component:estimated-waiting-time.value[x]:valueQuantity.comparatorShort description < | <= | >= | > - how to understand the value DefinitionHow the value should be understood and represented - whether the actual value is greater or less than the stated value due to measurement issues; e.g. if the comparator is "<" , then the real value is < stated value. Need a framework for handling measures where the value is <5ug/L or >400mg/L due to the limitations of measuring methodology. If there is no comparator, then there is no modification of the value How the Quantity should be understood and represented.
| ||
unit | Σ | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:estimated-waiting-time.value[x]:valueQuantity.unitShort description Unit representation DefinitionA human-readable form of the unit. There are many representations for units of measure and in many contexts, particular representations are fixed and required. I.e. mcg for micrograms.
| ||
system | Σ C | 0..1 | uriPattern | Element idObservation.component:estimated-waiting-time.value[x]:valueQuantity.systemShort description System that defines coded unit form DefinitionThe identification of the system that provides the coded form of the unit. Need to know the system that defines the coded form of the unit. The cardinality or value of this element may be affected by these constraints: qty-3 Constraints
http://unitsofmeasure.orgMappings
| ||
code | Σ | 0..1 | codeBinding | Element idObservation.component:estimated-waiting-time.value[x]:valueQuantity.codeShort description Coded form of the unit DefinitionA computer processable form of the unit in some unit representation system. Need a computable form of the unit that is fixed across all forms. UCUM provides this for quantities, but SNOMED CT provides many units of interest. The preferred system is UCUM, but SNOMED CT can also be used (for customary units) or ISO 4217 for currency. The context of use may additionally require a code from a particular system.
| ||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:estimated-waiting-time.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:estimated-waiting-time.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:estimated-waiting-time.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
inference-price | Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idObservation.component:inference-priceShort description Component results DefinitionSome 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. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:inference-price.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:inference-price.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:inference-price.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | Element idObservation.component:inference-price.codeShort description Type of component observation (code / type) DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://omi.de/fhir/registry/sid/component-codes", "code": "inference-price" } ] }Mappings
| ||
value[x] | Σ | 1..1 | Element idObservation.component:inference-price.value[x]Short description Actual component result DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below. Unordered, Open, by $this(Type) Constraints
| |||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
valueString | string | There are no (further) constraints on this element Data type | ||||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||||
valueInteger | integer | There are no (further) constraints on this element Data type | ||||
valueRange | Range | There are no (further) constraints on this element Data type | ||||
valueRatio | Ratio | There are no (further) constraints on this element Data type | ||||
valueSampledData | SampledData | There are no (further) constraints on this element Data type | ||||
valueTime | time | There are no (further) constraints on this element Data type | ||||
valueDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
valueQuantity | Σ | 1..1 | Quantity | Element idObservation.component:inference-price.value[x]:valueQuantityShort description Actual component result DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:inference-price.value[x]:valueQuantity.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:inference-price.value[x]:valueQuantity.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
| ||
value | Σ | 0..1 | decimal | There are no (further) constraints on this element Element idObservation.component:inference-price.value[x]:valueQuantity.valueShort description Numerical value (with implicit precision) DefinitionThe value of the measured amount. The value includes an implicit precision in the presentation of the value. Precision is handled implicitly in almost all cases of measurement. The implicit precision in the value should always be honored. Monetary values have their own rules for handling precision (refer to standard accounting text books).
| ||
comparator | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idObservation.component:inference-price.value[x]:valueQuantity.comparatorShort description < | <= | >= | > - how to understand the value DefinitionHow the value should be understood and represented - whether the actual value is greater or less than the stated value due to measurement issues; e.g. if the comparator is "<" , then the real value is < stated value. Need a framework for handling measures where the value is <5ug/L or >400mg/L due to the limitations of measuring methodology. If there is no comparator, then there is no modification of the value How the Quantity should be understood and represented.
| ||
unit | Σ | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:inference-price.value[x]:valueQuantity.unitShort description Unit representation DefinitionA human-readable form of the unit. There are many representations for units of measure and in many contexts, particular representations are fixed and required. I.e. mcg for micrograms.
| ||
system | Σ C | 0..1 | uriPattern | Element idObservation.component:inference-price.value[x]:valueQuantity.systemShort description System that defines coded unit form DefinitionThe identification of the system that provides the coded form of the unit. Need to know the system that defines the coded form of the unit. The cardinality or value of this element may be affected by these constraints: qty-3 Constraints
urn:iso:std:iso:4217Mappings
| ||
code | Σ | 0..1 | codePattern | Element idObservation.component:inference-price.value[x]:valueQuantity.codeShort description Coded form of the unit DefinitionA computer processable form of the unit in some unit representation system. Need a computable form of the unit that is fixed across all forms. UCUM provides this for quantities, but SNOMED CT provides many units of interest. The preferred system is UCUM, but SNOMED CT can also be used (for customary units) or ISO 4217 for currency. The context of use may additionally require a code from a particular system.
EURMappings
| ||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:inference-price.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:inference-price.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:inference-price.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
|
Example
Observation |
id : GbmHeartbeatObservationExample |
meta |
profile : http://omi.de/fhir/registry/StructureDefinition/HeartbeatObservationProfile |
extension |
extension |
url : hash |
value : b7edda3172c39fe8754d607f2182047479b05d31406009cdcf1183970f5397a4 |
extension |
url : type |
value |
coding |
code : SHA-256 |
system : http://terminology.hl7.org/CodeSystem/v3-IntegrityCheckAlgorithm |
display : secure hash algorithm - 256 |
url : http://omi.de/fhir/registry/StructureDefinition/build-hash-extension |
component |
code |
coding |
code : statuscode |
system : http://omi.de/fhir/registry/sid/component-codes |
display : Service Status |
value |
coding |
code : inference-ready |
system : http://omi.de/fhir/registry/CodeSystem/AiServiceStatusCodesCS |
display : Service is available and ready to apply inference |
component |
code |
coding |
code : queue-length |
system : http://omi.de/fhir/registry/sid/component-codes |
display : Queue Length |
value : 8 |
component |
value |
value : 20 |
unit : minutes |
system : http://unitsofmeasure.org |
code : min |
code |
coding |
code : estimated-waiting-time |
system : http://omi.de/fhir/registry/sid/component-codes |
display : Estimated Waiting Time |
component |
value |
value : 8 |
system : urn:iso:std:iso:4217 |
code : EUR |
code |
coding |
code : inference-price |
system : http://omi.de/fhir/registry/sid/component-codes |
display : Inference Price |
code |
coding |
code : C0449438 |
system : http://ncicb.nci.nih.gov/xml/owl/EVS/Thesaurus.owl |
display : Status |
status : amended |
Input Parameters
Description
Inputs for the GBM algorithm contain an image (Binary resource) and optional structured metainformation (ImagingStudy resource).
Profile
GbmServiceInputParameters (Parameters) | OmiServiceInputParameters | There are no (further) constraints on this element Element idParametersShort description Operation Request or Response DefinitionThis resource is a non-persisted resource used to pass information into and back from an operation. It has no other use, and there is no RESTful endpoint associated with it. The parameters that may be used are defined by the OperationDefinition resource.
| ||||
id | Σ | 0..1 | string | There are no (further) constraints on this element Element idParameters.idShort description Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. | ||
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idParameters.metaShort description Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
| ||
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idParameters.implicitRulesShort description A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
| ||
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idParameters.languageShort description Language of the resource content DefinitionThe base language in which the resource is written. 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). A human language.
| |||
parameter | S Σ C | 1..* | BackboneElement | There are no (further) constraints on this element Element idParameters.parameterShort description Operation Parameter DefinitionA parameter passed to or received from the operation. Unordered, Open, by name(Pattern) Constraints
| ||
(All Slices) | The requirements in this element apply to all slices | |||||
id | 0..1 | string | There are no (further) constraints on this element Element idParameters.parameter.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | S C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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. Unordered, Open, by url(Value) Constraints
| ||
parameterQueryExtension | S C | 0..1 | Extension(Complex) | There are no (further) constraints on this element Element idParameters.parameter.extension:parameterQueryExtensionShort description Service Input Parameter Query Extension Alternate namesextensions, user content DefinitionExtension to document how to get the value for a certain parameter. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttp://omi.de/fhir/registry/StructureDefinition/input-parameter-query-extension ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
name | S Σ | 1..1 | string | There are no (further) constraints on this element Element idParameters.parameter.nameShort description Name from the definition DefinitionThe name of the parameter (reference to the operation definition).
| ||
value[x] | S Σ C | 0..1 | There are no (further) constraints on this element Element idParameters.parameter.value[x]Short description If parameter is a data type DefinitionIf the parameter is a data type. The cardinality or value of this element may be affected by these constraints: inv-1 Constraints
| |||
valueBase64Binary | base64Binary | There are no (further) constraints on this element Data type | ||||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||||
valueCanonical | canonical() | There are no (further) constraints on this element Data type | ||||
valueCode | code | There are no (further) constraints on this element Data type | ||||
valueDate | date | There are no (further) constraints on this element Data type | ||||
valueDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
valueDecimal | decimal | There are no (further) constraints on this element Data type | ||||
valueId | id | There are no (further) constraints on this element Data type | ||||
valueInstant | instant | There are no (further) constraints on this element Data type | ||||
valueInteger | integer | There are no (further) constraints on this element Data type | ||||
valueMarkdown | markdown | There are no (further) constraints on this element Data type | ||||
valueOid | oid | There are no (further) constraints on this element Data type | ||||
valuePositiveInt | positiveInt | There are no (further) constraints on this element Data type | ||||
valueString | string | There are no (further) constraints on this element Data type | ||||
valueTime | time | There are no (further) constraints on this element Data type | ||||
valueUnsignedInt | unsignedInt | There are no (further) constraints on this element Data type | ||||
valueUri | uri | There are no (further) constraints on this element Data type | ||||
valueUrl | url | There are no (further) constraints on this element Data type | ||||
valueUuid | uuid | There are no (further) constraints on this element Data type | ||||
valueAddress | Address | There are no (further) constraints on this element Data type | ||||
valueAge | Age | There are no (further) constraints on this element Data type | ||||
valueAnnotation | Annotation | There are no (further) constraints on this element Data type | ||||
valueAttachment | Attachment | There are no (further) constraints on this element Data type | ||||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
valueCoding | Coding | There are no (further) constraints on this element Data type | ||||
valueContactPoint | ContactPoint | There are no (further) constraints on this element Data type | ||||
valueCount | Count | There are no (further) constraints on this element Data type | ||||
valueDistance | Distance | There are no (further) constraints on this element Data type | ||||
valueDuration | Duration | There are no (further) constraints on this element Data type | ||||
valueHumanName | HumanName | There are no (further) constraints on this element Data type | ||||
valueIdentifier | Identifier | There are no (further) constraints on this element Data type | ||||
valueMoney | Money | There are no (further) constraints on this element Data type | ||||
valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
valueQuantity | Quantity | There are no (further) constraints on this element Data type | ||||
valueRange | Range | There are no (further) constraints on this element Data type | ||||
valueRatio | Ratio | There are no (further) constraints on this element Data type | ||||
valueSampledData | SampledData | There are no (further) constraints on this element Data type | ||||
valueSignature | Signature | There are no (further) constraints on this element Data type | ||||
valueTiming | Timing | There are no (further) constraints on this element Data type | ||||
valueContactDetail | ContactDetail | There are no (further) constraints on this element Data type | ||||
valueContributor | Contributor | There are no (further) constraints on this element Data type | ||||
valueDataRequirement | DataRequirement | There are no (further) constraints on this element Data type | ||||
valueExpression | Expression | There are no (further) constraints on this element Data type | ||||
valueParameterDefinition | ParameterDefinition | There are no (further) constraints on this element Data type | ||||
valueRelatedArtifact | RelatedArtifact | There are no (further) constraints on this element Data type | ||||
valueTriggerDefinition | TriggerDefinition | There are no (further) constraints on this element Data type | ||||
valueUsageContext | UsageContext | There are no (further) constraints on this element Data type | ||||
valueDosage | Dosage | There are no (further) constraints on this element Data type | ||||
valueMeta | Meta | There are no (further) constraints on this element Data type | ||||
valueReference | Reference() | There are no (further) constraints on this element Data type | ||||
resource | S Σ C | 0..1 | Resource | There are no (further) constraints on this element Element idParameters.parameter.resourceShort description If parameter is a whole resource DefinitionIf the parameter is a whole resource. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods. The cardinality or value of this element may be affected by these constraints: inv-1 | ||
part | S Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element idParameters.parameter.partShort description Named part of a multi-part parameter DefinitionA named part of a multi-part parameter. Only one level of nested parameters is allowed.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idParameters.parameter.part.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | S C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter.part.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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. Unordered, Open, by url(Value) Constraints
| ||
parameterQueryExtension | S C | 0..1 | Extension(Complex) | There are no (further) constraints on this element Element idParameters.parameter.part.extension:parameterQueryExtensionShort description Service Input Parameter Query Extension Alternate namesextensions, user content DefinitionExtension to document how to get the value for a certain parameter. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttp://omi.de/fhir/registry/StructureDefinition/input-parameter-query-extension ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter.part.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
name | S Σ | 1..1 | string | There are no (further) constraints on this element Element idParameters.parameter.part.nameShort description Name from the definition DefinitionThe name of the parameter (reference to the operation definition).
| ||
value[x] | S Σ C | 0..1 | There are no (further) constraints on this element Element idParameters.parameter.part.value[x]Short description If parameter is a data type DefinitionIf the parameter is a data type. The cardinality or value of this element may be affected by these constraints: inv-1 Constraints
| |||
valueBase64Binary | base64Binary | There are no (further) constraints on this element Data type | ||||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||||
valueCanonical | canonical() | There are no (further) constraints on this element Data type | ||||
valueCode | code | There are no (further) constraints on this element Data type | ||||
valueDate | date | There are no (further) constraints on this element Data type | ||||
valueDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
valueDecimal | decimal | There are no (further) constraints on this element Data type | ||||
valueId | id | There are no (further) constraints on this element Data type | ||||
valueInstant | instant | There are no (further) constraints on this element Data type | ||||
valueInteger | integer | There are no (further) constraints on this element Data type | ||||
valueMarkdown | markdown | There are no (further) constraints on this element Data type | ||||
valueOid | oid | There are no (further) constraints on this element Data type | ||||
valuePositiveInt | positiveInt | There are no (further) constraints on this element Data type | ||||
valueString | string | There are no (further) constraints on this element Data type | ||||
valueTime | time | There are no (further) constraints on this element Data type | ||||
valueUnsignedInt | unsignedInt | There are no (further) constraints on this element Data type | ||||
valueUri | uri | There are no (further) constraints on this element Data type | ||||
valueUrl | url | There are no (further) constraints on this element Data type | ||||
valueUuid | uuid | There are no (further) constraints on this element Data type | ||||
valueAddress | Address | There are no (further) constraints on this element Data type | ||||
valueAge | Age | There are no (further) constraints on this element Data type | ||||
valueAnnotation | Annotation | There are no (further) constraints on this element Data type | ||||
valueAttachment | Attachment | There are no (further) constraints on this element Data type | ||||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
valueCoding | Coding | There are no (further) constraints on this element Data type | ||||
valueContactPoint | ContactPoint | There are no (further) constraints on this element Data type | ||||
valueCount | Count | There are no (further) constraints on this element Data type | ||||
valueDistance | Distance | There are no (further) constraints on this element Data type | ||||
valueDuration | Duration | There are no (further) constraints on this element Data type | ||||
valueHumanName | HumanName | There are no (further) constraints on this element Data type | ||||
valueIdentifier | Identifier | There are no (further) constraints on this element Data type | ||||
valueMoney | Money | There are no (further) constraints on this element Data type | ||||
valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
valueQuantity | Quantity | There are no (further) constraints on this element Data type | ||||
valueRange | Range | There are no (further) constraints on this element Data type | ||||
valueRatio | Ratio | There are no (further) constraints on this element Data type | ||||
valueSampledData | SampledData | There are no (further) constraints on this element Data type | ||||
valueSignature | Signature | There are no (further) constraints on this element Data type | ||||
valueTiming | Timing | There are no (further) constraints on this element Data type | ||||
valueContactDetail | ContactDetail | There are no (further) constraints on this element Data type | ||||
valueContributor | Contributor | There are no (further) constraints on this element Data type | ||||
valueDataRequirement | DataRequirement | There are no (further) constraints on this element Data type | ||||
valueExpression | Expression | There are no (further) constraints on this element Data type | ||||
valueParameterDefinition | ParameterDefinition | There are no (further) constraints on this element Data type | ||||
valueRelatedArtifact | RelatedArtifact | There are no (further) constraints on this element Data type | ||||
valueTriggerDefinition | TriggerDefinition | There are no (further) constraints on this element Data type | ||||
valueUsageContext | UsageContext | There are no (further) constraints on this element Data type | ||||
valueDosage | Dosage | There are no (further) constraints on this element Data type | ||||
valueMeta | Meta | There are no (further) constraints on this element Data type | ||||
valueReference | Reference() | There are no (further) constraints on this element Data type | ||||
resource | S Σ C | 0..1 | Resource | There are no (further) constraints on this element Element idParameters.parameter.part.resourceShort description If parameter is a whole resource DefinitionIf the parameter is a whole resource. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods. The cardinality or value of this element may be affected by these constraints: inv-1 | ||
part | Σ | 0..* | see (parameter) | There are no (further) constraints on this element Element idParameters.parameter.part.partShort description Named part of a multi-part parameter DefinitionA named part of a multi-part parameter. Only one level of nested parameters is allowed.
| ||
image | S Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idParameters.parameter:imageShort description Operation Parameter DefinitionA parameter passed to or received from the operation.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idParameters.parameter:image.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter:image.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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. Unordered, Open, by url(Value) Constraints
| ||
parameterQueryExtension | S C | 0..1 | Extension(Complex) | There are no (further) constraints on this element Element idParameters.parameter:image.extension:parameterQueryExtensionShort description Service Input Parameter Query Extension Alternate namesextensions, user content DefinitionExtension to document how to get the value for a certain parameter. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttp://omi.de/fhir/registry/StructureDefinition/input-parameter-query-extension ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter:image.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
name | Σ | 1..1 | stringPattern | There are no (further) constraints on this element Element idParameters.parameter:image.nameShort description Name from the definition DefinitionThe name of the parameter (reference to the operation definition).
image | ||
value[x] | Σ C | 0..1 | There are no (further) constraints on this element Element idParameters.parameter:image.value[x]Short description If parameter is a data type DefinitionIf the parameter is a data type. The cardinality or value of this element may be affected by these constraints: inv-1 Constraints
| |||
valueBase64Binary | base64Binary | There are no (further) constraints on this element Data type | ||||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||||
valueCanonical | canonical() | There are no (further) constraints on this element Data type | ||||
valueCode | code | There are no (further) constraints on this element Data type | ||||
valueDate | date | There are no (further) constraints on this element Data type | ||||
valueDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
valueDecimal | decimal | There are no (further) constraints on this element Data type | ||||
valueId | id | There are no (further) constraints on this element Data type | ||||
valueInstant | instant | There are no (further) constraints on this element Data type | ||||
valueInteger | integer | There are no (further) constraints on this element Data type | ||||
valueMarkdown | markdown | There are no (further) constraints on this element Data type | ||||
valueOid | oid | There are no (further) constraints on this element Data type | ||||
valuePositiveInt | positiveInt | There are no (further) constraints on this element Data type | ||||
valueString | string | There are no (further) constraints on this element Data type | ||||
valueTime | time | There are no (further) constraints on this element Data type | ||||
valueUnsignedInt | unsignedInt | There are no (further) constraints on this element Data type | ||||
valueUri | uri | There are no (further) constraints on this element Data type | ||||
valueUrl | url | There are no (further) constraints on this element Data type | ||||
valueUuid | uuid | There are no (further) constraints on this element Data type | ||||
valueAddress | Address | There are no (further) constraints on this element Data type | ||||
valueAge | Age | There are no (further) constraints on this element Data type | ||||
valueAnnotation | Annotation | There are no (further) constraints on this element Data type | ||||
valueAttachment | Attachment | There are no (further) constraints on this element Data type | ||||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
valueCoding | Coding | There are no (further) constraints on this element Data type | ||||
valueContactPoint | ContactPoint | There are no (further) constraints on this element Data type | ||||
valueCount | Count | There are no (further) constraints on this element Data type | ||||
valueDistance | Distance | There are no (further) constraints on this element Data type | ||||
valueDuration | Duration | There are no (further) constraints on this element Data type | ||||
valueHumanName | HumanName | There are no (further) constraints on this element Data type | ||||
valueIdentifier | Identifier | There are no (further) constraints on this element Data type | ||||
valueMoney | Money | There are no (further) constraints on this element Data type | ||||
valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
valueQuantity | Quantity | There are no (further) constraints on this element Data type | ||||
valueRange | Range | There are no (further) constraints on this element Data type | ||||
valueRatio | Ratio | There are no (further) constraints on this element Data type | ||||
valueSampledData | SampledData | There are no (further) constraints on this element Data type | ||||
valueSignature | Signature | There are no (further) constraints on this element Data type | ||||
valueTiming | Timing | There are no (further) constraints on this element Data type | ||||
valueContactDetail | ContactDetail | There are no (further) constraints on this element Data type | ||||
valueContributor | Contributor | There are no (further) constraints on this element Data type | ||||
valueDataRequirement | DataRequirement | There are no (further) constraints on this element Data type | ||||
valueExpression | Expression | There are no (further) constraints on this element Data type | ||||
valueParameterDefinition | ParameterDefinition | There are no (further) constraints on this element Data type | ||||
valueRelatedArtifact | RelatedArtifact | There are no (further) constraints on this element Data type | ||||
valueTriggerDefinition | TriggerDefinition | There are no (further) constraints on this element Data type | ||||
valueUsageContext | UsageContext | There are no (further) constraints on this element Data type | ||||
valueDosage | Dosage | There are no (further) constraints on this element Data type | ||||
valueMeta | Meta | There are no (further) constraints on this element Data type | ||||
valueReference | Reference() | There are no (further) constraints on this element Data type | ||||
resource | C | 1..1 | OMIDocumentReference | There are no (further) constraints on this element Element idParameters.parameter:image.resourceShort description A reference to a document DefinitionA reference to a document of any kind for any purpose. Provides metadata about the document so that the document can be discovered and managed. The scope of a document is any seralized object with a mime-type, so includes formal patient centric documents (CDA), cliical notes, scanned paper, and non-patient specific documents like policy text. Usually, this is used for documents other than those defined by FHIR. The cardinality or value of this element may be affected by these constraints: inv-1 Constraints
| ||
part | Σ | 0..* | see (parameter) | There are no (further) constraints on this element Element idParameters.parameter:image.partShort description Named part of a multi-part parameter DefinitionA named part of a multi-part parameter. Only one level of nested parameters is allowed.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idParameters.parameter:image.part.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter:image.part.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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. Unordered, Open, by url(Value) Constraints
| ||
parameterQueryExtension | S C | 0..1 | Extension(Complex) | There are no (further) constraints on this element Element idParameters.parameter:image.part.extension:parameterQueryExtensionShort description Service Input Parameter Query Extension Alternate namesextensions, user content DefinitionExtension to document how to get the value for a certain parameter. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttp://omi.de/fhir/registry/StructureDefinition/input-parameter-query-extension ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter:image.part.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
name | Σ | 1..1 | string | There are no (further) constraints on this element Element idParameters.parameter:image.part.nameShort description Name from the definition DefinitionThe name of the parameter (reference to the operation definition).
| ||
value[x] | Σ C | 0..1 | There are no (further) constraints on this element Element idParameters.parameter:image.part.value[x]Short description If parameter is a data type DefinitionIf the parameter is a data type. The cardinality or value of this element may be affected by these constraints: inv-1 Constraints
| |||
valueBase64Binary | base64Binary | There are no (further) constraints on this element Data type | ||||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||||
valueCanonical | canonical() | There are no (further) constraints on this element Data type | ||||
valueCode | code | There are no (further) constraints on this element Data type | ||||
valueDate | date | There are no (further) constraints on this element Data type | ||||
valueDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
valueDecimal | decimal | There are no (further) constraints on this element Data type | ||||
valueId | id | There are no (further) constraints on this element Data type | ||||
valueInstant | instant | There are no (further) constraints on this element Data type | ||||
valueInteger | integer | There are no (further) constraints on this element Data type | ||||
valueMarkdown | markdown | There are no (further) constraints on this element Data type | ||||
valueOid | oid | There are no (further) constraints on this element Data type | ||||
valuePositiveInt | positiveInt | There are no (further) constraints on this element Data type | ||||
valueString | string | There are no (further) constraints on this element Data type | ||||
valueTime | time | There are no (further) constraints on this element Data type | ||||
valueUnsignedInt | unsignedInt | There are no (further) constraints on this element Data type | ||||
valueUri | uri | There are no (further) constraints on this element Data type | ||||
valueUrl | url | There are no (further) constraints on this element Data type | ||||
valueUuid | uuid | There are no (further) constraints on this element Data type | ||||
valueAddress | Address | There are no (further) constraints on this element Data type | ||||
valueAge | Age | There are no (further) constraints on this element Data type | ||||
valueAnnotation | Annotation | There are no (further) constraints on this element Data type | ||||
valueAttachment | Attachment | There are no (further) constraints on this element Data type | ||||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
valueCoding | Coding | There are no (further) constraints on this element Data type | ||||
valueContactPoint | ContactPoint | There are no (further) constraints on this element Data type | ||||
valueCount | Count | There are no (further) constraints on this element Data type | ||||
valueDistance | Distance | There are no (further) constraints on this element Data type | ||||
valueDuration | Duration | There are no (further) constraints on this element Data type | ||||
valueHumanName | HumanName | There are no (further) constraints on this element Data type | ||||
valueIdentifier | Identifier | There are no (further) constraints on this element Data type | ||||
valueMoney | Money | There are no (further) constraints on this element Data type | ||||
valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
valueQuantity | Quantity | There are no (further) constraints on this element Data type | ||||
valueRange | Range | There are no (further) constraints on this element Data type | ||||
valueRatio | Ratio | There are no (further) constraints on this element Data type | ||||
valueSampledData | SampledData | There are no (further) constraints on this element Data type | ||||
valueSignature | Signature | There are no (further) constraints on this element Data type | ||||
valueTiming | Timing | There are no (further) constraints on this element Data type | ||||
valueContactDetail | ContactDetail | There are no (further) constraints on this element Data type | ||||
valueContributor | Contributor | There are no (further) constraints on this element Data type | ||||
valueDataRequirement | DataRequirement | There are no (further) constraints on this element Data type | ||||
valueExpression | Expression | There are no (further) constraints on this element Data type | ||||
valueParameterDefinition | ParameterDefinition | There are no (further) constraints on this element Data type | ||||
valueRelatedArtifact | RelatedArtifact | There are no (further) constraints on this element Data type | ||||
valueTriggerDefinition | TriggerDefinition | There are no (further) constraints on this element Data type | ||||
valueUsageContext | UsageContext | There are no (further) constraints on this element Data type | ||||
valueDosage | Dosage | There are no (further) constraints on this element Data type | ||||
valueMeta | Meta | There are no (further) constraints on this element Data type | ||||
valueReference | Reference() | There are no (further) constraints on this element Data type | ||||
resource | Σ C | 0..1 | Resource | There are no (further) constraints on this element Element idParameters.parameter:image.part.resourceShort description If parameter is a whole resource DefinitionIf the parameter is a whole resource. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods. The cardinality or value of this element may be affected by these constraints: inv-1 | ||
part | Σ | 0..* | see (parameter) | There are no (further) constraints on this element Element idParameters.parameter:image.part.partShort description Named part of a multi-part parameter DefinitionA named part of a multi-part parameter. Only one level of nested parameters is allowed.
| ||
imagingStudy | S Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idParameters.parameter:imagingStudyShort description Operation Parameter DefinitionA parameter passed to or received from the operation.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idParameters.parameter:imagingStudy.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter:imagingStudy.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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. Unordered, Open, by url(Value) Constraints
| ||
parameterQueryExtension | S C | 0..1 | Extension(Complex) | There are no (further) constraints on this element Element idParameters.parameter:imagingStudy.extension:parameterQueryExtensionShort description Service Input Parameter Query Extension Alternate namesextensions, user content DefinitionExtension to document how to get the value for a certain parameter. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttp://omi.de/fhir/registry/StructureDefinition/input-parameter-query-extension ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter:imagingStudy.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
name | Σ | 1..1 | stringPattern | There are no (further) constraints on this element Element idParameters.parameter:imagingStudy.nameShort description Name from the definition DefinitionThe name of the parameter (reference to the operation definition).
imagingStudy | ||
value[x] | Σ C | 0..1 | There are no (further) constraints on this element Element idParameters.parameter:imagingStudy.value[x]Short description If parameter is a data type DefinitionIf the parameter is a data type. The cardinality or value of this element may be affected by these constraints: inv-1 Constraints
| |||
valueBase64Binary | base64Binary | There are no (further) constraints on this element Data type | ||||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||||
valueCanonical | canonical() | There are no (further) constraints on this element Data type | ||||
valueCode | code | There are no (further) constraints on this element Data type | ||||
valueDate | date | There are no (further) constraints on this element Data type | ||||
valueDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
valueDecimal | decimal | There are no (further) constraints on this element Data type | ||||
valueId | id | There are no (further) constraints on this element Data type | ||||
valueInstant | instant | There are no (further) constraints on this element Data type | ||||
valueInteger | integer | There are no (further) constraints on this element Data type | ||||
valueMarkdown | markdown | There are no (further) constraints on this element Data type | ||||
valueOid | oid | There are no (further) constraints on this element Data type | ||||
valuePositiveInt | positiveInt | There are no (further) constraints on this element Data type | ||||
valueString | string | There are no (further) constraints on this element Data type | ||||
valueTime | time | There are no (further) constraints on this element Data type | ||||
valueUnsignedInt | unsignedInt | There are no (further) constraints on this element Data type | ||||
valueUri | uri | There are no (further) constraints on this element Data type | ||||
valueUrl | url | There are no (further) constraints on this element Data type | ||||
valueUuid | uuid | There are no (further) constraints on this element Data type | ||||
valueAddress | Address | There are no (further) constraints on this element Data type | ||||
valueAge | Age | There are no (further) constraints on this element Data type | ||||
valueAnnotation | Annotation | There are no (further) constraints on this element Data type | ||||
valueAttachment | Attachment | There are no (further) constraints on this element Data type | ||||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
valueCoding | Coding | There are no (further) constraints on this element Data type | ||||
valueContactPoint | ContactPoint | There are no (further) constraints on this element Data type | ||||
valueCount | Count | There are no (further) constraints on this element Data type | ||||
valueDistance | Distance | There are no (further) constraints on this element Data type | ||||
valueDuration | Duration | There are no (further) constraints on this element Data type | ||||
valueHumanName | HumanName | There are no (further) constraints on this element Data type | ||||
valueIdentifier | Identifier | There are no (further) constraints on this element Data type | ||||
valueMoney | Money | There are no (further) constraints on this element Data type | ||||
valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
valueQuantity | Quantity | There are no (further) constraints on this element Data type | ||||
valueRange | Range | There are no (further) constraints on this element Data type | ||||
valueRatio | Ratio | There are no (further) constraints on this element Data type | ||||
valueSampledData | SampledData | There are no (further) constraints on this element Data type | ||||
valueSignature | Signature | There are no (further) constraints on this element Data type | ||||
valueTiming | Timing | There are no (further) constraints on this element Data type | ||||
valueContactDetail | ContactDetail | There are no (further) constraints on this element Data type | ||||
valueContributor | Contributor | There are no (further) constraints on this element Data type | ||||
valueDataRequirement | DataRequirement | There are no (further) constraints on this element Data type | ||||
valueExpression | Expression | There are no (further) constraints on this element Data type | ||||
valueParameterDefinition | ParameterDefinition | There are no (further) constraints on this element Data type | ||||
valueRelatedArtifact | RelatedArtifact | There are no (further) constraints on this element Data type | ||||
valueTriggerDefinition | TriggerDefinition | There are no (further) constraints on this element Data type | ||||
valueUsageContext | UsageContext | There are no (further) constraints on this element Data type | ||||
valueDosage | Dosage | There are no (further) constraints on this element Data type | ||||
valueMeta | Meta | There are no (further) constraints on this element Data type | ||||
valueReference | Reference() | There are no (further) constraints on this element Data type | ||||
resource | C | 1..1 | MII_PR_Bildgebung_Bildgebungsstudie | There are no (further) constraints on this element Element idParameters.parameter:imagingStudy.resourceShort description A set of images produced in single study (one or more series of references images) DefinitionRepresentation of the content produced in a DICOM imaging study. A study comprises a set of series, each of which includes a set of Service-Object Pair Instances (SOP Instances - images or other data) acquired or produced in a common context. A series is of only one modality (e.g. X-ray, CT, MR, ultrasound), but a study may have multiple series of different modalities. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods. MII_PR_Bildgebung_Bildgebungsstudie ConditionsThe cardinality or value of this element may be affected by these constraints: inv-1 Constraints
| ||
part | Σ | 0..* | see (parameter) | There are no (further) constraints on this element Element idParameters.parameter:imagingStudy.partShort description Named part of a multi-part parameter DefinitionA named part of a multi-part parameter. Only one level of nested parameters is allowed.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idParameters.parameter:imagingStudy.part.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter:imagingStudy.part.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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. Unordered, Open, by url(Value) Constraints
| ||
parameterQueryExtension | S C | 0..1 | Extension(Complex) | There are no (further) constraints on this element Element idParameters.parameter:imagingStudy.part.extension:parameterQueryExtensionShort description Service Input Parameter Query Extension Alternate namesextensions, user content DefinitionExtension to document how to get the value for a certain parameter. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttp://omi.de/fhir/registry/StructureDefinition/input-parameter-query-extension ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter:imagingStudy.part.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
name | Σ | 1..1 | string | There are no (further) constraints on this element Element idParameters.parameter:imagingStudy.part.nameShort description Name from the definition DefinitionThe name of the parameter (reference to the operation definition).
| ||
value[x] | Σ C | 0..1 | There are no (further) constraints on this element Element idParameters.parameter:imagingStudy.part.value[x]Short description If parameter is a data type DefinitionIf the parameter is a data type. The cardinality or value of this element may be affected by these constraints: inv-1 Constraints
| |||
valueBase64Binary | base64Binary | There are no (further) constraints on this element Data type | ||||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||||
valueCanonical | canonical() | There are no (further) constraints on this element Data type | ||||
valueCode | code | There are no (further) constraints on this element Data type | ||||
valueDate | date | There are no (further) constraints on this element Data type | ||||
valueDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
valueDecimal | decimal | There are no (further) constraints on this element Data type | ||||
valueId | id | There are no (further) constraints on this element Data type | ||||
valueInstant | instant | There are no (further) constraints on this element Data type | ||||
valueInteger | integer | There are no (further) constraints on this element Data type | ||||
valueMarkdown | markdown | There are no (further) constraints on this element Data type | ||||
valueOid | oid | There are no (further) constraints on this element Data type | ||||
valuePositiveInt | positiveInt | There are no (further) constraints on this element Data type | ||||
valueString | string | There are no (further) constraints on this element Data type | ||||
valueTime | time | There are no (further) constraints on this element Data type | ||||
valueUnsignedInt | unsignedInt | There are no (further) constraints on this element Data type | ||||
valueUri | uri | There are no (further) constraints on this element Data type | ||||
valueUrl | url | There are no (further) constraints on this element Data type | ||||
valueUuid | uuid | There are no (further) constraints on this element Data type | ||||
valueAddress | Address | There are no (further) constraints on this element Data type | ||||
valueAge | Age | There are no (further) constraints on this element Data type | ||||
valueAnnotation | Annotation | There are no (further) constraints on this element Data type | ||||
valueAttachment | Attachment | There are no (further) constraints on this element Data type | ||||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
valueCoding | Coding | There are no (further) constraints on this element Data type | ||||
valueContactPoint | ContactPoint | There are no (further) constraints on this element Data type | ||||
valueCount | Count | There are no (further) constraints on this element Data type | ||||
valueDistance | Distance | There are no (further) constraints on this element Data type | ||||
valueDuration | Duration | There are no (further) constraints on this element Data type | ||||
valueHumanName | HumanName | There are no (further) constraints on this element Data type | ||||
valueIdentifier | Identifier | There are no (further) constraints on this element Data type | ||||
valueMoney | Money | There are no (further) constraints on this element Data type | ||||
valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
valueQuantity | Quantity | There are no (further) constraints on this element Data type | ||||
valueRange | Range | There are no (further) constraints on this element Data type | ||||
valueRatio | Ratio | There are no (further) constraints on this element Data type | ||||
valueSampledData | SampledData | There are no (further) constraints on this element Data type | ||||
valueSignature | Signature | There are no (further) constraints on this element Data type | ||||
valueTiming | Timing | There are no (further) constraints on this element Data type | ||||
valueContactDetail | ContactDetail | There are no (further) constraints on this element Data type | ||||
valueContributor | Contributor | There are no (further) constraints on this element Data type | ||||
valueDataRequirement | DataRequirement | There are no (further) constraints on this element Data type | ||||
valueExpression | Expression | There are no (further) constraints on this element Data type | ||||
valueParameterDefinition | ParameterDefinition | There are no (further) constraints on this element Data type | ||||
valueRelatedArtifact | RelatedArtifact | There are no (further) constraints on this element Data type | ||||
valueTriggerDefinition | TriggerDefinition | There are no (further) constraints on this element Data type | ||||
valueUsageContext | UsageContext | There are no (further) constraints on this element Data type | ||||
valueDosage | Dosage | There are no (further) constraints on this element Data type | ||||
valueMeta | Meta | There are no (further) constraints on this element Data type | ||||
valueReference | Reference() | There are no (further) constraints on this element Data type | ||||
resource | Σ C | 0..1 | Resource | There are no (further) constraints on this element Element idParameters.parameter:imagingStudy.part.resourceShort description If parameter is a whole resource DefinitionIf the parameter is a whole resource. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods. The cardinality or value of this element may be affected by these constraints: inv-1 | ||
part | Σ | 0..* | see (parameter) | There are no (further) constraints on this element Element idParameters.parameter:imagingStudy.part.partShort description Named part of a multi-part parameter DefinitionA named part of a multi-part parameter. Only one level of nested parameters is allowed.
| ||
image-binary | S Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idParameters.parameter:image-binaryShort description Operation Parameter DefinitionA parameter passed to or received from the operation.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idParameters.parameter:image-binary.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter:image-binary.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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. Unordered, Open, by url(Value) Constraints
| ||
parameterQueryExtension | S C | 0..1 | Extension(Complex) | There are no (further) constraints on this element Element idParameters.parameter:image-binary.extension:parameterQueryExtensionShort description Service Input Parameter Query Extension Alternate namesextensions, user content DefinitionExtension to document how to get the value for a certain parameter. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttp://omi.de/fhir/registry/StructureDefinition/input-parameter-query-extension ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter:image-binary.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
name | Σ | 1..1 | stringPattern | There are no (further) constraints on this element Element idParameters.parameter:image-binary.nameShort description Name from the definition DefinitionThe name of the parameter (reference to the operation definition).
image-binary | ||
value[x] | Σ C | 0..1 | There are no (further) constraints on this element Element idParameters.parameter:image-binary.value[x]Short description If parameter is a data type DefinitionIf the parameter is a data type. The cardinality or value of this element may be affected by these constraints: inv-1 Constraints
| |||
valueBase64Binary | base64Binary | There are no (further) constraints on this element Data type | ||||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||||
valueCanonical | canonical() | There are no (further) constraints on this element Data type | ||||
valueCode | code | There are no (further) constraints on this element Data type | ||||
valueDate | date | There are no (further) constraints on this element Data type | ||||
valueDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
valueDecimal | decimal | There are no (further) constraints on this element Data type | ||||
valueId | id | There are no (further) constraints on this element Data type | ||||
valueInstant | instant | There are no (further) constraints on this element Data type | ||||
valueInteger | integer | There are no (further) constraints on this element Data type | ||||
valueMarkdown | markdown | There are no (further) constraints on this element Data type | ||||
valueOid | oid | There are no (further) constraints on this element Data type | ||||
valuePositiveInt | positiveInt | There are no (further) constraints on this element Data type | ||||
valueString | string | There are no (further) constraints on this element Data type | ||||
valueTime | time | There are no (further) constraints on this element Data type | ||||
valueUnsignedInt | unsignedInt | There are no (further) constraints on this element Data type | ||||
valueUri | uri | There are no (further) constraints on this element Data type | ||||
valueUrl | url | There are no (further) constraints on this element Data type | ||||
valueUuid | uuid | There are no (further) constraints on this element Data type | ||||
valueAddress | Address | There are no (further) constraints on this element Data type | ||||
valueAge | Age | There are no (further) constraints on this element Data type | ||||
valueAnnotation | Annotation | There are no (further) constraints on this element Data type | ||||
valueAttachment | Attachment | There are no (further) constraints on this element Data type | ||||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
valueCoding | Coding | There are no (further) constraints on this element Data type | ||||
valueContactPoint | ContactPoint | There are no (further) constraints on this element Data type | ||||
valueCount | Count | There are no (further) constraints on this element Data type | ||||
valueDistance | Distance | There are no (further) constraints on this element Data type | ||||
valueDuration | Duration | There are no (further) constraints on this element Data type | ||||
valueHumanName | HumanName | There are no (further) constraints on this element Data type | ||||
valueIdentifier | Identifier | There are no (further) constraints on this element Data type | ||||
valueMoney | Money | There are no (further) constraints on this element Data type | ||||
valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
valueQuantity | Quantity | There are no (further) constraints on this element Data type | ||||
valueRange | Range | There are no (further) constraints on this element Data type | ||||
valueRatio | Ratio | There are no (further) constraints on this element Data type | ||||
valueSampledData | SampledData | There are no (further) constraints on this element Data type | ||||
valueSignature | Signature | There are no (further) constraints on this element Data type | ||||
valueTiming | Timing | There are no (further) constraints on this element Data type | ||||
valueContactDetail | ContactDetail | There are no (further) constraints on this element Data type | ||||
valueContributor | Contributor | There are no (further) constraints on this element Data type | ||||
valueDataRequirement | DataRequirement | There are no (further) constraints on this element Data type | ||||
valueExpression | Expression | There are no (further) constraints on this element Data type | ||||
valueParameterDefinition | ParameterDefinition | There are no (further) constraints on this element Data type | ||||
valueRelatedArtifact | RelatedArtifact | There are no (further) constraints on this element Data type | ||||
valueTriggerDefinition | TriggerDefinition | There are no (further) constraints on this element Data type | ||||
valueUsageContext | UsageContext | There are no (further) constraints on this element Data type | ||||
valueDosage | Dosage | There are no (further) constraints on this element Data type | ||||
valueMeta | Meta | There are no (further) constraints on this element Data type | ||||
valueReference | Reference() | There are no (further) constraints on this element Data type | ||||
resource | Σ C | 1..1 | Binary | There are no (further) constraints on this element Element idParameters.parameter:image-binary.resourceShort description If parameter is a whole resource DefinitionIf the parameter is a whole resource. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods. The cardinality or value of this element may be affected by these constraints: inv-1 | ||
part | Σ | 0..* | see (parameter) | There are no (further) constraints on this element Element idParameters.parameter:image-binary.partShort description Named part of a multi-part parameter DefinitionA named part of a multi-part parameter. Only one level of nested parameters is allowed.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idParameters.parameter:image-binary.part.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter:image-binary.part.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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. Unordered, Open, by url(Value) Constraints
| ||
parameterQueryExtension | S C | 0..1 | Extension(Complex) | There are no (further) constraints on this element Element idParameters.parameter:image-binary.part.extension:parameterQueryExtensionShort description Service Input Parameter Query Extension Alternate namesextensions, user content DefinitionExtension to document how to get the value for a certain parameter. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttp://omi.de/fhir/registry/StructureDefinition/input-parameter-query-extension ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter:image-binary.part.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
name | Σ | 1..1 | string | There are no (further) constraints on this element Element idParameters.parameter:image-binary.part.nameShort description Name from the definition DefinitionThe name of the parameter (reference to the operation definition).
| ||
value[x] | Σ C | 0..1 | There are no (further) constraints on this element Element idParameters.parameter:image-binary.part.value[x]Short description If parameter is a data type DefinitionIf the parameter is a data type. The cardinality or value of this element may be affected by these constraints: inv-1 Constraints
| |||
valueBase64Binary | base64Binary | There are no (further) constraints on this element Data type | ||||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||||
valueCanonical | canonical() | There are no (further) constraints on this element Data type | ||||
valueCode | code | There are no (further) constraints on this element Data type | ||||
valueDate | date | There are no (further) constraints on this element Data type | ||||
valueDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
valueDecimal | decimal | There are no (further) constraints on this element Data type | ||||
valueId | id | There are no (further) constraints on this element Data type | ||||
valueInstant | instant | There are no (further) constraints on this element Data type | ||||
valueInteger | integer | There are no (further) constraints on this element Data type | ||||
valueMarkdown | markdown | There are no (further) constraints on this element Data type | ||||
valueOid | oid | There are no (further) constraints on this element Data type | ||||
valuePositiveInt | positiveInt | There are no (further) constraints on this element Data type | ||||
valueString | string | There are no (further) constraints on this element Data type | ||||
valueTime | time | There are no (further) constraints on this element Data type | ||||
valueUnsignedInt | unsignedInt | There are no (further) constraints on this element Data type | ||||
valueUri | uri | There are no (further) constraints on this element Data type | ||||
valueUrl | url | There are no (further) constraints on this element Data type | ||||
valueUuid | uuid | There are no (further) constraints on this element Data type | ||||
valueAddress | Address | There are no (further) constraints on this element Data type | ||||
valueAge | Age | There are no (further) constraints on this element Data type | ||||
valueAnnotation | Annotation | There are no (further) constraints on this element Data type | ||||
valueAttachment | Attachment | There are no (further) constraints on this element Data type | ||||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
valueCoding | Coding | There are no (further) constraints on this element Data type | ||||
valueContactPoint | ContactPoint | There are no (further) constraints on this element Data type | ||||
valueCount | Count | There are no (further) constraints on this element Data type | ||||
valueDistance | Distance | There are no (further) constraints on this element Data type | ||||
valueDuration | Duration | There are no (further) constraints on this element Data type | ||||
valueHumanName | HumanName | There are no (further) constraints on this element Data type | ||||
valueIdentifier | Identifier | There are no (further) constraints on this element Data type | ||||
valueMoney | Money | There are no (further) constraints on this element Data type | ||||
valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
valueQuantity | Quantity | There are no (further) constraints on this element Data type | ||||
valueRange | Range | There are no (further) constraints on this element Data type | ||||
valueRatio | Ratio | There are no (further) constraints on this element Data type | ||||
valueSampledData | SampledData | There are no (further) constraints on this element Data type | ||||
valueSignature | Signature | There are no (further) constraints on this element Data type | ||||
valueTiming | Timing | There are no (further) constraints on this element Data type | ||||
valueContactDetail | ContactDetail | There are no (further) constraints on this element Data type | ||||
valueContributor | Contributor | There are no (further) constraints on this element Data type | ||||
valueDataRequirement | DataRequirement | There are no (further) constraints on this element Data type | ||||
valueExpression | Expression | There are no (further) constraints on this element Data type | ||||
valueParameterDefinition | ParameterDefinition | There are no (further) constraints on this element Data type | ||||
valueRelatedArtifact | RelatedArtifact | There are no (further) constraints on this element Data type | ||||
valueTriggerDefinition | TriggerDefinition | There are no (further) constraints on this element Data type | ||||
valueUsageContext | UsageContext | There are no (further) constraints on this element Data type | ||||
valueDosage | Dosage | There are no (further) constraints on this element Data type | ||||
valueMeta | Meta | There are no (further) constraints on this element Data type | ||||
valueReference | Reference() | There are no (further) constraints on this element Data type | ||||
resource | Σ C | 0..1 | Resource | There are no (further) constraints on this element Element idParameters.parameter:image-binary.part.resourceShort description If parameter is a whole resource DefinitionIf the parameter is a whole resource. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods. The cardinality or value of this element may be affected by these constraints: inv-1 | ||
part | Σ | 0..* | see (parameter) | There are no (further) constraints on this element Element idParameters.parameter:image-binary.part.partShort description Named part of a multi-part parameter DefinitionA named part of a multi-part parameter. Only one level of nested parameters is allowed.
| ||
mri-image | S Σ C | 1..1 | BackboneElement | There are no (further) constraints on this element Element idParameters.parameter:mri-imageShort description Operation Parameter DefinitionA parameter passed to or received from the operation.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idParameters.parameter:mri-image.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | S C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter:mri-image.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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. Unordered, Open, by url(Value) Constraints
| ||
parameterQueryExtension | S C | 0..1 | Extension(Complex) | There are no (further) constraints on this element Element idParameters.parameter:mri-image.extension:parameterQueryExtensionShort description Service Input Parameter Query Extension Alternate namesextensions, user content DefinitionExtension to document how to get the value for a certain parameter. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttp://omi.de/fhir/registry/StructureDefinition/input-parameter-query-extension ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter:mri-image.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
name | S Σ | 1..1 | stringPattern | Element idParameters.parameter:mri-image.nameShort description Name from the definition DefinitionThe name of the parameter (reference to the operation definition).
mri-image | ||
value[x] | S Σ C | 0..1 | There are no (further) constraints on this element Element idParameters.parameter:mri-image.value[x]Short description If parameter is a data type DefinitionIf the parameter is a data type. The cardinality or value of this element may be affected by these constraints: inv-1 Constraints
| |||
valueBase64Binary | base64Binary | There are no (further) constraints on this element Data type | ||||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||||
valueCanonical | canonical() | There are no (further) constraints on this element Data type | ||||
valueCode | code | There are no (further) constraints on this element Data type | ||||
valueDate | date | There are no (further) constraints on this element Data type | ||||
valueDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
valueDecimal | decimal | There are no (further) constraints on this element Data type | ||||
valueId | id | There are no (further) constraints on this element Data type | ||||
valueInstant | instant | There are no (further) constraints on this element Data type | ||||
valueInteger | integer | There are no (further) constraints on this element Data type | ||||
valueMarkdown | markdown | There are no (further) constraints on this element Data type | ||||
valueOid | oid | There are no (further) constraints on this element Data type | ||||
valuePositiveInt | positiveInt | There are no (further) constraints on this element Data type | ||||
valueString | string | There are no (further) constraints on this element Data type | ||||
valueTime | time | There are no (further) constraints on this element Data type | ||||
valueUnsignedInt | unsignedInt | There are no (further) constraints on this element Data type | ||||
valueUri | uri | There are no (further) constraints on this element Data type | ||||
valueUrl | url | There are no (further) constraints on this element Data type | ||||
valueUuid | uuid | There are no (further) constraints on this element Data type | ||||
valueAddress | Address | There are no (further) constraints on this element Data type | ||||
valueAge | Age | There are no (further) constraints on this element Data type | ||||
valueAnnotation | Annotation | There are no (further) constraints on this element Data type | ||||
valueAttachment | Attachment | There are no (further) constraints on this element Data type | ||||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
valueCoding | Coding | There are no (further) constraints on this element Data type | ||||
valueContactPoint | ContactPoint | There are no (further) constraints on this element Data type | ||||
valueCount | Count | There are no (further) constraints on this element Data type | ||||
valueDistance | Distance | There are no (further) constraints on this element Data type | ||||
valueDuration | Duration | There are no (further) constraints on this element Data type | ||||
valueHumanName | HumanName | There are no (further) constraints on this element Data type | ||||
valueIdentifier | Identifier | There are no (further) constraints on this element Data type | ||||
valueMoney | Money | There are no (further) constraints on this element Data type | ||||
valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
valueQuantity | Quantity | There are no (further) constraints on this element Data type | ||||
valueRange | Range | There are no (further) constraints on this element Data type | ||||
valueRatio | Ratio | There are no (further) constraints on this element Data type | ||||
valueSampledData | SampledData | There are no (further) constraints on this element Data type | ||||
valueSignature | Signature | There are no (further) constraints on this element Data type | ||||
valueTiming | Timing | There are no (further) constraints on this element Data type | ||||
valueContactDetail | ContactDetail | There are no (further) constraints on this element Data type | ||||
valueContributor | Contributor | There are no (further) constraints on this element Data type | ||||
valueDataRequirement | DataRequirement | There are no (further) constraints on this element Data type | ||||
valueExpression | Expression | There are no (further) constraints on this element Data type | ||||
valueParameterDefinition | ParameterDefinition | There are no (further) constraints on this element Data type | ||||
valueRelatedArtifact | RelatedArtifact | There are no (further) constraints on this element Data type | ||||
valueTriggerDefinition | TriggerDefinition | There are no (further) constraints on this element Data type | ||||
valueUsageContext | UsageContext | There are no (further) constraints on this element Data type | ||||
valueDosage | Dosage | There are no (further) constraints on this element Data type | ||||
valueMeta | Meta | There are no (further) constraints on this element Data type | ||||
valueReference | Reference() | There are no (further) constraints on this element Data type | ||||
resource | S C | 1..1 | OMIDocumentReference | Element idParameters.parameter:mri-image.resourceShort description A reference to a document DefinitionA reference to a document of any kind for any purpose. Provides metadata about the document so that the document can be discovered and managed. The scope of a document is any seralized object with a mime-type, so includes formal patient centric documents (CDA), cliical notes, scanned paper, and non-patient specific documents like policy text. Usually, this is used for documents other than those defined by FHIR. The cardinality or value of this element may be affected by these constraints: inv-1 Constraints
| ||
part | S Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element idParameters.parameter:mri-image.partShort description Named part of a multi-part parameter DefinitionA named part of a multi-part parameter. Only one level of nested parameters is allowed.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idParameters.parameter:mri-image.part.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | S C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter:mri-image.part.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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. Unordered, Open, by url(Value) Constraints
| ||
parameterQueryExtension | S C | 0..1 | Extension(Complex) | There are no (further) constraints on this element Element idParameters.parameter:mri-image.part.extension:parameterQueryExtensionShort description Service Input Parameter Query Extension Alternate namesextensions, user content DefinitionExtension to document how to get the value for a certain parameter. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttp://omi.de/fhir/registry/StructureDefinition/input-parameter-query-extension ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter:mri-image.part.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
name | S Σ | 1..1 | string | There are no (further) constraints on this element Element idParameters.parameter:mri-image.part.nameShort description Name from the definition DefinitionThe name of the parameter (reference to the operation definition).
| ||
value[x] | S Σ C | 0..1 | There are no (further) constraints on this element Element idParameters.parameter:mri-image.part.value[x]Short description If parameter is a data type DefinitionIf the parameter is a data type. The cardinality or value of this element may be affected by these constraints: inv-1 Constraints
| |||
valueBase64Binary | base64Binary | There are no (further) constraints on this element Data type | ||||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||||
valueCanonical | canonical() | There are no (further) constraints on this element Data type | ||||
valueCode | code | There are no (further) constraints on this element Data type | ||||
valueDate | date | There are no (further) constraints on this element Data type | ||||
valueDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
valueDecimal | decimal | There are no (further) constraints on this element Data type | ||||
valueId | id | There are no (further) constraints on this element Data type | ||||
valueInstant | instant | There are no (further) constraints on this element Data type | ||||
valueInteger | integer | There are no (further) constraints on this element Data type | ||||
valueMarkdown | markdown | There are no (further) constraints on this element Data type | ||||
valueOid | oid | There are no (further) constraints on this element Data type | ||||
valuePositiveInt | positiveInt | There are no (further) constraints on this element Data type | ||||
valueString | string | There are no (further) constraints on this element Data type | ||||
valueTime | time | There are no (further) constraints on this element Data type | ||||
valueUnsignedInt | unsignedInt | There are no (further) constraints on this element Data type | ||||
valueUri | uri | There are no (further) constraints on this element Data type | ||||
valueUrl | url | There are no (further) constraints on this element Data type | ||||
valueUuid | uuid | There are no (further) constraints on this element Data type | ||||
valueAddress | Address | There are no (further) constraints on this element Data type | ||||
valueAge | Age | There are no (further) constraints on this element Data type | ||||
valueAnnotation | Annotation | There are no (further) constraints on this element Data type | ||||
valueAttachment | Attachment | There are no (further) constraints on this element Data type | ||||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
valueCoding | Coding | There are no (further) constraints on this element Data type | ||||
valueContactPoint | ContactPoint | There are no (further) constraints on this element Data type | ||||
valueCount | Count | There are no (further) constraints on this element Data type | ||||
valueDistance | Distance | There are no (further) constraints on this element Data type | ||||
valueDuration | Duration | There are no (further) constraints on this element Data type | ||||
valueHumanName | HumanName | There are no (further) constraints on this element Data type | ||||
valueIdentifier | Identifier | There are no (further) constraints on this element Data type | ||||
valueMoney | Money | There are no (further) constraints on this element Data type | ||||
valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
valueQuantity | Quantity | There are no (further) constraints on this element Data type | ||||
valueRange | Range | There are no (further) constraints on this element Data type | ||||
valueRatio | Ratio | There are no (further) constraints on this element Data type | ||||
valueSampledData | SampledData | There are no (further) constraints on this element Data type | ||||
valueSignature | Signature | There are no (further) constraints on this element Data type | ||||
valueTiming | Timing | There are no (further) constraints on this element Data type | ||||
valueContactDetail | ContactDetail | There are no (further) constraints on this element Data type | ||||
valueContributor | Contributor | There are no (further) constraints on this element Data type | ||||
valueDataRequirement | DataRequirement | There are no (further) constraints on this element Data type | ||||
valueExpression | Expression | There are no (further) constraints on this element Data type | ||||
valueParameterDefinition | ParameterDefinition | There are no (further) constraints on this element Data type | ||||
valueRelatedArtifact | RelatedArtifact | There are no (further) constraints on this element Data type | ||||
valueTriggerDefinition | TriggerDefinition | There are no (further) constraints on this element Data type | ||||
valueUsageContext | UsageContext | There are no (further) constraints on this element Data type | ||||
valueDosage | Dosage | There are no (further) constraints on this element Data type | ||||
valueMeta | Meta | There are no (further) constraints on this element Data type | ||||
valueReference | Reference() | There are no (further) constraints on this element Data type | ||||
resource | S Σ C | 0..1 | Resource | There are no (further) constraints on this element Element idParameters.parameter:mri-image.part.resourceShort description If parameter is a whole resource DefinitionIf the parameter is a whole resource. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods. The cardinality or value of this element may be affected by these constraints: inv-1 | ||
part | Σ | 0..* | see (parameter) | There are no (further) constraints on this element Element idParameters.parameter:mri-image.part.partShort description Named part of a multi-part parameter DefinitionA named part of a multi-part parameter. Only one level of nested parameters is allowed.
|
Example
Parameters |
id : GbmServiceInputParametersExample |
meta |
profile : http://omi.de/fhir/registry/StructureDefinition/GbmServiceInputParameters |
parameter |
name : mri-image |
resource |
id : WholeBodyMriDocumentReference |
meta |
profile : http://omi.de/fhir/registry/StructureDefinition/omi-document-reference |
content |
attachment |
url : https://omi.de/fhir/Binary/123 |
contentType : application/dicom |
status : current |
type |
coding |
code : 46358-8 |
system : http://loinc.org |
display : MR Whole body |
Output Parameters
Description
Outputs for the GBM algorithm include a annotated image in DICOM format. Additionally structured output could be provided.
Profiles
GbmServiceOutputParameters (Parameters) | OmiServiceOutputParameters | There are no (further) constraints on this element Element idParametersShort description Operation Request or Response DefinitionThis resource is a non-persisted resource used to pass information into and back from an operation. It has no other use, and there is no RESTful endpoint associated with it. The parameters that may be used are defined by the OperationDefinition resource.
| ||||
id | Σ | 0..1 | string | There are no (further) constraints on this element Element idParameters.idShort description Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. | ||
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idParameters.metaShort description Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
| ||
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idParameters.implicitRulesShort description A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
| ||
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idParameters.languageShort description Language of the resource content DefinitionThe base language in which the resource is written. 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). A human language.
| |||
parameter | S Σ C | 1..* | BackboneElement | There are no (further) constraints on this element Element idParameters.parameterShort description Operation Parameter DefinitionA parameter passed to or received from the operation. Unordered, Open, by name(Pattern) Constraints
| ||
(All Slices) | The requirements in this element apply to all slices | |||||
id | 0..1 | string | There are no (further) constraints on this element Element idParameters.parameter.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
name | S Σ | 1..1 | string | There are no (further) constraints on this element Element idParameters.parameter.nameShort description Name from the definition DefinitionThe name of the parameter (reference to the operation definition).
| ||
value[x] | S Σ C | 0..1 | There are no (further) constraints on this element Element idParameters.parameter.value[x]Short description If parameter is a data type DefinitionIf the parameter is a data type. The cardinality or value of this element may be affected by these constraints: inv-1 Constraints
| |||
valueBase64Binary | base64Binary | There are no (further) constraints on this element Data type | ||||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||||
valueCanonical | canonical() | There are no (further) constraints on this element Data type | ||||
valueCode | code | There are no (further) constraints on this element Data type | ||||
valueDate | date | There are no (further) constraints on this element Data type | ||||
valueDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
valueDecimal | decimal | There are no (further) constraints on this element Data type | ||||
valueId | id | There are no (further) constraints on this element Data type | ||||
valueInstant | instant | There are no (further) constraints on this element Data type | ||||
valueInteger | integer | There are no (further) constraints on this element Data type | ||||
valueMarkdown | markdown | There are no (further) constraints on this element Data type | ||||
valueOid | oid | There are no (further) constraints on this element Data type | ||||
valuePositiveInt | positiveInt | There are no (further) constraints on this element Data type | ||||
valueString | string | There are no (further) constraints on this element Data type | ||||
valueTime | time | There are no (further) constraints on this element Data type | ||||
valueUnsignedInt | unsignedInt | There are no (further) constraints on this element Data type | ||||
valueUri | uri | There are no (further) constraints on this element Data type | ||||
valueUrl | url | There are no (further) constraints on this element Data type | ||||
valueUuid | uuid | There are no (further) constraints on this element Data type | ||||
valueAddress | Address | There are no (further) constraints on this element Data type | ||||
valueAge | Age | There are no (further) constraints on this element Data type | ||||
valueAnnotation | Annotation | There are no (further) constraints on this element Data type | ||||
valueAttachment | Attachment | There are no (further) constraints on this element Data type | ||||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
valueCoding | Coding | There are no (further) constraints on this element Data type | ||||
valueContactPoint | ContactPoint | There are no (further) constraints on this element Data type | ||||
valueCount | Count | There are no (further) constraints on this element Data type | ||||
valueDistance | Distance | There are no (further) constraints on this element Data type | ||||
valueDuration | Duration | There are no (further) constraints on this element Data type | ||||
valueHumanName | HumanName | There are no (further) constraints on this element Data type | ||||
valueIdentifier | Identifier | There are no (further) constraints on this element Data type | ||||
valueMoney | Money | There are no (further) constraints on this element Data type | ||||
valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
valueQuantity | Quantity | There are no (further) constraints on this element Data type | ||||
valueRange | Range | There are no (further) constraints on this element Data type | ||||
valueRatio | Ratio | There are no (further) constraints on this element Data type | ||||
valueSampledData | SampledData | There are no (further) constraints on this element Data type | ||||
valueSignature | Signature | There are no (further) constraints on this element Data type | ||||
valueTiming | Timing | There are no (further) constraints on this element Data type | ||||
valueContactDetail | ContactDetail | There are no (further) constraints on this element Data type | ||||
valueContributor | Contributor | There are no (further) constraints on this element Data type | ||||
valueDataRequirement | DataRequirement | There are no (further) constraints on this element Data type | ||||
valueExpression | Expression | There are no (further) constraints on this element Data type | ||||
valueParameterDefinition | ParameterDefinition | There are no (further) constraints on this element Data type | ||||
valueRelatedArtifact | RelatedArtifact | There are no (further) constraints on this element Data type | ||||
valueTriggerDefinition | TriggerDefinition | There are no (further) constraints on this element Data type | ||||
valueUsageContext | UsageContext | There are no (further) constraints on this element Data type | ||||
valueDosage | Dosage | There are no (further) constraints on this element Data type | ||||
valueMeta | Meta | There are no (further) constraints on this element Data type | ||||
valueReference | Reference() | There are no (further) constraints on this element Data type | ||||
resource | S Σ C | 0..1 | Resource | There are no (further) constraints on this element Element idParameters.parameter.resourceShort description If parameter is a whole resource DefinitionIf the parameter is a whole resource. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods. The cardinality or value of this element may be affected by these constraints: inv-1 | ||
part | S Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element idParameters.parameter.partShort description Named part of a multi-part parameter DefinitionA named part of a multi-part parameter. Only one level of nested parameters is allowed.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idParameters.parameter.part.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter.part.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter.part.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
name | S Σ | 1..1 | string | There are no (further) constraints on this element Element idParameters.parameter.part.nameShort description Name from the definition DefinitionThe name of the parameter (reference to the operation definition).
| ||
value[x] | S Σ C | 0..1 | There are no (further) constraints on this element Element idParameters.parameter.part.value[x]Short description If parameter is a data type DefinitionIf the parameter is a data type. The cardinality or value of this element may be affected by these constraints: inv-1 Constraints
| |||
valueBase64Binary | base64Binary | There are no (further) constraints on this element Data type | ||||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||||
valueCanonical | canonical() | There are no (further) constraints on this element Data type | ||||
valueCode | code | There are no (further) constraints on this element Data type | ||||
valueDate | date | There are no (further) constraints on this element Data type | ||||
valueDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
valueDecimal | decimal | There are no (further) constraints on this element Data type | ||||
valueId | id | There are no (further) constraints on this element Data type | ||||
valueInstant | instant | There are no (further) constraints on this element Data type | ||||
valueInteger | integer | There are no (further) constraints on this element Data type | ||||
valueMarkdown | markdown | There are no (further) constraints on this element Data type | ||||
valueOid | oid | There are no (further) constraints on this element Data type | ||||
valuePositiveInt | positiveInt | There are no (further) constraints on this element Data type | ||||
valueString | string | There are no (further) constraints on this element Data type | ||||
valueTime | time | There are no (further) constraints on this element Data type | ||||
valueUnsignedInt | unsignedInt | There are no (further) constraints on this element Data type | ||||
valueUri | uri | There are no (further) constraints on this element Data type | ||||
valueUrl | url | There are no (further) constraints on this element Data type | ||||
valueUuid | uuid | There are no (further) constraints on this element Data type | ||||
valueAddress | Address | There are no (further) constraints on this element Data type | ||||
valueAge | Age | There are no (further) constraints on this element Data type | ||||
valueAnnotation | Annotation | There are no (further) constraints on this element Data type | ||||
valueAttachment | Attachment | There are no (further) constraints on this element Data type | ||||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
valueCoding | Coding | There are no (further) constraints on this element Data type | ||||
valueContactPoint | ContactPoint | There are no (further) constraints on this element Data type | ||||
valueCount | Count | There are no (further) constraints on this element Data type | ||||
valueDistance | Distance | There are no (further) constraints on this element Data type | ||||
valueDuration | Duration | There are no (further) constraints on this element Data type | ||||
valueHumanName | HumanName | There are no (further) constraints on this element Data type | ||||
valueIdentifier | Identifier | There are no (further) constraints on this element Data type | ||||
valueMoney | Money | There are no (further) constraints on this element Data type | ||||
valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
valueQuantity | Quantity | There are no (further) constraints on this element Data type | ||||
valueRange | Range | There are no (further) constraints on this element Data type | ||||
valueRatio | Ratio | There are no (further) constraints on this element Data type | ||||
valueSampledData | SampledData | There are no (further) constraints on this element Data type | ||||
valueSignature | Signature | There are no (further) constraints on this element Data type | ||||
valueTiming | Timing | There are no (further) constraints on this element Data type | ||||
valueContactDetail | ContactDetail | There are no (further) constraints on this element Data type | ||||
valueContributor | Contributor | There are no (further) constraints on this element Data type | ||||
valueDataRequirement | DataRequirement | There are no (further) constraints on this element Data type | ||||
valueExpression | Expression | There are no (further) constraints on this element Data type | ||||
valueParameterDefinition | ParameterDefinition | There are no (further) constraints on this element Data type | ||||
valueRelatedArtifact | RelatedArtifact | There are no (further) constraints on this element Data type | ||||
valueTriggerDefinition | TriggerDefinition | There are no (further) constraints on this element Data type | ||||
valueUsageContext | UsageContext | There are no (further) constraints on this element Data type | ||||
valueDosage | Dosage | There are no (further) constraints on this element Data type | ||||
valueMeta | Meta | There are no (further) constraints on this element Data type | ||||
valueReference | Reference() | There are no (further) constraints on this element Data type | ||||
resource | S Σ C | 0..1 | Resource | There are no (further) constraints on this element Element idParameters.parameter.part.resourceShort description If parameter is a whole resource DefinitionIf the parameter is a whole resource. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods. The cardinality or value of this element may be affected by these constraints: inv-1 | ||
part | Σ | 0..* | see (parameter) | There are no (further) constraints on this element Element idParameters.parameter.part.partShort description Named part of a multi-part parameter DefinitionA named part of a multi-part parameter. Only one level of nested parameters is allowed.
| ||
pdfReport | S Σ C | 0..1 | BackboneElement | There are no (further) constraints on this element Element idParameters.parameter:pdfReportShort description Operation Parameter DefinitionA parameter passed to or received from the operation.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idParameters.parameter:pdfReport.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter:pdfReport.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter:pdfReport.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
name | Σ | 1..1 | stringPattern | There are no (further) constraints on this element Element idParameters.parameter:pdfReport.nameShort description Name from the definition DefinitionThe name of the parameter (reference to the operation definition).
pdfReport | ||
value[x] | Σ C | 0..1 | There are no (further) constraints on this element Element idParameters.parameter:pdfReport.value[x]Short description If parameter is a data type DefinitionIf the parameter is a data type. The cardinality or value of this element may be affected by these constraints: inv-1 Constraints
| |||
valueBase64Binary | base64Binary | There are no (further) constraints on this element Data type | ||||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||||
valueCanonical | canonical() | There are no (further) constraints on this element Data type | ||||
valueCode | code | There are no (further) constraints on this element Data type | ||||
valueDate | date | There are no (further) constraints on this element Data type | ||||
valueDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
valueDecimal | decimal | There are no (further) constraints on this element Data type | ||||
valueId | id | There are no (further) constraints on this element Data type | ||||
valueInstant | instant | There are no (further) constraints on this element Data type | ||||
valueInteger | integer | There are no (further) constraints on this element Data type | ||||
valueMarkdown | markdown | There are no (further) constraints on this element Data type | ||||
valueOid | oid | There are no (further) constraints on this element Data type | ||||
valuePositiveInt | positiveInt | There are no (further) constraints on this element Data type | ||||
valueString | string | There are no (further) constraints on this element Data type | ||||
valueTime | time | There are no (further) constraints on this element Data type | ||||
valueUnsignedInt | unsignedInt | There are no (further) constraints on this element Data type | ||||
valueUri | uri | There are no (further) constraints on this element Data type | ||||
valueUrl | url | There are no (further) constraints on this element Data type | ||||
valueUuid | uuid | There are no (further) constraints on this element Data type | ||||
valueAddress | Address | There are no (further) constraints on this element Data type | ||||
valueAge | Age | There are no (further) constraints on this element Data type | ||||
valueAnnotation | Annotation | There are no (further) constraints on this element Data type | ||||
valueAttachment | Attachment | There are no (further) constraints on this element Data type | ||||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
valueCoding | Coding | There are no (further) constraints on this element Data type | ||||
valueContactPoint | ContactPoint | There are no (further) constraints on this element Data type | ||||
valueCount | Count | There are no (further) constraints on this element Data type | ||||
valueDistance | Distance | There are no (further) constraints on this element Data type | ||||
valueDuration | Duration | There are no (further) constraints on this element Data type | ||||
valueHumanName | HumanName | There are no (further) constraints on this element Data type | ||||
valueIdentifier | Identifier | There are no (further) constraints on this element Data type | ||||
valueMoney | Money | There are no (further) constraints on this element Data type | ||||
valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
valueQuantity | Quantity | There are no (further) constraints on this element Data type | ||||
valueRange | Range | There are no (further) constraints on this element Data type | ||||
valueRatio | Ratio | There are no (further) constraints on this element Data type | ||||
valueSampledData | SampledData | There are no (further) constraints on this element Data type | ||||
valueSignature | Signature | There are no (further) constraints on this element Data type | ||||
valueTiming | Timing | There are no (further) constraints on this element Data type | ||||
valueContactDetail | ContactDetail | There are no (further) constraints on this element Data type | ||||
valueContributor | Contributor | There are no (further) constraints on this element Data type | ||||
valueDataRequirement | DataRequirement | There are no (further) constraints on this element Data type | ||||
valueExpression | Expression | There are no (further) constraints on this element Data type | ||||
valueParameterDefinition | ParameterDefinition | There are no (further) constraints on this element Data type | ||||
valueRelatedArtifact | RelatedArtifact | There are no (further) constraints on this element Data type | ||||
valueTriggerDefinition | TriggerDefinition | There are no (further) constraints on this element Data type | ||||
valueUsageContext | UsageContext | There are no (further) constraints on this element Data type | ||||
valueDosage | Dosage | There are no (further) constraints on this element Data type | ||||
valueMeta | Meta | There are no (further) constraints on this element Data type | ||||
valueReference | Reference() | There are no (further) constraints on this element Data type | ||||
resource | C | 1..1 | OMIDocumentReference | There are no (further) constraints on this element Element idParameters.parameter:pdfReport.resourceShort description A reference to a document DefinitionA reference to a document of any kind for any purpose. Provides metadata about the document so that the document can be discovered and managed. The scope of a document is any seralized object with a mime-type, so includes formal patient centric documents (CDA), cliical notes, scanned paper, and non-patient specific documents like policy text. Usually, this is used for documents other than those defined by FHIR. The cardinality or value of this element may be affected by these constraints: inv-1 Constraints
| ||
part | Σ | 0..* | see (parameter) | There are no (further) constraints on this element Element idParameters.parameter:pdfReport.partShort description Named part of a multi-part parameter DefinitionA named part of a multi-part parameter. Only one level of nested parameters is allowed.
| ||
image | S Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idParameters.parameter:imageShort description Operation Parameter DefinitionA parameter passed to or received from the operation.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idParameters.parameter:image.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter:image.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter:image.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
name | Σ | 1..1 | stringPattern | There are no (further) constraints on this element Element idParameters.parameter:image.nameShort description Name from the definition DefinitionThe name of the parameter (reference to the operation definition).
image | ||
value[x] | Σ C | 0..1 | There are no (further) constraints on this element Element idParameters.parameter:image.value[x]Short description If parameter is a data type DefinitionIf the parameter is a data type. The cardinality or value of this element may be affected by these constraints: inv-1 Constraints
| |||
valueBase64Binary | base64Binary | There are no (further) constraints on this element Data type | ||||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||||
valueCanonical | canonical() | There are no (further) constraints on this element Data type | ||||
valueCode | code | There are no (further) constraints on this element Data type | ||||
valueDate | date | There are no (further) constraints on this element Data type | ||||
valueDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
valueDecimal | decimal | There are no (further) constraints on this element Data type | ||||
valueId | id | There are no (further) constraints on this element Data type | ||||
valueInstant | instant | There are no (further) constraints on this element Data type | ||||
valueInteger | integer | There are no (further) constraints on this element Data type | ||||
valueMarkdown | markdown | There are no (further) constraints on this element Data type | ||||
valueOid | oid | There are no (further) constraints on this element Data type | ||||
valuePositiveInt | positiveInt | There are no (further) constraints on this element Data type | ||||
valueString | string | There are no (further) constraints on this element Data type | ||||
valueTime | time | There are no (further) constraints on this element Data type | ||||
valueUnsignedInt | unsignedInt | There are no (further) constraints on this element Data type | ||||
valueUri | uri | There are no (further) constraints on this element Data type | ||||
valueUrl | url | There are no (further) constraints on this element Data type | ||||
valueUuid | uuid | There are no (further) constraints on this element Data type | ||||
valueAddress | Address | There are no (further) constraints on this element Data type | ||||
valueAge | Age | There are no (further) constraints on this element Data type | ||||
valueAnnotation | Annotation | There are no (further) constraints on this element Data type | ||||
valueAttachment | Attachment | There are no (further) constraints on this element Data type | ||||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
valueCoding | Coding | There are no (further) constraints on this element Data type | ||||
valueContactPoint | ContactPoint | There are no (further) constraints on this element Data type | ||||
valueCount | Count | There are no (further) constraints on this element Data type | ||||
valueDistance | Distance | There are no (further) constraints on this element Data type | ||||
valueDuration | Duration | There are no (further) constraints on this element Data type | ||||
valueHumanName | HumanName | There are no (further) constraints on this element Data type | ||||
valueIdentifier | Identifier | There are no (further) constraints on this element Data type | ||||
valueMoney | Money | There are no (further) constraints on this element Data type | ||||
valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
valueQuantity | Quantity | There are no (further) constraints on this element Data type | ||||
valueRange | Range | There are no (further) constraints on this element Data type | ||||
valueRatio | Ratio | There are no (further) constraints on this element Data type | ||||
valueSampledData | SampledData | There are no (further) constraints on this element Data type | ||||
valueSignature | Signature | There are no (further) constraints on this element Data type | ||||
valueTiming | Timing | There are no (further) constraints on this element Data type | ||||
valueContactDetail | ContactDetail | There are no (further) constraints on this element Data type | ||||
valueContributor | Contributor | There are no (further) constraints on this element Data type | ||||
valueDataRequirement | DataRequirement | There are no (further) constraints on this element Data type | ||||
valueExpression | Expression | There are no (further) constraints on this element Data type | ||||
valueParameterDefinition | ParameterDefinition | There are no (further) constraints on this element Data type | ||||
valueRelatedArtifact | RelatedArtifact | There are no (further) constraints on this element Data type | ||||
valueTriggerDefinition | TriggerDefinition | There are no (further) constraints on this element Data type | ||||
valueUsageContext | UsageContext | There are no (further) constraints on this element Data type | ||||
valueDosage | Dosage | There are no (further) constraints on this element Data type | ||||
valueMeta | Meta | There are no (further) constraints on this element Data type | ||||
valueReference | Reference() | There are no (further) constraints on this element Data type | ||||
resource | C | 1..1 | OMIDocumentReference | There are no (further) constraints on this element Element idParameters.parameter:image.resourceShort description A reference to a document DefinitionA reference to a document of any kind for any purpose. Provides metadata about the document so that the document can be discovered and managed. The scope of a document is any seralized object with a mime-type, so includes formal patient centric documents (CDA), cliical notes, scanned paper, and non-patient specific documents like policy text. Usually, this is used for documents other than those defined by FHIR. The cardinality or value of this element may be affected by these constraints: inv-1 Constraints
| ||
part | Σ | 0..* | see (parameter) | There are no (further) constraints on this element Element idParameters.parameter:image.partShort description Named part of a multi-part parameter DefinitionA named part of a multi-part parameter. Only one level of nested parameters is allowed.
| ||
observations | S Σ C | 0..* | BackboneElement | There are no (further) constraints on this element Element idParameters.parameter:observationsShort description Operation Parameter DefinitionA parameter passed to or received from the operation.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idParameters.parameter:observations.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter:observations.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter:observations.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
name | Σ | 1..1 | stringPattern | There are no (further) constraints on this element Element idParameters.parameter:observations.nameShort description Name from the definition DefinitionThe name of the parameter (reference to the operation definition).
observations | ||
value[x] | Σ C | 0..1 | There are no (further) constraints on this element Element idParameters.parameter:observations.value[x]Short description If parameter is a data type DefinitionIf the parameter is a data type. The cardinality or value of this element may be affected by these constraints: inv-1 Constraints
| |||
valueBase64Binary | base64Binary | There are no (further) constraints on this element Data type | ||||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||||
valueCanonical | canonical() | There are no (further) constraints on this element Data type | ||||
valueCode | code | There are no (further) constraints on this element Data type | ||||
valueDate | date | There are no (further) constraints on this element Data type | ||||
valueDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
valueDecimal | decimal | There are no (further) constraints on this element Data type | ||||
valueId | id | There are no (further) constraints on this element Data type | ||||
valueInstant | instant | There are no (further) constraints on this element Data type | ||||
valueInteger | integer | There are no (further) constraints on this element Data type | ||||
valueMarkdown | markdown | There are no (further) constraints on this element Data type | ||||
valueOid | oid | There are no (further) constraints on this element Data type | ||||
valuePositiveInt | positiveInt | There are no (further) constraints on this element Data type | ||||
valueString | string | There are no (further) constraints on this element Data type | ||||
valueTime | time | There are no (further) constraints on this element Data type | ||||
valueUnsignedInt | unsignedInt | There are no (further) constraints on this element Data type | ||||
valueUri | uri | There are no (further) constraints on this element Data type | ||||
valueUrl | url | There are no (further) constraints on this element Data type | ||||
valueUuid | uuid | There are no (further) constraints on this element Data type | ||||
valueAddress | Address | There are no (further) constraints on this element Data type | ||||
valueAge | Age | There are no (further) constraints on this element Data type | ||||
valueAnnotation | Annotation | There are no (further) constraints on this element Data type | ||||
valueAttachment | Attachment | There are no (further) constraints on this element Data type | ||||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
valueCoding | Coding | There are no (further) constraints on this element Data type | ||||
valueContactPoint | ContactPoint | There are no (further) constraints on this element Data type | ||||
valueCount | Count | There are no (further) constraints on this element Data type | ||||
valueDistance | Distance | There are no (further) constraints on this element Data type | ||||
valueDuration | Duration | There are no (further) constraints on this element Data type | ||||
valueHumanName | HumanName | There are no (further) constraints on this element Data type | ||||
valueIdentifier | Identifier | There are no (further) constraints on this element Data type | ||||
valueMoney | Money | There are no (further) constraints on this element Data type | ||||
valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
valueQuantity | Quantity | There are no (further) constraints on this element Data type | ||||
valueRange | Range | There are no (further) constraints on this element Data type | ||||
valueRatio | Ratio | There are no (further) constraints on this element Data type | ||||
valueSampledData | SampledData | There are no (further) constraints on this element Data type | ||||
valueSignature | Signature | There are no (further) constraints on this element Data type | ||||
valueTiming | Timing | There are no (further) constraints on this element Data type | ||||
valueContactDetail | ContactDetail | There are no (further) constraints on this element Data type | ||||
valueContributor | Contributor | There are no (further) constraints on this element Data type | ||||
valueDataRequirement | DataRequirement | There are no (further) constraints on this element Data type | ||||
valueExpression | Expression | There are no (further) constraints on this element Data type | ||||
valueParameterDefinition | ParameterDefinition | There are no (further) constraints on this element Data type | ||||
valueRelatedArtifact | RelatedArtifact | There are no (further) constraints on this element Data type | ||||
valueTriggerDefinition | TriggerDefinition | There are no (further) constraints on this element Data type | ||||
valueUsageContext | UsageContext | There are no (further) constraints on this element Data type | ||||
valueDosage | Dosage | There are no (further) constraints on this element Data type | ||||
valueMeta | Meta | There are no (further) constraints on this element Data type | ||||
valueReference | Reference() | There are no (further) constraints on this element Data type | ||||
resource | C | 1..1 | OmiOutputObservation | There are no (further) constraints on this element Element idParameters.parameter:observations.resourceShort description Measurements and simple assertions Alternate namesVital Signs, Measurement, Results, Tests DefinitionMeasurements and simple assertions made about a patient, device or other subject. 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 laboratory reports, etc. The cardinality or value of this element may be affected by these constraints: inv-1 Constraints
| ||
part | Σ | 0..* | see (parameter) | There are no (further) constraints on this element Element idParameters.parameter:observations.partShort description Named part of a multi-part parameter DefinitionA named part of a multi-part parameter. Only one level of nested parameters is allowed.
| ||
mri-image | S Σ C | 1..1 | BackboneElement | There are no (further) constraints on this element Element idParameters.parameter:mri-imageShort description Operation Parameter DefinitionA parameter passed to or received from the operation.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idParameters.parameter:mri-image.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter:mri-image.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter:mri-image.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
name | S Σ | 1..1 | stringPattern | Element idParameters.parameter:mri-image.nameShort description Name from the definition DefinitionThe name of the parameter (reference to the operation definition).
mri-image | ||
value[x] | S Σ C | 0..1 | There are no (further) constraints on this element Element idParameters.parameter:mri-image.value[x]Short description If parameter is a data type DefinitionIf the parameter is a data type. The cardinality or value of this element may be affected by these constraints: inv-1 Constraints
| |||
valueBase64Binary | base64Binary | There are no (further) constraints on this element Data type | ||||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||||
valueCanonical | canonical() | There are no (further) constraints on this element Data type | ||||
valueCode | code | There are no (further) constraints on this element Data type | ||||
valueDate | date | There are no (further) constraints on this element Data type | ||||
valueDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
valueDecimal | decimal | There are no (further) constraints on this element Data type | ||||
valueId | id | There are no (further) constraints on this element Data type | ||||
valueInstant | instant | There are no (further) constraints on this element Data type | ||||
valueInteger | integer | There are no (further) constraints on this element Data type | ||||
valueMarkdown | markdown | There are no (further) constraints on this element Data type | ||||
valueOid | oid | There are no (further) constraints on this element Data type | ||||
valuePositiveInt | positiveInt | There are no (further) constraints on this element Data type | ||||
valueString | string | There are no (further) constraints on this element Data type | ||||
valueTime | time | There are no (further) constraints on this element Data type | ||||
valueUnsignedInt | unsignedInt | There are no (further) constraints on this element Data type | ||||
valueUri | uri | There are no (further) constraints on this element Data type | ||||
valueUrl | url | There are no (further) constraints on this element Data type | ||||
valueUuid | uuid | There are no (further) constraints on this element Data type | ||||
valueAddress | Address | There are no (further) constraints on this element Data type | ||||
valueAge | Age | There are no (further) constraints on this element Data type | ||||
valueAnnotation | Annotation | There are no (further) constraints on this element Data type | ||||
valueAttachment | Attachment | There are no (further) constraints on this element Data type | ||||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
valueCoding | Coding | There are no (further) constraints on this element Data type | ||||
valueContactPoint | ContactPoint | There are no (further) constraints on this element Data type | ||||
valueCount | Count | There are no (further) constraints on this element Data type | ||||
valueDistance | Distance | There are no (further) constraints on this element Data type | ||||
valueDuration | Duration | There are no (further) constraints on this element Data type | ||||
valueHumanName | HumanName | There are no (further) constraints on this element Data type | ||||
valueIdentifier | Identifier | There are no (further) constraints on this element Data type | ||||
valueMoney | Money | There are no (further) constraints on this element Data type | ||||
valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
valueQuantity | Quantity | There are no (further) constraints on this element Data type | ||||
valueRange | Range | There are no (further) constraints on this element Data type | ||||
valueRatio | Ratio | There are no (further) constraints on this element Data type | ||||
valueSampledData | SampledData | There are no (further) constraints on this element Data type | ||||
valueSignature | Signature | There are no (further) constraints on this element Data type | ||||
valueTiming | Timing | There are no (further) constraints on this element Data type | ||||
valueContactDetail | ContactDetail | There are no (further) constraints on this element Data type | ||||
valueContributor | Contributor | There are no (further) constraints on this element Data type | ||||
valueDataRequirement | DataRequirement | There are no (further) constraints on this element Data type | ||||
valueExpression | Expression | There are no (further) constraints on this element Data type | ||||
valueParameterDefinition | ParameterDefinition | There are no (further) constraints on this element Data type | ||||
valueRelatedArtifact | RelatedArtifact | There are no (further) constraints on this element Data type | ||||
valueTriggerDefinition | TriggerDefinition | There are no (further) constraints on this element Data type | ||||
valueUsageContext | UsageContext | There are no (further) constraints on this element Data type | ||||
valueDosage | Dosage | There are no (further) constraints on this element Data type | ||||
valueMeta | Meta | There are no (further) constraints on this element Data type | ||||
valueReference | Reference() | There are no (further) constraints on this element Data type | ||||
resource | S C | 1..1 | OMIDocumentReference | Element idParameters.parameter:mri-image.resourceShort description A reference to a document DefinitionA reference to a document of any kind for any purpose. Provides metadata about the document so that the document can be discovered and managed. The scope of a document is any seralized object with a mime-type, so includes formal patient centric documents (CDA), cliical notes, scanned paper, and non-patient specific documents like policy text. Usually, this is used for documents other than those defined by FHIR. The cardinality or value of this element may be affected by these constraints: inv-1 Constraints
| ||
part | S Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element idParameters.parameter:mri-image.partShort description Named part of a multi-part parameter DefinitionA named part of a multi-part parameter. Only one level of nested parameters is allowed.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idParameters.parameter:mri-image.part.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter:mri-image.part.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idParameters.parameter:mri-image.part.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
name | S Σ | 1..1 | string | There are no (further) constraints on this element Element idParameters.parameter:mri-image.part.nameShort description Name from the definition DefinitionThe name of the parameter (reference to the operation definition).
| ||
value[x] | S Σ C | 0..1 | There are no (further) constraints on this element Element idParameters.parameter:mri-image.part.value[x]Short description If parameter is a data type DefinitionIf the parameter is a data type. The cardinality or value of this element may be affected by these constraints: inv-1 Constraints
| |||
valueBase64Binary | base64Binary | There are no (further) constraints on this element Data type | ||||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||||
valueCanonical | canonical() | There are no (further) constraints on this element Data type | ||||
valueCode | code | There are no (further) constraints on this element Data type | ||||
valueDate | date | There are no (further) constraints on this element Data type | ||||
valueDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
valueDecimal | decimal | There are no (further) constraints on this element Data type | ||||
valueId | id | There are no (further) constraints on this element Data type | ||||
valueInstant | instant | There are no (further) constraints on this element Data type | ||||
valueInteger | integer | There are no (further) constraints on this element Data type | ||||
valueMarkdown | markdown | There are no (further) constraints on this element Data type | ||||
valueOid | oid | There are no (further) constraints on this element Data type | ||||
valuePositiveInt | positiveInt | There are no (further) constraints on this element Data type | ||||
valueString | string | There are no (further) constraints on this element Data type | ||||
valueTime | time | There are no (further) constraints on this element Data type | ||||
valueUnsignedInt | unsignedInt | There are no (further) constraints on this element Data type | ||||
valueUri | uri | There are no (further) constraints on this element Data type | ||||
valueUrl | url | There are no (further) constraints on this element Data type | ||||
valueUuid | uuid | There are no (further) constraints on this element Data type | ||||
valueAddress | Address | There are no (further) constraints on this element Data type | ||||
valueAge | Age | There are no (further) constraints on this element Data type | ||||
valueAnnotation | Annotation | There are no (further) constraints on this element Data type | ||||
valueAttachment | Attachment | There are no (further) constraints on this element Data type | ||||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
valueCoding | Coding | There are no (further) constraints on this element Data type | ||||
valueContactPoint | ContactPoint | There are no (further) constraints on this element Data type | ||||
valueCount | Count | There are no (further) constraints on this element Data type | ||||
valueDistance | Distance | There are no (further) constraints on this element Data type | ||||
valueDuration | Duration | There are no (further) constraints on this element Data type | ||||
valueHumanName | HumanName | There are no (further) constraints on this element Data type | ||||
valueIdentifier | Identifier | There are no (further) constraints on this element Data type | ||||
valueMoney | Money | There are no (further) constraints on this element Data type | ||||
valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
valueQuantity | Quantity | There are no (further) constraints on this element Data type | ||||
valueRange | Range | There are no (further) constraints on this element Data type | ||||
valueRatio | Ratio | There are no (further) constraints on this element Data type | ||||
valueSampledData | SampledData | There are no (further) constraints on this element Data type | ||||
valueSignature | Signature | There are no (further) constraints on this element Data type | ||||
valueTiming | Timing | There are no (further) constraints on this element Data type | ||||
valueContactDetail | ContactDetail | There are no (further) constraints on this element Data type | ||||
valueContributor | Contributor | There are no (further) constraints on this element Data type | ||||
valueDataRequirement | DataRequirement | There are no (further) constraints on this element Data type | ||||
valueExpression | Expression | There are no (further) constraints on this element Data type | ||||
valueParameterDefinition | ParameterDefinition | There are no (further) constraints on this element Data type | ||||
valueRelatedArtifact | RelatedArtifact | There are no (further) constraints on this element Data type | ||||
valueTriggerDefinition | TriggerDefinition | There are no (further) constraints on this element Data type | ||||
valueUsageContext | UsageContext | There are no (further) constraints on this element Data type | ||||
valueDosage | Dosage | There are no (further) constraints on this element Data type | ||||
valueMeta | Meta | There are no (further) constraints on this element Data type | ||||
valueReference | Reference() | There are no (further) constraints on this element Data type | ||||
resource | S Σ C | 0..1 | Resource | There are no (further) constraints on this element Element idParameters.parameter:mri-image.part.resourceShort description If parameter is a whole resource DefinitionIf the parameter is a whole resource. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods. The cardinality or value of this element may be affected by these constraints: inv-1 | ||
part | Σ | 0..* | see (parameter) | There are no (further) constraints on this element Element idParameters.parameter:mri-image.part.partShort description Named part of a multi-part parameter DefinitionA named part of a multi-part parameter. Only one level of nested parameters is allowed.
|
Instance
Parameters |
id : GbmServiceOutputParametersExample |
meta |
profile : http://omi.de/fhir/registry/StructureDefinition/GbmServiceOutputParameters |
parameter |
name : mri-image |
resource |
id : WholeBodyMriDocumentReference |
meta |
profile : http://omi.de/fhir/registry/StructureDefinition/omi-document-reference |
content |
attachment |
url : https://omi.de/fhir/Binary/123 |
contentType : application/dicom |
status : current |
type |
coding |
code : 46358-8 |
system : http://loinc.org |
display : MR Whole body |
Structured Output
GbmSummaryOutputObservation (Observation) | C | OmiOutputObservation | There are no (further) constraints on this element Element idObservationShort description Measurements and simple assertions Alternate namesVital Signs, Measurement, Results, Tests DefinitionMeasurements and simple assertions made about a patient, device or other subject. 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 laboratory reports, etc.
| |||
id | Σ | 0..1 | string | There are no (further) constraints on this element Element idObservation.idShort description Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. | ||
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idObservation.metaShort description Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
| ||
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idObservation.implicitRulesShort description A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
| ||
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idObservation.languageShort description Language of the resource content DefinitionThe base language in which the resource is written. 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). A human language.
| |||
text | 0..1 | Narrative | There are no (further) constraints on this element Element idObservation.textShort description Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource and can 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. 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 information is added later.
| |||
contained | 0..* | Resource | There are no (further) constraints on this element Element idObservation.containedShort description Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese 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. 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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.modifierExtensionShort description Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay 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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
identifier | Σ | 0..* | Identifier | There are no (further) constraints on this element Element idObservation.identifierShort description Business Identifier for observation DefinitionA unique identifier assigned to this observation. Allows observations to be distinguished and referenced.
| ||
basedOn | Σ | 0..* | Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest) | There are no (further) constraints on this element Element idObservation.basedOnShort description Fulfills plan, proposal or order Alternate namesFulfills DefinitionA plan, proposal or order that is fulfilled in whole or in part by this event. For example, a MedicationRequest may require a patient to have laboratory test performed before it is dispensed. Allows tracing of authorization for the event and tracking whether proposals/recommendations were acted upon. Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest) Constraints
| ||
partOf | Σ | 0..* | Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy) | There are no (further) constraints on this element Element idObservation.partOfShort description Part of referenced event Alternate namesContainer DefinitionA larger event of which this particular Observation is a component or step. For example, an observation as part of a procedure. To link an Observation to an Encounter use Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy) Constraints
| ||
status | S Σ ?! | 1..1 | codeBinding | There are no (further) constraints on this element Element idObservation.statusShort description registered | preliminary | final | amended + DefinitionThe status of the result value. Need to track the status of individual results. Some results are finalized before the whole report is finalized. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. Codes providing the status of an observation.
| ||
category | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.categoryShort description Classification of type of observation DefinitionA code that classifies the general type of observation being made. Used for filtering what observations are retrieved and displayed. 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. Codes for high level observation categories. ObservationCategoryCodes (preferred) Constraints
| |||
code | S Σ | 1..1 | CodeableConcept | There are no (further) constraints on this element Element idObservation.codeShort description Type of observation (code / type) Alternate namesName DefinitionDescribes what was observed. Sometimes this is called the observation "name". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and, if present, component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
| ||
subject | Σ | 0..1 | Reference(Patient | Group | Device | Location) | There are no (further) constraints on this element Element idObservation.subjectShort description Who and/or what the observation is about DefinitionThe patient, or group of patients, location, or device this observation is about and into whose record the observation is placed. If the actual focus of the observation is different from the subject (or a sample of, part, or region of the subject), the Observations have no value if you don't know who or what they're about. 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. Reference(Patient | Group | Device | Location) Constraints
| ||
focus | Σ | 0..* | Reference(Resource) | There are no (further) constraints on this element Element idObservation.focusShort description What the observation is about, when it is not about the subject of record DefinitionThe actual focus of an observation when it is not the patient of record representing something or someone associated with the patient such as a spouse, parent, fetus, or donor. For example, fetus observations in a mother's record. The focus of an observation could also be an existing condition, an intervention, the subject's diet, another observation of the subject, or a body structure such as tumor or implanted device. An example use case would be using the Observation resource to capture whether the mother is trained to change her child's tracheostomy tube. In this example, the child is the patient of record and the mother is the focus. Typically, an observation is made about the subject - a patient, or group of patients, location, or device - and the distinction between the subject and what is directly measured for an observation is specified in the observation code itself ( e.g., "Blood Glucose") and does not need to be represented separately using this element. Use
| ||
encounter | Σ | 0..1 | Reference(Encounter) | There are no (further) constraints on this element Element idObservation.encounterShort description Healthcare event during which this observation is made Alternate namesContext DefinitionThe healthcare event (e.g. a patient and healthcare provider interaction) during which this observation is made. For some observations it may be important to know the link between an observation and a particular encounter. 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 but still be tied to the context of the encounter (e.g. pre-admission laboratory tests).
| ||
effective[x] | Σ | 0..1 | There are no (further) constraints on this element Element idObservation.effective[x]Short description Clinically relevant time/time-period for observation Alternate namesOccurrence DefinitionThe 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. Knowing when an observation was deemed true is important to its relevance as well as determining trends. At least a date should be present unless this observation is a historical report. For recording imprecise or "fuzzy" times (For example, a blood glucose measurement taken "after breakfast") use the Timing datatype which allow the measurement to be tied to regular life events.
| |||
effectiveDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
effectivePeriod | Period | There are no (further) constraints on this element Data type | ||||
effectiveTiming | Timing | There are no (further) constraints on this element Data type | ||||
effectiveInstant | instant | There are no (further) constraints on this element Data type | ||||
issued | Σ | 0..1 | instant | There are no (further) constraints on this element Element idObservation.issuedShort description Date/Time this version was made available DefinitionThe date and time this version of the observation was made available to providers, typically after the results have been reviewed and verified. For Observations that don’t require review and verification, it may be the same as the
| ||
performer | Σ | 0..* | Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson) | There are no (further) constraints on this element Element idObservation.performerShort description Who is responsible for the observation DefinitionWho was responsible for asserting the observed value as "true". May give a degree of confidence in the observation and also indicates where follow-up questions should be directed. Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson) Constraints
| ||
value[x] | S Σ C | 0..1 | There are no (further) constraints on this element Element idObservation.value[x]Short description Actual result DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. An observation may have; 1) a single value here, 2) both a value and a set of related or component values, or 3) only a set of related or component values. 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 additional guidance, see the Notes section below. The cardinality or value of this element may be affected by these constraints: obs-7 Constraints
| |||
valueQuantity | Quantity | There are no (further) constraints on this element Data type | ||||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
valueString | string | There are no (further) constraints on this element Data type | ||||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||||
valueInteger | integer | There are no (further) constraints on this element Data type | ||||
valueRange | Range | There are no (further) constraints on this element Data type | ||||
valueRatio | Ratio | There are no (further) constraints on this element Data type | ||||
valueSampledData | SampledData | There are no (further) constraints on this element Data type | ||||
valueTime | time | There are no (further) constraints on this element Data type | ||||
valueDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.dataAbsentReasonShort description Why the result is missing DefinitionProvides a reason why the expected value in the element Observation.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. 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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
note | 0..* | Annotation | There are no (further) constraints on this element Element idObservation.noteShort description Comments about the observation DefinitionComments about the observation or the results. Need to be able to provide free text additional information. May include general statements about the observation, or statements about significant, unexpected or unreliable results values, or information about its source when relevant to its interpretation.
| |||
bodySite | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idObservation.bodySiteShort description Observed body part DefinitionIndicates the site on the subject's body where the observation was made (i.e. the target site). 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 bodySite. Codes describing anatomical locations. May include laterality. SNOMEDCTBodyStructures (example) Constraints
| |||
method | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idObservation.methodShort description How it was done DefinitionIndicates the mechanism used to perform the observation. In some cases, method can impact results and is thus used for determining whether results can be compared or determining significance of results. Only used if not implicit in code for Observation.code. Methods for simple observations.
| |||
specimen | 0..1 | Reference(Specimen) | There are no (further) constraints on this element Element idObservation.specimenShort description Specimen used for this observation DefinitionThe specimen that was used when this observation was made. Should only be used if not implicit in code found in
| |||
device | 0..1 | Reference(Device | DeviceMetric) | There are no (further) constraints on this element Element idObservation.deviceShort description (Measurement) Device DefinitionThe device used to generate the observation data. Note that this is not meant to represent a device involved in the transmission of the result, e.g., a gateway. Such devices may be documented using the Provenance resource where relevant. Reference(Device | DeviceMetric) Constraints
| |||
referenceRange | C | 0..* | BackboneElement | There are no (further) constraints on this element Element idObservation.referenceRangeShort description Provides guide for interpretation DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. Multiple reference ranges are interpreted as an "OR". In other words, to represent two distinct target populations, two 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. 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 might 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.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.referenceRange.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.referenceRange.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.referenceRange.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
low | C | 0..1 | SimpleQuantity | There are no (further) constraints on this element Element idObservation.referenceRange.lowShort description Low Range, if relevant DefinitionThe 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). The cardinality or value of this element may be affected by these constraints: obs-3 Constraints
| ||
high | C | 0..1 | SimpleQuantity | There are no (further) constraints on this element Element idObservation.referenceRange.highShort description High Range, if relevant DefinitionThe 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). The cardinality or value of this element may be affected by these constraints: obs-3 Constraints
| ||
type | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.referenceRange.typeShort description Reference range qualifier DefinitionCodes to indicate the what part of the targeted reference population it applies to. For example, the normal or therapeutic range. Need to be able to say what kind of reference range this is - normal, recommended, therapeutic, etc., - for proper interpretation. This SHOULD be populated if there is more than one range. If this element is not present then the normal range is assumed. Code for the meaning of a reference range. ObservationReferenceRangeMeaningCodes (preferred) Constraints
| |||
appliesTo | 0..* | CodeableConcept | There are no (further) constraints on this element Element idObservation.referenceRange.appliesToShort description Reference range population DefinitionCodes 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. Multiple Need to be able to identify the target population for proper interpretation. This SHOULD be populated if there is more than one range. If this element is not present then the normal population is assumed. Codes identifying the population the reference range applies to. ObservationReferenceRangeAppliesToCodes (example) Constraints
| |||
age | 0..1 | Range | There are no (further) constraints on this element Element idObservation.referenceRange.ageShort description Applicable age range, if relevant DefinitionThe 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. Some analytes vary greatly over age.
| |||
text | 0..1 | string | There are no (further) constraints on this element Element idObservation.referenceRange.textShort description Text based reference range in an observation DefinitionText 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".
| |||
hasMember | Σ | 0..* | Reference(Observation | QuestionnaireResponse | MolecularSequence) | There are no (further) constraints on this element Element idObservation.hasMemberShort description Related resource that belongs to the Observation group DefinitionThis observation is a group observation (e.g. a battery, a panel of tests, a set of vital sign measurements) that includes the target as a member of the group. When using this element, an observation will typically have either a value or a set of related resources, although both may be present in some cases. For a discussion on the ways Observations can assembled in groups together, see Notes below. Note that a system may calculate results from QuestionnaireResponse into a final score and represent the score as an Observation. Reference(Observation | QuestionnaireResponse | MolecularSequence) Constraints
| ||
derivedFrom | Σ | 0..* | Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence) | There are no (further) constraints on this element Element idObservation.derivedFromShort description Related measurements the observation is made from DefinitionThe target resource that represents a measurement from which this observation value is derived. For example, a calculated anion gap or a fetal measurement based on an ultrasound image. All the reference choices that are listed in this element can represent clinical observations and other measurements that may be the source for a derived value. The most common reference will be another Observation. For a discussion on the ways Observations can assembled in groups together, see Notes below. Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence) Constraints
| ||
component | S Σ | 0..* | BackboneElement | Element idObservation.componentShort description Component results DefinitionSome 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. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below. Unordered, Open, by code(Pattern) Constraints
| ||
(All Slices) | The requirements in this element apply to all slices | |||||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | S Σ | 1..1 | CodeableConcept | There are no (further) constraints on this element Element idObservation.component.codeShort description Type of component observation (code / type) DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
| ||
value[x] | S Σ | 0..1 | There are no (further) constraints on this element Element idObservation.component.value[x]Short description Actual component result DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below.
| |||
valueQuantity | Quantity | There are no (further) constraints on this element Data type | ||||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
valueString | string | There are no (further) constraints on this element Data type | ||||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||||
valueInteger | integer | There are no (further) constraints on this element Data type | ||||
valueRange | Range | There are no (further) constraints on this element Data type | ||||
valueRatio | Ratio | There are no (further) constraints on this element Data type | ||||
valueSampledData | SampledData | There are no (further) constraints on this element Data type | ||||
valueTime | time | There are no (further) constraints on this element Data type | ||||
valueDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
total | S Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idObservation.component:totalShort description Component results DefinitionSome 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. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:total.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:total.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:total.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | S Σ | 1..1 | CodeableConceptPattern | Element idObservation.component:total.codeShort description Type of component observation (code / type) DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://snomed.info/sct", "code": "258261001", "display": "Tumor volume (observable entity)" } ] }Mappings
| ||
value[x] | S Σ | 1..1 | Pattern | Element idObservation.component:total.value[x]Short description Actual component result DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below.
{ "unit": "mL", "system": "http://unitsofmeasure.org", "code": "ml" }Mappings
| ||
valueQuantity | Quantity | Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:total.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:total.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:total.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
peritumoralEdema | S Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idObservation.component:peritumoralEdemaShort description Component results DefinitionSome 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. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:peritumoralEdema.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:peritumoralEdema.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:peritumoralEdema.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | S Σ | 1..1 | CodeableConceptPattern | Element idObservation.component:peritumoralEdema.codeShort description Type of component observation (code / type) DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://ncicb.nci.nih.gov/xml/owl/EVS/Thesaurus.owl", "code": "C121674", "display": "Peritumoral Edema" } ] }Mappings
| ||
value[x] | S Σ | 1..1 | Pattern | Element idObservation.component:peritumoralEdema.value[x]Short description Actual component result DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below.
{ "unit": "mL", "system": "http://unitsofmeasure.org", "code": "ml" }Mappings
| ||
valueQuantity | Quantity | Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:peritumoralEdema.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:peritumoralEdema.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:peritumoralEdema.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
enhancingTumor | S Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idObservation.component:enhancingTumorShort description Component results DefinitionSome 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. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:enhancingTumor.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:enhancingTumor.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:enhancingTumor.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | S Σ | 1..1 | CodeableConceptPattern | Element idObservation.component:enhancingTumor.codeShort description Type of component observation (code / type) DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://omi.de/fhir/registry/CodeSystem/TodoCodesCS", "code": "enhancingTumor", "display": "Enhancing Tumor" } ] }Mappings
| ||
value[x] | S Σ | 1..1 | Pattern | Element idObservation.component:enhancingTumor.value[x]Short description Actual component result DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below.
{ "unit": "mL", "system": "http://unitsofmeasure.org", "code": "ml" }Mappings
| ||
valueQuantity | Quantity | Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:enhancingTumor.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:enhancingTumor.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:enhancingTumor.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
necroticAndNonEnhancingTumor | S Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idObservation.component:necroticAndNonEnhancingTumorShort description Component results DefinitionSome 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. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:necroticAndNonEnhancingTumor.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:necroticAndNonEnhancingTumor.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:necroticAndNonEnhancingTumor.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | S Σ | 1..1 | CodeableConceptPattern | Element idObservation.component:necroticAndNonEnhancingTumor.codeShort description Type of component observation (code / type) DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://omi.de/fhir/registry/CodeSystem/TodoCodesCS", "code": "necroticAndNonEnhancingTumor", "display": "Necrotic and Non-Enhancing Tumor" } ] }Mappings
| ||
value[x] | S Σ | 1..1 | Pattern | Element idObservation.component:necroticAndNonEnhancingTumor.value[x]Short description Actual component result DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below.
{ "unit": "mL", "system": "http://unitsofmeasure.org", "code": "ml" }Mappings
| ||
valueQuantity | Quantity | Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:necroticAndNonEnhancingTumor.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:necroticAndNonEnhancingTumor.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:necroticAndNonEnhancingTumor.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
|
Variants / Biomarkers
GBMBiomarkerVariant (Observation) | C | Variant | There are no (further) constraints on this element Element idObservationShort description Variant Alternate namesVital Signs, Measurement, Results, Tests DefinitionMeasurements and simple assertions made about a patient, device or other subject. 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 laboratory reports, etc.
| |||
id | Σ | 0..1 | string | There are no (further) constraints on this element Element idObservation.idShort description Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. | ||
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idObservation.metaShort description Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
| ||
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idObservation.implicitRulesShort description A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
| ||
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idObservation.languageShort description Language of the resource content DefinitionThe base language in which the resource is written. 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). A human language.
| |||
text | 0..1 | Narrative | There are no (further) constraints on this element Element idObservation.textShort description Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource and can 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. 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 information is added later.
| |||
contained | 0..* | Resource | There are no (further) constraints on this element Element idObservation.containedShort description Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese 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. 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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.extensionShort description Extension DefinitionAn Extension Unordered, Open, by url(Value) Constraints
| ||
secondary-finding | C | 0..1 | Extension(CodeableConcept) | There are no (further) constraints on this element Element idObservation.extension:secondary-findingShort description Secondary findings are genetic test results that provide information about variants in a gene unrelated to the primary purpose for the testing, most often discovered when [Whole Exome Sequencing (WES)](https://en.wikipedia.org/wiki/Exome_sequencing) or [Whole Genome Sequencing (WGS)](https://en.wikipedia.org/wiki/Whole_genome_sequencing) is performed. This extension should be used to denote when a genetic finding is being shared as a secondary finding, and ideally refer to a corresponding guideline or policy statement. For more detail, please see: https://ghr.nlm.nih.gov/primer/testing/secondaryfindings DefinitionSecondary findings are genetic test results that provide information about variants in a gene unrelated to the primary purpose for the testing, most often discovered when Whole Exome Sequencing (WES) or Whole Genome Sequencing (WGS) is performed. This extension should be used to denote when a genetic finding is being shared as a secondary finding, and ideally refer to a corresponding guideline or policy statement. For more detail, please see: https://ghr.nlm.nih.gov/primer/testing/secondaryfindings. http://hl7.org/fhir/StructureDefinition/observation-secondaryFinding ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
body-structure | C | 0..1 | Extension(Reference(BodyStructure)) | There are no (further) constraints on this element Element idObservation.extension:body-structureShort description Target anatomic location or structure DefinitionRecord details about the anatomical location of a specimen or body part. This resource may be used when a coded concept does not provide the necessary detail needed for the use case. Extension(Reference(BodyStructure)) Extension URLhttp://hl7.org/fhir/StructureDefinition/bodySite ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
modifierExtension | ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.modifierExtensionShort description Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay 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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
identifier | Σ | 0..* | Identifier | There are no (further) constraints on this element Element idObservation.identifierShort description Business Identifier for observation DefinitionA unique identifier assigned to this observation. Allows observations to be distinguished and referenced.
| ||
basedOn | Σ | 0..* | Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest) | There are no (further) constraints on this element Element idObservation.basedOnShort description Fulfills plan, proposal or order Alternate namesFulfills DefinitionA plan, proposal or order that is fulfilled in whole or in part by this event. For example, a MedicationRequest may require a patient to have laboratory test performed before it is dispensed. Allows tracing of authorization for the event and tracking whether proposals/recommendations were acted upon. Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest) Constraints
| ||
partOf | Σ | 0..* | Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy) | There are no (further) constraints on this element Element idObservation.partOfShort description Part of referenced event Alternate namesContainer DefinitionA larger event of which this particular Observation is a component or step. For example, an observation as part of a procedure. To link an Observation to an Encounter use Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy) Constraints
| ||
status | Σ ?! | 1..1 | codeBinding | There are no (further) constraints on this element Element idObservation.statusShort description registered | preliminary | final | amended + DefinitionThe status of the result value. Need to track the status of individual results. Some results are finalized before the whole report is finalized. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. Codes providing the status of an observation.
| ||
category | 1..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.categoryShort description Classification of type of observation DefinitionA code that classifies the general type of observation being made. Used for filtering what observations are retrieved and displayed. 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. Unordered, Open, by coding(Value) Slice based on the category.code pattern BindingCodes for high level observation categories. ObservationCategoryCodes (preferred) Constraints
| |||
labCategory | 1..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.category:labCategoryShort description Classification of type of observation DefinitionA code that classifies the general type of observation being made. Used for filtering what observations are retrieved and displayed. 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. Codes for high level observation categories. ObservationCategoryCodes (preferred) Constraints
| |||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.category:labCategory.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.category:labCategory.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
| ||
coding | Σ | 1..* | CodingPattern | There are no (further) constraints on this element Element idObservation.category:labCategory.codingShort description Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. 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.
{ "system": "http://terminology.hl7.org/CodeSystem/observation-category", "code": "laboratory" }Mappings
| ||
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idObservation.category:labCategory.textShort description Plain text representation of the concept DefinitionA 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. 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. Very often the text is the same as a displayName of one of the codings.
| ||
code | Σ | 1..1 | CodeableConceptPattern | There are no (further) constraints on this element Element idObservation.codeShort description 69548-6 Alternate namesName DefinitionDescribes what was observed. Sometimes this is called the observation "name". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and, if present, component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://loinc.org", "code": "69548-6" } ] }Mappings
| ||
subject | Σ | 0..1 | Reference(Patient | Group | Device | Location) | There are no (further) constraints on this element Element idObservation.subjectShort description Who and/or what the observation is about DefinitionThe patient, or group of patients, location, or device this observation is about and into whose record the observation is placed. If the actual focus of the observation is different from the subject (or a sample of, part, or region of the subject), the Observations have no value if you don't know who or what they're about. 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. Reference(Patient | Group | Device | Location) Constraints
| ||
focus | Σ | 0..* | Reference(Resource) | There are no (further) constraints on this element Element idObservation.focusShort description What the observation is about, when it is not about the subject of record DefinitionThe actual focus of an observation when it is not the patient of record representing something or someone associated with the patient such as a spouse, parent, fetus, or donor. For example, fetus observations in a mother's record. The focus of an observation could also be an existing condition, an intervention, the subject's diet, another observation of the subject, or a body structure such as tumor or implanted device. An example use case would be using the Observation resource to capture whether the mother is trained to change her child's tracheostomy tube. In this example, the child is the patient of record and the mother is the focus. Typically, an observation is made about the subject - a patient, or group of patients, location, or device - and the distinction between the subject and what is directly measured for an observation is specified in the observation code itself ( e.g., "Blood Glucose") and does not need to be represented separately using this element. Use
| ||
encounter | Σ | 0..1 | Reference(Encounter) | There are no (further) constraints on this element Element idObservation.encounterShort description Healthcare event during which this observation is made Alternate namesContext DefinitionThe healthcare event (e.g. a patient and healthcare provider interaction) during which this observation is made. For some observations it may be important to know the link between an observation and a particular encounter. 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 but still be tied to the context of the encounter (e.g. pre-admission laboratory tests).
| ||
effective[x] | Σ | 0..1 | There are no (further) constraints on this element Element idObservation.effective[x]Short description Clinically relevant time/time-period for observation Alternate namesOccurrence DefinitionThe 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. Knowing when an observation was deemed true is important to its relevance as well as determining trends. At least a date should be present unless this observation is a historical report. For recording imprecise or "fuzzy" times (For example, a blood glucose measurement taken "after breakfast") use the Timing datatype which allow the measurement to be tied to regular life events.
| |||
effectiveDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
effectivePeriod | Period | There are no (further) constraints on this element Data type | ||||
effectiveTiming | Timing | There are no (further) constraints on this element Data type | ||||
effectiveInstant | instant | There are no (further) constraints on this element Data type | ||||
issued | Σ | 0..1 | instant | There are no (further) constraints on this element Element idObservation.issuedShort description Date/Time this version was made available DefinitionThe date and time this version of the observation was made available to providers, typically after the results have been reviewed and verified. For Observations that don’t require review and verification, it may be the same as the
| ||
performer | Σ | 0..* | Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson) | There are no (further) constraints on this element Element idObservation.performerShort description Who is responsible for the observation DefinitionWho was responsible for asserting the observed value as "true". May give a degree of confidence in the observation and also indicates where follow-up questions should be directed. Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson) Constraints
| ||
value[x] | Σ C | 0..1 | Element idObservation.value[x]Short description Actual result DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. An observation may have; 1) a single value here, 2) both a value and a set of related or component values, or 3) only a set of related or component values. 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 additional guidance, see the Notes section below. Unordered, Open, by $this(Type) ConditionsThe cardinality or value of this element may be affected by these constraints: obs-7 Constraints
| |||
valueCodeableConcept | Σ C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.value[x]:valueCodeableConceptShort description Indeterminate | No call | Present | Absent. DefinitionThe presence or absence of the variant described in the components. If not searching for specific variations and merely reporting what's found, the profile's value should be set to 'Present'. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. An observation may have; 1) a single value here, 2) both a value and a set of related or component values, or 3) only a set of related or component values. 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 additional guidance, see the Notes section below. http://loinc.org/vs/LL1971-2 (required) ConditionsThe cardinality or value of this element may be affected by these constraints: obs-7 Constraints
| ||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.dataAbsentReasonShort description Why the result is missing DefinitionProvides a reason why the expected value in the element Observation.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. 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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
note | 0..* | CodedAnnotation | There are no (further) constraints on this element Element idObservation.noteShort description Comments about the Observation that also contain a coded type DefinitionA text note which also contains information about who made the statement and when. Need to be able to provide free text additional information. Notes SHALL NOT contain information which can be captured in a structured way. May include general statements about the observation, or statements about significant, unexpected or unreliable results values, or information about its source when relevant to its interpretation. The CodedAnnotation data type, while not allowing for or intending to make the content computable, does allow the author to indicate the type of note. This does not replace the use of interpretation, value, or component values. One important note is that Annotation is a FHIR data type, this is NOT about annotations in the genomic context. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
bodySite | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idObservation.bodySiteShort description Observed body part DefinitionIndicates the site on the subject's body where the observation was made (i.e. the target site). 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 bodySite. Codes describing anatomical locations. May include laterality. SNOMEDCTBodyStructures (example) Constraints
| |||
method | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.methodShort description Sequencing | SNP array | PCR | Computational analysis | ... DefinitionIndicates the mechanism used to perform the observation. In some cases, method can impact results and is thus used for determining whether results can be compared or determining significance of results. Only used if not implicit in code for Observation.code. http://loinc.org/vs/LL4048-6 (extensible) Constraints
| |||
specimen | 0..1 | Reference(Specimen) | There are no (further) constraints on this element Element idObservation.specimenShort description Specimen used for this observation DefinitionThe specimen that was used when this observation was made. Should only be used if not implicit in code found in
| |||
device | 0..1 | Reference(Device | DeviceMetric) | There are no (further) constraints on this element Element idObservation.deviceShort description (Measurement) Device DefinitionThe device used to generate the observation data. Note that this is not meant to represent a device involved in the transmission of the result, e.g., a gateway. Such devices may be documented using the Provenance resource where relevant. Reference(Device | DeviceMetric) Constraints
| |||
referenceRange | C | 0..* | BackboneElement | There are no (further) constraints on this element Element idObservation.referenceRangeShort description Provides guide for interpretation DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. Multiple reference ranges are interpreted as an "OR". In other words, to represent two distinct target populations, two 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. 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 might 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.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.referenceRange.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.referenceRange.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.referenceRange.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
low | C | 0..1 | SimpleQuantity | There are no (further) constraints on this element Element idObservation.referenceRange.lowShort description Low Range, if relevant DefinitionThe 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). The cardinality or value of this element may be affected by these constraints: obs-3 Constraints
| ||
high | C | 0..1 | SimpleQuantity | There are no (further) constraints on this element Element idObservation.referenceRange.highShort description High Range, if relevant DefinitionThe 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). The cardinality or value of this element may be affected by these constraints: obs-3 Constraints
| ||
type | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.referenceRange.typeShort description Reference range qualifier DefinitionCodes to indicate the what part of the targeted reference population it applies to. For example, the normal or therapeutic range. Need to be able to say what kind of reference range this is - normal, recommended, therapeutic, etc., - for proper interpretation. This SHOULD be populated if there is more than one range. If this element is not present then the normal range is assumed. Code for the meaning of a reference range. ObservationReferenceRangeMeaningCodes (preferred) Constraints
| |||
appliesTo | 0..* | CodeableConcept | There are no (further) constraints on this element Element idObservation.referenceRange.appliesToShort description Reference range population DefinitionCodes 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. Multiple Need to be able to identify the target population for proper interpretation. This SHOULD be populated if there is more than one range. If this element is not present then the normal population is assumed. Codes identifying the population the reference range applies to. ObservationReferenceRangeAppliesToCodes (example) Constraints
| |||
age | 0..1 | Range | There are no (further) constraints on this element Element idObservation.referenceRange.ageShort description Applicable age range, if relevant DefinitionThe 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. Some analytes vary greatly over age.
| |||
text | 0..1 | string | There are no (further) constraints on this element Element idObservation.referenceRange.textShort description Text based reference range in an observation DefinitionText 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".
| |||
hasMember | Σ | 0..* | Reference(Observation | QuestionnaireResponse | MolecularSequence) | There are no (further) constraints on this element Element idObservation.hasMemberShort description Related resource that belongs to the Observation group DefinitionThis observation is a group observation (e.g. a battery, a panel of tests, a set of vital sign measurements) that includes the target as a member of the group. When using this element, an observation will typically have either a value or a set of related resources, although both may be present in some cases. For a discussion on the ways Observations can assembled in groups together, see Notes below. Note that a system may calculate results from QuestionnaireResponse into a final score and represent the score as an Observation. Reference(Observation | QuestionnaireResponse | MolecularSequence) Constraints
| ||
derivedFrom | Σ | 0..* | Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence) | There are no (further) constraints on this element Element idObservation.derivedFromShort description Related measurements the observation is made from DefinitionThe target resource that represents a measurement from which this observation value is derived. For example, a calculated anion gap or a fetal measurement based on an ultrasound image. All the reference choices that are listed in this element can represent clinical observations and other measurements that may be the source for a derived value. The most common reference will be another Observation. For a discussion on the ways Observations can assembled in groups together, see Notes below. Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence) Constraints
| ||
component | Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element idObservation.componentShort description Component results DefinitionSome 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. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below. Unordered, Open, by code(Pattern) Slice based on the component.code pattern Constraints
| ||
(All Slices) | The requirements in this element apply to all slices | |||||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConcept | There are no (further) constraints on this element Element idObservation.component.codeShort description Type of component observation (code / type) DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
| ||
value[x] | Σ | 0..1 | There are no (further) constraints on this element Element idObservation.component.value[x]Short description Actual component result DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below.
| |||
valueQuantity | Quantity | There are no (further) constraints on this element Data type | ||||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
valueString | string | There are no (further) constraints on this element Data type | ||||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||||
valueInteger | integer | There are no (further) constraints on this element Data type | ||||
valueRange | Range | There are no (further) constraints on this element Data type | ||||
valueRatio | Ratio | There are no (further) constraints on this element Data type | ||||
valueSampledData | SampledData | There are no (further) constraints on this element Data type | ||||
valueTime | time | There are no (further) constraints on this element Data type | ||||
valueDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
conclusion-string | Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idObservation.component:conclusion-stringShort description Clinical Conclusion DefinitionConcise and clinically contextualized summary conclusion (interpretation/impression) of the observation Need to be able to provide a conclusion that is not lost among the basic result data. An example would be the interpretative information, typically canned, about a variant identified in the patient.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:conclusion-string.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:conclusion-string.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:conclusion-string.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | There are no (further) constraints on this element Element idObservation.component:conclusion-string.codeShort description conclusion-string DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://hl7.org/fhir/uv/genomics-reporting/CodeSystem/tbd-codes-cs", "code": "conclusion-string" } ] }Mappings
| ||
value[x] | Σ | 0..1 | There are no (further) constraints on this element Element idObservation.component:conclusion-string.value[x]Short description Summary conclusion (interpretation/impression) DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below.
| |||
valueString | string | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:conclusion-string.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:conclusion-string.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:conclusion-string.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
gene-studied | Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element idObservation.component:gene-studiedShort description Gene Studied DefinitionThe gene(s) on which the variant is located. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:gene-studied.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:gene-studied.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:gene-studied.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | There are no (further) constraints on this element Element idObservation.component:gene-studied.codeShort description 48018-6 DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://loinc.org", "code": "48018-6" } ] }Mappings
| ||
value[x] | Σ | 1..1 | Binding | There are no (further) constraints on this element Element idObservation.component:gene-studied.value[x]Short description The HGNC gene symbol is to be used as display text and the HGNC gene ID used as the code. If no HGNC code issued for this gene yet, NCBI gene IDs SHALL be used. DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below.
| ||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:gene-studied.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:gene-studied.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:gene-studied.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
cytogenetic-location | Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element idObservation.component:cytogenetic-locationShort description Cytogenetic (Chromosome) Location DefinitionThe relevant chromosomal region. The combination of numbers and letters provide a genetic 'address'. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:cytogenetic-location.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:cytogenetic-location.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:cytogenetic-location.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | There are no (further) constraints on this element Element idObservation.component:cytogenetic-location.codeShort description 48001-2 DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://loinc.org", "code": "48001-2" } ] }Mappings
| ||
value[x] | Σ | 1..1 | There are no (further) constraints on this element Element idObservation.component:cytogenetic-location.value[x]Short description Example: 1q21.1 DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below.
| |||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:cytogenetic-location.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:cytogenetic-location.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:cytogenetic-location.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
reference-sequence-assembly | Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element idObservation.component:reference-sequence-assemblyShort description Human Reference Sequence Assembly DefinitionThe reference genome/assembly used in this analysis. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:reference-sequence-assembly.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:reference-sequence-assembly.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:reference-sequence-assembly.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | There are no (further) constraints on this element Element idObservation.component:reference-sequence-assembly.codeShort description 62374-4 DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://loinc.org", "code": "62374-4" } ] }Mappings
| ||
value[x] | Σ | 1..1 | Binding | There are no (further) constraints on this element Element idObservation.component:reference-sequence-assembly.value[x]Short description GRCh37 | GRCh38 | ... DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below. http://loinc.org/vs/LL1040-6 (extensible) Constraints
| ||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:reference-sequence-assembly.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:reference-sequence-assembly.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:reference-sequence-assembly.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
coding-hgvs | Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idObservation.component:coding-hgvsShort description Coding (cDNA) Change - cHGVS DefinitionDescription of the coding (cDNA) sequence change using a valid HGVS-formatted string. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:coding-hgvs.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:coding-hgvs.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:coding-hgvs.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | There are no (further) constraints on this element Element idObservation.component:coding-hgvs.codeShort description 48004-6 DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://loinc.org", "code": "48004-6" } ] }Mappings
| ||
value[x] | Σ | 1..1 | Binding | There are no (further) constraints on this element Element idObservation.component:coding-hgvs.value[x]Short description A valid HGVS-formatted 'c.' string, e.g. NM_005228.5:c.2369C>T. DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below.
| ||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:coding-hgvs.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:coding-hgvs.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:coding-hgvs.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
genomic-hgvs | Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idObservation.component:genomic-hgvsShort description Genomic (gDNA) Change - gHGVS DefinitionDescription of the genomic (gDNA) sequence change using a valid HGVS-formatted string. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:genomic-hgvs.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:genomic-hgvs.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:genomic-hgvs.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | There are no (further) constraints on this element Element idObservation.component:genomic-hgvs.codeShort description 81290-9 DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://loinc.org", "code": "81290-9" } ] }Mappings
| ||
value[x] | Σ | 1..1 | Binding | There are no (further) constraints on this element Element idObservation.component:genomic-hgvs.value[x]Short description A valid HGVS-formatted 'g.' string, e.g. NC_000016.9:g.2124200_2138612dup DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below.
| ||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:genomic-hgvs.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:genomic-hgvs.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:genomic-hgvs.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
cytogenomic-nomenclature | Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idObservation.component:cytogenomic-nomenclatureShort description Cytogenomic Nomenclature (ISCN) DefinitionFully describes a variant with a single code. Typically a large variant such as a mosaic, abnormal chromosome numbers, etc. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:cytogenomic-nomenclature.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:cytogenomic-nomenclature.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:cytogenomic-nomenclature.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | There are no (further) constraints on this element Element idObservation.component:cytogenomic-nomenclature.codeShort description 81291-7 DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://loinc.org", "code": "81291-7" } ] }Mappings
| ||
value[x] | Σ | 1..1 | There are no (further) constraints on this element Element idObservation.component:cytogenomic-nomenclature.value[x]Short description Actual component result DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below. Binding not yet defined
| |||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:cytogenomic-nomenclature.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:cytogenomic-nomenclature.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:cytogenomic-nomenclature.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
genomic-ref-seq | Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idObservation.component:genomic-ref-seqShort description Genomic Reference Sequence DefinitionID of the genomic reference sequence, which includes transcribed and non transcribed stretches 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:genomic-ref-seq.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:genomic-ref-seq.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:genomic-ref-seq.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | There are no (further) constraints on this element Element idObservation.component:genomic-ref-seq.codeShort description 48013-7 DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://loinc.org", "code": "48013-7" } ] }Mappings
| ||
value[x] | Σ | 1..1 | There are no (further) constraints on this element Element idObservation.component:genomic-ref-seq.value[x]Short description Versioned genomic reference sequence identifier DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below. Multiple bindings acceptable (NCBI or LRG)
| |||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:genomic-ref-seq.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:genomic-ref-seq.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:genomic-ref-seq.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
transcript-ref-seq | Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idObservation.component:transcript-ref-seqShort description Reference Transcript DefinitionNCBI's RefSeq ('NM_...'), Ensembl ('ENST...'), and LRG ('LRG...' plus 't1' to indicate transcript) 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:transcript-ref-seq.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:transcript-ref-seq.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:transcript-ref-seq.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | There are no (further) constraints on this element Element idObservation.component:transcript-ref-seq.codeShort description 51958-7 DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://loinc.org", "code": "51958-7" } ] }Mappings
| ||
value[x] | Σ | 1..1 | There are no (further) constraints on this element Element idObservation.component:transcript-ref-seq.value[x]Short description Versioned transcript reference sequence identifier DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below. Multiple bindings acceptable (NCBI or LRG)
| |||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:transcript-ref-seq.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:transcript-ref-seq.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:transcript-ref-seq.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
exact-start-end | Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idObservation.component:exact-start-endShort description Exact Start-End DefinitionThe exact integer-based genomic coordinates of the start and end of the variant region. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:exact-start-end.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:exact-start-end.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:exact-start-end.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | There are no (further) constraints on this element Element idObservation.component:exact-start-end.codeShort description 81254-5 DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://loinc.org", "code": "81254-5" } ] }Mappings
| ||
value[x] | Σ | 0..1 | There are no (further) constraints on this element Element idObservation.component:exact-start-end.value[x]Short description Range in question. 'High' can be omitted for single nucleotide variants. DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below.
| |||
valueRange | Range | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:exact-start-end.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:exact-start-end.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:exact-start-end.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
inner-start-end | Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idObservation.component:inner-start-endShort description Inner Start-End DefinitionThe genomic coordinates of the narrowest genomic range in which the variant might reside. Used when the exact boundaries of the variant are not clear. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:inner-start-end.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:inner-start-end.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:inner-start-end.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | There are no (further) constraints on this element Element idObservation.component:inner-start-end.codeShort description 81302-2 DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://loinc.org", "code": "81302-2" } ] }Mappings
| ||
value[x] | Σ | 0..1 | There are no (further) constraints on this element Element idObservation.component:inner-start-end.value[x]Short description Imprecise variant inner-bounding range DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below.
| |||
valueRange | Range | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:inner-start-end.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:inner-start-end.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:inner-start-end.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
outer-start-end | Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idObservation.component:outer-start-endShort description Outer Start-End DefinitionThe genomic coordinates of the widest genomic range in which the variant might reside. Used when the exact boundaries of the variant are not clear. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:outer-start-end.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:outer-start-end.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:outer-start-end.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | There are no (further) constraints on this element Element idObservation.component:outer-start-end.codeShort description 81301-4 DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://loinc.org", "code": "81301-4" } ] }Mappings
| ||
value[x] | Σ | 0..1 | There are no (further) constraints on this element Element idObservation.component:outer-start-end.value[x]Short description Imprecise variant outer-bounding range DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below.
| |||
valueRange | Range | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:outer-start-end.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:outer-start-end.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:outer-start-end.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
coordinate-system | Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idObservation.component:coordinate-systemShort description Coordinate System DefinitionThese are different ways of identifying nucleotides or amino acids within a sequence. In the 1-based system, the first unit of the polymer (e.g. the first nucleotide) is counted as number 1. In the 0-based system, the number 0 designates the location before the first nucleotide. Different databases and file types may use different systems. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:coordinate-system.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:coordinate-system.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:coordinate-system.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | There are no (further) constraints on this element Element idObservation.component:coordinate-system.codeShort description 92822-6 DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://loinc.org", "code": "92822-6" } ] }Mappings
| ||
value[x] | Σ | 1..1 | Binding | There are no (further) constraints on this element Element idObservation.component:coordinate-system.value[x]Short description 0-based interval counting | 0-based character counting | 1-based character counting DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below. http://loinc.org/vs/LL5323-2 (extensible) Constraints
| ||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:coordinate-system.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:coordinate-system.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:coordinate-system.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
ref-allele | Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idObservation.component:ref-alleleShort description Genomic Ref Allele DefinitionReference values ('normal') examined within the Reference Sequence. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:ref-allele.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:ref-allele.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:ref-allele.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | There are no (further) constraints on this element Element idObservation.component:ref-allele.codeShort description 69547-8 DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://loinc.org", "code": "69547-8" } ] }Mappings
| ||
value[x] | Σ | 0..1 | There are no (further) constraints on this element Element idObservation.component:ref-allele.value[x]Short description Normalized string per the VCF format. DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below.
| |||
valueString | string | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:ref-allele.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:ref-allele.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:ref-allele.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
alt-allele | Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idObservation.component:alt-alleleShort description Genomic Alt Allele DefinitionThe genomic alternate allele is the contiguous segment of DNA in the test sample that differs from the reference allele at the same location and thus defines a variant. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:alt-allele.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:alt-allele.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:alt-allele.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | There are no (further) constraints on this element Element idObservation.component:alt-allele.codeShort description 69551-0 DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://loinc.org", "code": "69551-0" } ] }Mappings
| ||
value[x] | Σ | 0..1 | There are no (further) constraints on this element Element idObservation.component:alt-allele.value[x]Short description Normalized string per the VCF format. DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below.
| |||
valueString | string | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:alt-allele.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:alt-allele.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:alt-allele.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
coding-change-type | Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idObservation.component:coding-change-typeShort description Coding DNA Change Type DefinitionType of DNA change observed. Convenience property for variants with exact breakpoints, required otherwise. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:coding-change-type.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:coding-change-type.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:coding-change-type.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | There are no (further) constraints on this element Element idObservation.component:coding-change-type.codeShort description 48019-4 DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://loinc.org", "code": "48019-4" } ] }Mappings
| ||
value[x] | Σ | 1..1 | Binding | There are no (further) constraints on this element Element idObservation.component:coding-change-type.value[x]Short description deletion | insertion | delins | SNV | copy_number_gain | copy_number_loss | ... (many) DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below. Concepts in sequence ontology under SO:0002072
| ||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:coding-change-type.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:coding-change-type.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:coding-change-type.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
genomic-source-class | Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idObservation.component:genomic-source-classShort description Genomic Source Class DefinitionThe genomic class of the specimen being analyzed: Germline for inherited genome, somatic for cancer genome, and prenatal for fetal genome. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:genomic-source-class.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:genomic-source-class.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:genomic-source-class.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | There are no (further) constraints on this element Element idObservation.component:genomic-source-class.codeShort description 48002-0 DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://loinc.org", "code": "48002-0" } ] }Mappings
| ||
value[x] | Σ | 1..1 | Binding | There are no (further) constraints on this element Element idObservation.component:genomic-source-class.value[x]Short description Germline | Somatic | Fetal | Likely germline | Likely somatic | Likely fetal | Unknown genomic origin | De novo DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below. http://loinc.org/vs/LL378-1 (extensible) Constraints
| ||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:genomic-source-class.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:genomic-source-class.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:genomic-source-class.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
sample-allelic-frequency | Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idObservation.component:sample-allelic-frequencyShort description Sample Allelic Frequency DefinitionThe relative frequency of the allele at a given locus in the sample. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:sample-allelic-frequency.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:sample-allelic-frequency.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:sample-allelic-frequency.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | There are no (further) constraints on this element Element idObservation.component:sample-allelic-frequency.codeShort description 81258-6 DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://loinc.org", "code": "81258-6" } ] }Mappings
| ||
value[x] | Σ | 0..1 | There are no (further) constraints on this element Element idObservation.component:sample-allelic-frequency.value[x]Short description Relative frequency in the sample DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below.
| |||
valueQuantity | Quantity | There are no (further) constraints on this element Data type | ||||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:sample-allelic-frequency.value[x].idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:sample-allelic-frequency.value[x].extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
| ||
value | Σ | 0..1 | decimal | There are no (further) constraints on this element Element idObservation.component:sample-allelic-frequency.value[x].valueShort description Numerical value (with implicit precision) DefinitionThe value of the measured amount. The value includes an implicit precision in the presentation of the value. Precision is handled implicitly in almost all cases of measurement. The implicit precision in the value should always be honored. Monetary values have their own rules for handling precision (refer to standard accounting text books).
| ||
comparator | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idObservation.component:sample-allelic-frequency.value[x].comparatorShort description < | <= | >= | > - how to understand the value DefinitionHow the value should be understood and represented - whether the actual value is greater or less than the stated value due to measurement issues; e.g. if the comparator is "<" , then the real value is < stated value. Need a framework for handling measures where the value is <5ug/L or >400mg/L due to the limitations of measuring methodology. If there is no comparator, then there is no modification of the value How the Quantity should be understood and represented.
| ||
unit | Σ | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:sample-allelic-frequency.value[x].unitShort description Unit representation DefinitionA human-readable form of the unit. There are many representations for units of measure and in many contexts, particular representations are fixed and required. I.e. mcg for micrograms.
| ||
system | Σ C | 0..1 | uriPattern | There are no (further) constraints on this element Element idObservation.component:sample-allelic-frequency.value[x].systemShort description System that defines coded unit form DefinitionThe identification of the system that provides the coded form of the unit. Need to know the system that defines the coded form of the unit. The cardinality or value of this element may be affected by these constraints: qty-3 Constraints
http://unitsofmeasure.orgMappings
| ||
code | Σ | 0..1 | code | There are no (further) constraints on this element Element idObservation.component:sample-allelic-frequency.value[x].codeShort description Coded form of the unit DefinitionA computer processable form of the unit in some unit representation system. Need a computable form of the unit that is fixed across all forms. UCUM provides this for quantities, but SNOMED CT provides many units of interest. The preferred system is UCUM, but SNOMED CT can also be used (for customary units) or ISO 4217 for currency. The context of use may additionally require a code from a particular system.
| ||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:sample-allelic-frequency.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:sample-allelic-frequency.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:sample-allelic-frequency.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
allelic-read-depth | Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idObservation.component:allelic-read-depthShort description Allelic Read Depth DefinitionSpecifies the number of reads that identified the allele in question whether it consists of one or a small sequence of contiguous nucleotides. Different methods and purposes require different numbers of reads to be acceptable. Often >400, sometimes as few as 2-4. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:allelic-read-depth.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:allelic-read-depth.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:allelic-read-depth.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | There are no (further) constraints on this element Element idObservation.component:allelic-read-depth.codeShort description 82121-5 DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://loinc.org", "code": "82121-5" } ] }Mappings
| ||
value[x] | Σ | 0..1 | There are no (further) constraints on this element Element idObservation.component:allelic-read-depth.value[x]Short description Unfiltered count of supporting reads DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below.
| |||
valueQuantity | Quantity | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:allelic-read-depth.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:allelic-read-depth.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:allelic-read-depth.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
allelic-state | Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idObservation.component:allelic-stateShort description Allelic State DefinitionThe observed level of occurrence of the variant in the set of chromosomes. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:allelic-state.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:allelic-state.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:allelic-state.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | There are no (further) constraints on this element Element idObservation.component:allelic-state.codeShort description 53034-5 DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://loinc.org", "code": "53034-5" } ] }Mappings
| ||
value[x] | Σ | 1..1 | Binding | There are no (further) constraints on this element Element idObservation.component:allelic-state.value[x]Short description Heteroplasmic | Homoplasmic | Homozygous | Heterozygous | Hemizygous DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below. http://loinc.org/vs/LL381-5 (extensible) Constraints
| ||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:allelic-state.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:allelic-state.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:allelic-state.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
variant-inheritance | Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idObservation.component:variant-inheritanceShort description Variant Inheritance DefinitionBy which parent the variant was inherited in the patient, if known. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:variant-inheritance.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:variant-inheritance.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:variant-inheritance.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | There are no (further) constraints on this element Element idObservation.component:variant-inheritance.codeShort description variant-inheritance DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://hl7.org/fhir/uv/genomics-reporting/CodeSystem/tbd-codes-cs", "code": "variant-inheritance" } ] }Mappings
| ||
value[x] | Σ | 1..1 | Binding | There are no (further) constraints on this element Element idObservation.component:variant-inheritance.value[x]Short description Maternal | Paternal | Unknown DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below. VariantInheritanceVS (extensible) Constraints
| ||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:variant-inheritance.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:variant-inheritance.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:variant-inheritance.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
variation-code | Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element idObservation.component:variation-codeShort description Variation Code DefinitionAccession number in a variant database such as ClinVar, given for cross-reference. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:variation-code.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:variation-code.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:variation-code.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | There are no (further) constraints on this element Element idObservation.component:variation-code.codeShort description 81252-9 DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://loinc.org", "code": "81252-9" } ] }Mappings
| ||
value[x] | Σ | 1..1 | There are no (further) constraints on this element Element idObservation.component:variation-code.value[x]Short description ClinVar ID or similar DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below. Multiple bindings acceptable
| |||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:variation-code.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:variation-code.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:variation-code.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
chromosome-identifier | Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element idObservation.component:chromosome-identifierShort description Chromosome Identifier DefinitionAn indicator, enumerated in humans by numbers 1-22, X, and Y, representing the chromosome on which the variant is located. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:chromosome-identifier.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:chromosome-identifier.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:chromosome-identifier.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | There are no (further) constraints on this element Element idObservation.component:chromosome-identifier.codeShort description 48000-4 DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://loinc.org", "code": "48000-4" } ] }Mappings
| ||
value[x] | Σ | 1..1 | Binding | There are no (further) constraints on this element Element idObservation.component:chromosome-identifier.value[x]Short description Chromosome 1 | Chromosome 2 | ... | Chromosome 22 | Chromosome X | Chromosome Y DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below. http://loinc.org/vs/LL2938-0 (required) Constraints
| ||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:chromosome-identifier.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:chromosome-identifier.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:chromosome-identifier.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
protein-hgvs | Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idObservation.component:protein-hgvsShort description Protein (Amino Acid) Change - pHGVS DefinitionDescription of the protein (amino acid) sequence change using a valid HGVS-formatted string. The description of the variant is surrounded in parentheses if it is calculated rather than directly observed. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:protein-hgvs.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:protein-hgvs.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:protein-hgvs.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | There are no (further) constraints on this element Element idObservation.component:protein-hgvs.codeShort description 48005-3 DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://loinc.org", "code": "48005-3" } ] }Mappings
| ||
value[x] | Σ | 1..1 | Binding | There are no (further) constraints on this element Element idObservation.component:protein-hgvs.value[x]Short description A valid HGVS-formatted 'p.' string, e.g. NP_000050.2:p.(Asn1836Lys) DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below.
| ||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:protein-hgvs.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:protein-hgvs.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:protein-hgvs.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
amino-acid-change-type | Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idObservation.component:amino-acid-change-typeShort description Amino Acid Change Type DefinitionCodified type for associated Amino Acid Marker, for convenience. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:amino-acid-change-type.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:amino-acid-change-type.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:amino-acid-change-type.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | There are no (further) constraints on this element Element idObservation.component:amino-acid-change-type.codeShort description 48006-1 DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://loinc.org", "code": "48006-1" } ] }Mappings
| ||
value[x] | Σ | 1..1 | Binding | There are no (further) constraints on this element Element idObservation.component:amino-acid-change-type.value[x]Short description Wild type | Deletion | Duplication | Frameshift | Initiating Methionine | Insertion | Insertion and Deletion | Missense | Nonsense | Silent DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below. http://loinc.org/vs/LL380-7 (extensible) Constraints
| ||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:amino-acid-change-type.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:amino-acid-change-type.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:amino-acid-change-type.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
molecular-consequence | Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idObservation.component:molecular-consequenceShort description Molecular Consequence DefinitionThe calculated or observed effect of a variant on its downstream transcript and, if applicable, ensuing protein sequence. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:molecular-consequence.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:molecular-consequence.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:molecular-consequence.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | There are no (further) constraints on this element Element idObservation.component:molecular-consequence.codeShort description molecular-consequence DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://hl7.org/fhir/uv/genomics-reporting/CodeSystem/tbd-codes-cs", "code": "molecular-consequence" } ] }Mappings
| ||
value[x] | Σ | 1..1 | Binding | There are no (further) constraints on this element Element idObservation.component:molecular-consequence.value[x]Short description stop_lost | stop_gained | inframe_insertion | frameshift_variant | ... (many) DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below. Concepts in sequence ontology under SO:0001537. MolecularConsequenceVS (extensible) Constraints
| ||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:molecular-consequence.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:molecular-consequence.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:molecular-consequence.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
copy-number | Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idObservation.component:copy-numberShort description Genomic Structural Variant Copy Number DefinitionThe copy number of the large variant. In HGVS, this is the numeric value following the “X”. It is a unit-less value. Note that a copy number of 1 can imply a deletion. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:copy-number.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:copy-number.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:copy-number.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | There are no (further) constraints on this element Element idObservation.component:copy-number.codeShort description 82155-3 DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://loinc.org", "code": "82155-3" } ] }Mappings
| ||
value[x] | Σ C | 0..1 | There are no (further) constraints on this element Element idObservation.component:copy-number.value[x]Short description Actual component result DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below.
| |||
valueQuantity | Quantity | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:copy-number.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:copy-number.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:copy-number.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
variant-confidence-status | Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idObservation.component:variant-confidence-statusShort description Variant Confidence Status DefinitionA code that represents the confidence of a true positive variant call. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:variant-confidence-status.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:variant-confidence-status.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:variant-confidence-status.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | There are no (further) constraints on this element Element idObservation.component:variant-confidence-status.codeShort description variant-confidence-status DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://hl7.org/fhir/uv/genomics-reporting/CodeSystem/tbd-codes-cs", "code": "variant-confidence-status" } ] }Mappings
| ||
value[x] | Σ | 1..1 | Binding | There are no (further) constraints on this element Element idObservation.component:variant-confidence-status.value[x]Short description High | Intermediate | Low DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below. VariantConfidenceStatusVS (required) Constraints
| ||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:variant-confidence-status.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:variant-confidence-status.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:variant-confidence-status.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
class | Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idObservation.component:classShort description Component results DefinitionSome 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. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:class.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:class.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:class.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | Element idObservation.component:class.codeShort description Type of component observation (code / type) DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://snomed.info/sct", "code": "277046005", "display": "Class" } ] }Mappings
| ||
value[x] | Σ | 1..1 | There are no (further) constraints on this element Element idObservation.component:class.value[x]Short description Actual component result DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below.
| |||
valueQuantity | Quantity | There are no (further) constraints on this element Data type | ||||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
valueString | string | There are no (further) constraints on this element Data type | ||||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||||
valueInteger | integer | There are no (further) constraints on this element Data type | ||||
valueRange | Range | There are no (further) constraints on this element Data type | ||||
valueRatio | Ratio | There are no (further) constraints on this element Data type | ||||
valueSampledData | SampledData | There are no (further) constraints on this element Data type | ||||
valueTime | time | There are no (further) constraints on this element Data type | ||||
valueDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:class.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:class.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:class.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
| |||
probability | Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idObservation.component:probabilityShort description Component results DefinitionSome 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. 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. For a discussion on the ways Observations can be assembled in groups together see Notes below.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idObservation.component:probability.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:probability.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idObservation.component:probability.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
| ||
code | Σ | 1..1 | CodeableConceptPattern | Element idObservation.component:probability.codeShort description Type of component observation (code / type) DefinitionDescribes what was observed. Sometimes this is called the observation "code". Knowing what kind of observation is being made is essential to understanding the observation. All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. Codes identifying names of simple observations.
{ "coding": [ { "system": "http://ncicb.nci.nih.gov/xml/owl/EVS/Thesaurus.owl", "code": "C54154", "display": "Probability" } ] }Mappings
| ||
value[x] | Σ | 1..1 | There are no (further) constraints on this element Element idObservation.component:probability.value[x]Short description Actual component result DefinitionThe information determined as a result of making the observation, if the information has a simple value. An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the Notes section below.
| |||
valueQuantity | Quantity | There are no (further) constraints on this element Data type | ||||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
valueString | string | There are no (further) constraints on this element Data type | ||||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||||
valueInteger | integer | There are no (further) constraints on this element Data type | ||||
valueRange | Range | There are no (further) constraints on this element Data type | ||||
valueRatio | Ratio | There are no (further) constraints on this element Data type | ||||
valueSampledData | SampledData | There are no (further) constraints on this element Data type | ||||
valueTime | time | There are no (further) constraints on this element Data type | ||||
valueDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
dataAbsentReason | C | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:probability.dataAbsentReasonShort description Why the component result is missing DefinitionProvides a reason why the expected value in the element Observation.component.value[x] is missing. For many results it is necessary to handle exceptional values in measurements. "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. Codes specifying why the result ( The cardinality or value of this element may be affected by these constraints: obs-6 Constraints
| ||
interpretation | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idObservation.component:probability.interpretationShort description High, low, normal, etc. Alternate namesAbnormal Flag DefinitionA categorical assessment of an observation value. For example, high, low, normal. For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result. Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Codes identifying interpretations of observations. ObservationInterpretationCodes (extensible) Constraints
| |||
referenceRange | 0..* | see (referenceRange) | There are no (further) constraints on this element Element idObservation.component:probability.referenceRangeShort description Provides guide for interpretation of component result DefinitionGuidance on how to interpret the value by comparison to a normal or recommended range. 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. 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 might 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.
|
instances
Structured Output
Observation |
id : GbmAlgorithmSummaryOutputObservation |
meta |
profile : http://omi.de/fhir/registry/StructureDefinition/gbm-output-observation-profile |
component |
value |
unit : mL |
system : http://unitsofmeasure.org |
code : ml |
value : 69 |
code |
coding |
code : 258261001 |
system : http://snomed.info/sct |
display : Tumor volume (observable entity) |
component |
value |
unit : mL |
system : http://unitsofmeasure.org |
code : ml |
value : 51 |
code |
coding |
code : C121674 |
system : http://ncicb.nci.nih.gov/xml/owl/EVS/Thesaurus.owl |
display : Peritumoral Edema |
component |
value |
unit : mL |
system : http://unitsofmeasure.org |
code : ml |
value : 16 |
code |
coding |
code : enhancingTumor |
system : http://omi.de/fhir/registry/CodeSystem/TodoCodesCS |
display : Enhancing Tumor |
component |
value |
unit : mL |
system : http://unitsofmeasure.org |
code : ml |
value : 1 |
code |
coding |
code : necroticAndNonEnhancingTumor |
system : http://omi.de/fhir/registry/CodeSystem/TodoCodesCS |
display : Necrotic and Non-Enhancing Tumor |
code |
coding |
code : 371534008 |
system : http://snomed.info/sct |
display : Summary report |
status : final |
Observation |
id : GbmAlgorithmFilteredSegmentationOutputObservation |
meta |
profile : http://omi.de/fhir/registry/StructureDefinition/gbm-output-observation-profile |
component |
value |
unit : mL |
system : http://unitsofmeasure.org |
code : ml |
value : 69 |
code |
coding |
code : 258261001 |
system : http://snomed.info/sct |
display : Tumor volume (observable entity) |
code |
coding |
code : 74529008 |
system : http://snomed.info/sct |
display : Image analysis, segmentation |
status : final |
Observation |
id : GbmAlgorithmVolumeOutputObservation |
meta |
profile : http://omi.de/fhir/registry/StructureDefinition/gbm-output-observation-profile |
component |
value |
unit : mL |
system : http://unitsofmeasure.org |
code : ml |
value : 68.5 |
code |
coding |
code : 258261001 |
system : http://snomed.info/sct |
display : Tumor volume (observable entity) |
component |
value |
unit : mL |
system : http://unitsofmeasure.org |
code : ml |
value : 50.76 |
code |
coding |
code : C121674 |
system : http://ncicb.nci.nih.gov/xml/owl/EVS/Thesaurus.owl |
display : Peritumoral Edema |
component |
value |
unit : mL |
system : http://unitsofmeasure.org |
code : ml |
value : 16.39 |
code |
coding |
code : enhancingTumor |
system : http://omi.de/fhir/registry/CodeSystem/TodoCodesCS |
display : Enhancing Tumor |
component |
value |
unit : mL |
system : http://unitsofmeasure.org |
code : ml |
value : 1.35 |
code |
coding |
code : necroticAndNonEnhancingTumor |
system : http://omi.de/fhir/registry/CodeSystem/TodoCodesCS |
display : Necrotic and Non-Enhancing Tumor |
code |
coding |
code : 118565006 |
system : http://snomed.info/sct |
display : Volume |
status : final |
Variants / Biomarkers
Observation |
id : MGMTMutation |
meta |
profile : http://omi.de/fhir/registry/StructureDefinition/gbm-variant |
component |
code |
coding |
system : http://loinc.org |
code : 48018-6 |
display : Gene studied ID |
value |
coding |
code : 7059 |
system : http://www.genenames.org/geneId |
display : MGMT |
component |
code |
coding |
code : 277046005 |
system : http://snomed.info/sct |
display : Class |
value : 0 |
component |
value |
value : 0.93 |
code |
coding |
code : C54154 |
system : http://ncicb.nci.nih.gov/xml/owl/EVS/Thesaurus.owl |
display : Probability |
code |
coding |
system : http://loinc.org |
code : 69548-6 |
category |
coding |
system : http://terminology.hl7.org/CodeSystem/observation-category |
code : laboratory |
status : final |
Observation |
id : IDHMutation |
meta |
profile : http://omi.de/fhir/registry/StructureDefinition/gbm-variant |
component |
code |
coding |
system : http://loinc.org |
code : 48018-6 |
display : Gene studied ID |
value |
coding |
code : 5382 |
system : http://www.genenames.org/geneId |
display : IDH1 |
component |
code |
coding |
code : 277046005 |
system : http://snomed.info/sct |
display : Class |
value : 0 |
component |
value |
value : 1 |
code |
coding |
code : C54154 |
system : http://ncicb.nci.nih.gov/xml/owl/EVS/Thesaurus.owl |
display : Probability |
code |
coding |
system : http://loinc.org |
code : 69548-6 |
category |
coding |
system : http://terminology.hl7.org/CodeSystem/observation-category |
code : laboratory |
status : final |
Observation |
id : ATRXMutation |
meta |
profile : http://omi.de/fhir/registry/StructureDefinition/gbm-variant |
component |
code |
coding |
system : http://loinc.org |
code : 48018-6 |
display : Gene studied ID |
value |
coding |
code : 886 |
system : http://www.genenames.org/geneId |
display : ATRX |
component |
code |
coding |
code : 277046005 |
system : http://snomed.info/sct |
display : Class |
value : 0 |
component |
value |
value : 0.92 |
code |
coding |
code : C54154 |
system : http://ncicb.nci.nih.gov/xml/owl/EVS/Thesaurus.owl |
display : Probability |
code |
coding |
system : http://loinc.org |
code : 69548-6 |
category |
coding |
system : http://terminology.hl7.org/CodeSystem/observation-category |
code : laboratory |
status : final |