Testēšanas pārskata struktūra
Testēšanas pārskats ir nespecifisko izmeklējumu rezultātu kopa.
Izskatīšanas pieeja:
- Kā ir iespējams reģistrēt vienkāršos gadījumus? (EGĀ)
- Kā ir iespējams reģistrēt sarežģitākus gadījumus, kad izmeklējums neizriet no citiem izmeklējumiem (asins saderība)?
- Kā ir iespējams reģistrēt sarežģitākus gadījumus, kad izmeklējums nosaka pakārtotu izmeklējumu veikšanu (mikrobiloģija)?
- Kā ir iespējams reģistrēt sarežģitākus gadījumus, kad izmeklējums tiek veikts auglim?
- Kā ir iespējams reģistrēt sarežģitākus gadījumus, kad izmeklējums tiek veikts dzīvnieka vai insekta materiālā?
- Kā ir iespējams reģistrēt sarežģitākus gadījumus, kad izmeklējums tiek veikts materiālā, kas ir noņemts no priekšmeta, kas ir saistīts ar pacientu?
Testēšanas pārskats
DiagnosticReport | I | DiagnosticReport | There are no (further) constraints on this element Element IdDiagnosticReport A Diagnostic report - a combination of request information, atomic results, images, interpretation, as well as formatted reports Alternate namesReport, Test, Result, Results, Labs, Laboratory DefinitionThe findings and interpretation of diagnostic tests performed on patients, groups of patients, devices, and locations, and/or specimens derived from these. The report includes clinical context such as requesting and provider information, and some mix of atomic results, images, textual and coded interpretations, and formatted representation of diagnostic reports. This is intended to capture a single report and is not suitable for use in displaying summary information that covers multiple reports. For example, this resource has not been designed for laboratory cumulative reporting formats nor detailed structured reports for sequencing.
| |
identifier | Σ | 1..1 | Identifier | Element IdDiagnosticReport.identifier Business identifier for report Alternate namesReportID, Filler ID, Placer ID DefinitionIdentifiers assigned to this report by the performer or other systems. | Testēšanas pārskata identifikators Need to know what identifier to use when making queries about this report from the source laboratory, and for linking to the report outside FHIR context. Usually assigned by the Information System of the diagnostic service provider (filler id). Unordered, Open, by type(Value) Constraints
|
LabDiagnosticReportShortId | S Σ | 1..1 | Identifier | There are no (further) constraints on this element Element IdDiagnosticReport.identifier:LabDiagnosticReportShortId Business identifier for report Alternate namesReportID, Filler ID, Placer ID DefinitionIdentifiers assigned to this report by the performer or other systems. Need to know what identifier to use when making queries about this report from the source laboratory, and for linking to the report outside FHIR context. Usually assigned by the Information System of the diagnostic service provider (filler id).
|
use | S Σ ?! | 1..1 | codeBindingFixed Value | Element IdDiagnosticReport.identifier:LabDiagnosticReportShortId.use 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 . IdentifierUse (required)Constraints
usual
|
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdDiagnosticReport.identifier:LabDiagnosticReportShortId.type 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 | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdDiagnosticReport.identifier:LabDiagnosticReportShortId.system 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.
General http://www.acme.com/identifiers/patient Mappings
|
value | S Σ | 1..1 | string | Element IdDiagnosticReport.identifier:LabDiagnosticReportShortId.value The value that is might not be unique DefinitionAn identifier assigned to this Diagnostic Report in LIS and placed in pdf representation for users. | Unikāls testēšanas pārskata identifikators LIS, kurš tiek ievietots pdf testēšanas pārskata formā lietotājiem. 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 123456 Mappings
|
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdDiagnosticReport.identifier:LabDiagnosticReportShortId.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
|
assigner | Σ I | 0..1 | Reference(Organization) | There are no (further) constraints on this element Element IdDiagnosticReport.identifier:LabDiagnosticReportShortId.assigner 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.
|
LabDiagnosticReportUniqueId | S Σ | 1..1 | Identifier | There are no (further) constraints on this element Element IdDiagnosticReport.identifier:LabDiagnosticReportUniqueId Business identifier for report Alternate namesReportID, Filler ID, Placer ID DefinitionIdentifiers assigned to this report by the performer or other systems. Need to know what identifier to use when making queries about this report from the source laboratory, and for linking to the report outside FHIR context. Usually assigned by the Information System of the diagnostic service provider (filler id).
|
use | S Σ ?! | 1..1 | codeBindingFixed Value | Element IdDiagnosticReport.identifier:LabDiagnosticReportUniqueId.use 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 . IdentifierUse (required)Constraints
official
|
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdDiagnosticReport.identifier:LabDiagnosticReportUniqueId.type 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 | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdDiagnosticReport.identifier:LabDiagnosticReportUniqueId.system 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.
General http://www.acme.com/identifiers/patient Mappings
|
value | S Σ | 1..1 | string | Element IdDiagnosticReport.identifier:LabDiagnosticReportUniqueId.value The value that is unique DefinitionA unique identifier assigned to this diagnostic report in LIS. diagnostic report identifier MUST follow the following algorithm: [organisation code][resource id][resource version][effective year][unique sequence of 10 digits within organisation] | Unikāls testēšanas pārskata identifikators LIS. Testēšanas pārskata identifikatoram jāatbilst sekojošam veidošanas algoritmam: [organizācijas kods][resursa id][resursa versija][testēšanas pārskata gads][unikāla 10 ciparu kombinācija organizācijas ietvaros] 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 123456 LabDiagnosticReportUniqueId 010068303.1.1.1.0.0000000001 Mappings
|
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdDiagnosticReport.identifier:LabDiagnosticReportUniqueId.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
|
assigner | Σ I | 0..1 | Reference(Organization) | There are no (further) constraints on this element Element IdDiagnosticReport.identifier:LabDiagnosticReportUniqueId.assigner 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.
|
basedOn | S I | 1..1 | Reference(ServiceRequest) | Element IdDiagnosticReport.basedOn What was requested Alternate namesRequest DefinitionDetails concerning a service requested. This allows tracing of authorization for the report and tracking whether proposals/recommendations were acted upon. Note: Usually there is one test request for each result, however in some circumstances multiple test requests may be represented using a single test result resource. Note that there are also cases where one request leads to multiple reports. Allowed aggregation: referenced Constraints
|
reference | S Σ I | 1..1 | string | Element IdDiagnosticReport.basedOn.reference Reference to system Service Request Id DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdDiagnosticReport.basedOn.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
|
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdDiagnosticReport.basedOn.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdDiagnosticReport.basedOn.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
status | Σ ?! | 1..1 | codeBinding | Element IdDiagnosticReport.status registered | partial | preliminary | final + DefinitionThe status of the diagnostic report. Diagnostic services routinely issue provisional/incomplete reports, and sometimes withdraw previously released reports. Note that FHIR strings SHALL NOT exceed 1MB in size The status of the diagnostic report. http://kleintech.software/fhir/terminology/1.3.6.1.4.1.38760.2.803 (required)Constraints
|
category | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element IdDiagnosticReport.category Service category Alternate namesDepartment, Sub-department, Service, Discipline DefinitionA code that classifies the clinical discipline, department or diagnostic service that created the report (e.g. cardiology, biochemistry, hematology, MRI). This is used for searching, sorting and display purposes. Multiple categories are allowed using various categorization schemes. The level of granularity is defined by the category concepts in the value set. More fine-grained filtering can be performed using the metadata and/or terminology hierarchy in DiagnosticReport.code. Codes for diagnostic service sections. DiagnosticServiceSectionCodes (example)Constraints
|
code | S Σ | 1..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdDiagnosticReport.code Name/Code for this diagnostic report Alternate namesType DefinitionA code or name that describes this diagnostic report. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Codes that describe Diagnostic Reports. LOINCDiagnosticReportCodes (preferred)Constraints
|
coding | S Σ | 1..1 | CodingFixed Value | Element IdDiagnosticReport.code.coding 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://kleintech.software/fhir/terminology/1.3.6.1.4.1.38760.2.809", "code": "1.3.6.1.4.1.38760.FHIR.1.1.1", "display": "Testēšanas pārskats" }
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element IdDiagnosticReport.code.text 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.
|
subject | S Σ I | 1..1 | Reference(Patient) | Element IdDiagnosticReport.subject The subject of the report - usually, but not always, the patient Alternate namesPatient DefinitionThe subject of the report. Usually, but not always, this is a patient. However, diagnostic services also perform analyses on specimens collected from a variety of other sources. SHALL know the subject context. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Allowed aggregation: referenced Constraints
|
reference | S Σ I | 1..1 | string | Element IdDiagnosticReport.subject.reference Patient system Id in EHR DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdDiagnosticReport.subject.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
|
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdDiagnosticReport.subject.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdDiagnosticReport.subject.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
encounter | Σ I | 0..1 | Reference(Encounter) | There are no (further) constraints on this element Element IdDiagnosticReport.encounter Health care event when test ordered Alternate namesContext DefinitionThe healthcare event (e.g. a patient and healthcare provider interaction) which this DiagnosticReport is about. Links the request to the Encounter context. 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] | S Σ | 1..1 | Element IdDiagnosticReport.effective[x] Diagnostic Report validation time Alternate namesObservation time, Effective Time, Occurrence DefinitionAs Laboratory Diagnostic Report contains observations of specimen collected on different dates or in different time and same specimen might be retested later on, no accurate specimen collection datetime is applicable. The approval/ validation datetime will be used instead. Need to know where in the patient history to file/present this report. If the diagnostic procedure was performed on the patient, this is the time it was performed. If there are specimens, the diagnostically relevant time can be derived from the specimen collection times, but the specimen information is not always available, and the exact relationship between the specimens and the diagnostically relevant time is not always automatic.
| |
effectiveDateTime | dateTime | There are no (further) constraints on this element Data Type | ||
effectivePeriod | Period | There are no (further) constraints on this element Data Type | ||
issued | S Σ | 1..1 | instant | Element IdDiagnosticReport.issued DateTime this version was made Alternate namesDate published, Date Issued, Date Verified DefinitionThe date and time that this version of the report was made available to LAB IS, typically after the report was reviewed and verified; in case of historical data effective and issued datetime may differ by years. Clinicians need to be able to check the date that the report was released. May be different from the update time of the resource itself, because that is the status of the record (potentially a secondary copy), not the actual release time of the report.
|
performer | S Σ I | 1..1 | Reference(Organization) | Element IdDiagnosticReport.performer Responsible Diagnostic Service Alternate namesLaboratory, Service, Practitioner, Department, Company, Authorized by, Director DefinitionThe diagnostic service that is responsible for issuing the report. Need to know whom to contact if there are queries about the results. Also may need to track the source of reports for secondary data analysis. This is not necessarily the source of the atomic data items or the entity that interpreted the results. It is the entity that takes responsibility for the clinical report. Allowed aggregation: referenced Constraints
|
reference | S Σ I | 1..1 | string | There are no (further) constraints on this element Element IdDiagnosticReport.performer.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdDiagnosticReport.performer.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
|
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdDiagnosticReport.performer.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdDiagnosticReport.performer.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
resultsInterpreter | S Σ I | 1..* | Reference(PractitionerRole) | Element IdDiagnosticReport.resultsInterpreter Primary result interpreter Alternate namesAnalyzed by, Reported by DefinitionThe practitioner or organization that is responsible for the report's conclusions and interpretations. Need to know whom to contact if there are queries about the results. Also may need to track the source of reports for secondary data analysis. Might not be the same entity that takes responsibility for the clinical report. Allowed aggregation: referenced Constraints
|
reference | S Σ I | 1..1 | string | There are no (further) constraints on this element Element IdDiagnosticReport.resultsInterpreter.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdDiagnosticReport.resultsInterpreter.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
|
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdDiagnosticReport.resultsInterpreter.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdDiagnosticReport.resultsInterpreter.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
specimen | S I | 1..* | Reference(Specimen) | There are no (further) constraints on this element Element IdDiagnosticReport.specimen Specimens this report is based on DefinitionDetails about the specimens on which this diagnostic report is based. Need to be able to report information about the collected specimens on which the report is based. If the specimen is sufficiently specified with a code in the test result name, then this additional data may be redundant. If there are multiple specimens, these may be represented per observation or group.
|
reference | S Σ I | 1..1 | string | There are no (further) constraints on this element Element IdDiagnosticReport.specimen.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdDiagnosticReport.specimen.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
|
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdDiagnosticReport.specimen.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdDiagnosticReport.specimen.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
result | I | 1..* | Reference(Observation) | There are no (further) constraints on this element Element IdDiagnosticReport.result Observations Alternate namesData, Atomic Value, Result, Atomic result, Data, Test, Analyte, Battery, Organizer DefinitionObservations that are part of this diagnostic report. Need to support individual results, or groups of results, where the result grouping is arbitrary, but meaningful. Observations can contain observations.
|
reference | S Σ I | 1..1 | string | There are no (further) constraints on this element Element IdDiagnosticReport.result.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdDiagnosticReport.result.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
|
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdDiagnosticReport.result.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdDiagnosticReport.result.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
imagingStudy | I | 0..0 | Reference(ImagingStudy) | There are no (further) constraints on this element Element IdDiagnosticReport.imagingStudy Reference to full details of imaging associated with the diagnostic report DefinitionOne or more links to full details of any imaging performed during the diagnostic investigation. Typically, this is imaging performed by DICOM enabled modalities, but this is not required. A fully enabled PACS viewer can use this information to provide views of the source images. ImagingStudy and the image element are somewhat overlapping - typically, the list of image references in the image element will also be found in one of the imaging study resources. However, each caters to different types of displays for different types of purposes. Neither, either, or both may be provided.
|
media | Σ | 1..* | BackboneElement | Element IdDiagnosticReport.media Logotypes associated with this report Alternate namesDICOM, Slides, Scans DefinitionReferemce uz laboratorijas logotipu un LATAK logotipts, ja nepieciešams. Many diagnostic services include images in the report as part of their service.
|
comment | 0..1 | string | There are no (further) constraints on this element Element IdDiagnosticReport.media.comment Comment about the image (e.g. explanation) DefinitionA comment about the image. Typically, this is used to provide an explanation for why the image is included, or to draw the viewer's attention to important features. The provider of the report should make a comment about each image included in the report. The comment should be displayed with the image. It would be common for the report to include additional discussion of the image contents in other sections such as the conclusion.
| |
link | S Σ I | 1..1 | Reference(Media) | There are no (further) constraints on this element Element IdDiagnosticReport.media.link Reference to the image source DefinitionReference to the image source. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
reference | S Σ I | 1..1 | string | There are no (further) constraints on this element Element IdDiagnosticReport.media.link.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdDiagnosticReport.media.link.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
|
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdDiagnosticReport.media.link.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdDiagnosticReport.media.link.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
conclusion | 0..1 | string | There are no (further) constraints on this element Element IdDiagnosticReport.conclusion Clinical conclusion (interpretation) of test results Alternate namesReport DefinitionConcise and clinically contextualized summary conclusion (interpretation/impression) of the diagnostic report. Need to be able to provide a conclusion that is not lost among the basic result data. Note that FHIR strings SHALL NOT exceed 1MB in size
| |
conclusionCode | 0..* | CodeableConcept | There are no (further) constraints on this element Element IdDiagnosticReport.conclusionCode Codes for the clinical conclusion of test results DefinitionOne or more codes that represent the summary conclusion (interpretation/impression) of the diagnostic report. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Diagnosis codes provided as adjuncts to the report. SNOMEDCTClinicalFindings (example)Constraints
| |
presentedForm | S I | 0..* | Attachment | There are no (further) constraints on this element Element IdDiagnosticReport.presentedForm Entire report as issued DefinitionRich text representation of the entire result as issued by the diagnostic service. Multiple formats are allowed but they SHALL be semantically equivalent. Gives laboratory the ability to provide its own fully formatted report for clinical fidelity. "application/pdf" is recommended as the most reliable and interoperable in this context.
|
contentType | Σ | 1..1 | codeBindingFixed Value | Element IdDiagnosticReport.presentedForm.contentType Mime type of the content, with charset etc. Definition"application/pdf" is expected. Processors of the data need to be able to know how to interpret the data. Note that FHIR strings SHALL NOT exceed 1MB in size The mime type of an attachment. Any valid mime type is allowed. Mime Types (required)Constraints
application/pdf
|
language | S Σ | 1..1 | codeBinding | Element IdDiagnosticReport.presentedForm.language Human language of the content (BCP-47) DefinitionThe human language of the content. The value can be any valid value according to BCP 47. Users need to be able to choose between the languages in a set of attachments. Note that FHIR strings SHALL NOT exceed 1MB in size A human language. http://kleintech.software/fhir/terminology/1.3.6.1.4.1.38760.2.2 (required)Constraints
General en-AU Mappings
|
data | S | 1..1 | base64Binary | There are no (further) constraints on this element Element IdDiagnosticReport.presentedForm.data Data inline, base64ed DefinitionThe actual data of the attachment - a sequence of bytes, base64 encoded. The data needs to able to be transmitted inline. The base64-encoded data SHALL be expressed in the same character set as the base resource XML or JSON.
|
url | Σ | 0..1 | url | There are no (further) constraints on this element Element IdDiagnosticReport.presentedForm.url Uri where the data can be found DefinitionA location where the data can be accessed. The data needs to be transmitted by reference. If both data and url are provided, the url SHALL point to the same content as the data contains. Urls may be relative references or may reference transient locations such as a wrapping envelope using cid: though this has ramifications for using signatures. Relative URLs are interpreted relative to the service url, like a resource reference, rather than relative to the resource itself. If a URL is provided, it SHALL resolve to actual data.
General http://www.acme.com/logo-small.png Mappings
|
size | Σ | 0..1 | unsignedInt | There are no (further) constraints on this element Element IdDiagnosticReport.presentedForm.size Number of bytes of content (if url provided) DefinitionThe number of bytes of data that make up this attachment (before base64 encoding, if that is done). Representing the size allows applications to determine whether they should fetch the content automatically in advance, or refuse to fetch it at all. The number of bytes is redundant if the data is provided as a base64binary, but is useful if the data is provided as a url reference.
|
hash | Σ | 0..1 | base64Binary | There are no (further) constraints on this element Element IdDiagnosticReport.presentedForm.hash Hash of the data (sha-1, base64ed) DefinitionThe calculated hash of the data using SHA-1. Represented using base64. Included so that applications can verify that the contents of a location have not changed due to technical failures (e.g., storage rot, transport glitch, incorrect version). The hash is calculated on the data prior to base64 encoding, if the data is based64 encoded. The hash is not intended to support digital signatures. Where protection against malicious threats a digital signature should be considered, see Provenance.signature for mechanism to protect a resource with a digital signature.
|
title | S Σ | 1..1 | string | There are no (further) constraints on this element Element IdDiagnosticReport.presentedForm.title Label to display in place of the data DefinitionA label or set of text to display in place of the data. Applications need a label to display to a human user in place of the actual data if the data cannot be rendered or perceived by the viewer. Note that FHIR strings SHALL NOT exceed 1MB in size
General Official Corporate Logo Mappings
|
creation | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element IdDiagnosticReport.presentedForm.creation Date attachment was first created DefinitionThe date that the attachment was first created. This is often tracked as an integrity issue for use of the attachment.
|
JSON struktūra:
{ "resourceType": "StructureDefinition", "id": "1.3.6.1.4.1.38760.FHIR.1.1.1", "url": "https://example.org/fhir/StructureDefinition/LaboratoryDiagnosticReport", "version": "0", "name": "LaboratoryDiagnosticReport", "status": "draft", "description": "General Laboratory Diagnostic Report | Laboratorijas testēšanas pārskats", "fhirVersion": "4.0.1", "kind": "resource", "abstract": false, "type": "DiagnosticReport", "baseDefinition": "http://hl7.org/fhir/StructureDefinition/DiagnosticReport", "derivation": "constraint", "differential": { "element": [ { "id": "DiagnosticReport.identifier", "path": "DiagnosticReport.identifier", "slicing": { "discriminator": [ { "type": "value", "path": "type" } ], "rules": "open" }, "definition": "Identifiers assigned to this report by the performer or other systems. | Testēšanas pārskata identifikators", "min": 1, "max": "1" }, { "id": "DiagnosticReport.identifier:LabDiagnosticReportShortId", "path": "DiagnosticReport.identifier", "sliceName": "LabDiagnosticReportShortId", "min": 1, "max": "1", "mustSupport": true }, { "id": "DiagnosticReport.identifier:LabDiagnosticReportShortId.use", "path": "DiagnosticReport.identifier.use", "min": 1, "fixedCode": "usual", "mustSupport": true }, { "id": "DiagnosticReport.identifier:LabDiagnosticReportShortId.value", "path": "DiagnosticReport.identifier.value", "short": "The value that is might not be unique", "definition": "An identifier assigned to this Diagnostic Report in LIS and placed in pdf representation for users. | Unikāls testēšanas pārskata identifikators LIS, kurš tiek ievietots pdf testēšanas pārskata formā lietotājiem.", "min": 1, "mustSupport": true }, { "id": "DiagnosticReport.identifier:LabDiagnosticReportUniqueId", "path": "DiagnosticReport.identifier", "sliceName": "LabDiagnosticReportUniqueId", "min": 1, "max": "1", "mustSupport": true }, { "id": "DiagnosticReport.identifier:LabDiagnosticReportUniqueId.use", "path": "DiagnosticReport.identifier.use", "min": 1, "fixedCode": "official", "mustSupport": true }, { "id": "DiagnosticReport.identifier:LabDiagnosticReportUniqueId.value", "path": "DiagnosticReport.identifier.value", "definition": "A unique identifier assigned to this diagnostic report in LIS. diagnostic report identifier MUST follow the following algorithm: [organisation code][resource id][resource version][effective year][unique sequence of 10 digits within organisation] | Unikāls testēšanas pārskata identifikators LIS. Testēšanas pārskata identifikatoram jāatbilst sekojošam veidošanas algoritmam: [organizācijas kods][resursa id][resursa versija][testēšanas pārskata gads][unikāla 10 ciparu kombinācija organizācijas ietvaros]", "min": 1, "example": [ { "label": "LabDiagnosticReportUniqueId", "valueString": "010068303.1.1.1.0.0000000001" } ], "mustSupport": true }, { "id": "DiagnosticReport.basedOn", "path": "DiagnosticReport.basedOn", "min": 1, "max": "1", "type": [ { "code": "Reference", "targetProfile": [ "http://hl7.org/fhir/StructureDefinition/ServiceRequest" ], "aggregation": [ "referenced" ] } ], "mustSupport": true }, { "id": "DiagnosticReport.basedOn.reference", "path": "DiagnosticReport.basedOn.reference", "short": "Reference to system Service Request Id", "min": 1, "mustSupport": true }, { "id": "DiagnosticReport.status", "path": "DiagnosticReport.status", "binding": { "extension": [ { "url": "http://hl7.org/fhir/StructureDefinition/elementdefinition-bindingName", "valueString": "DiagnosticReportStatus" } ], "strength": "required", "valueSet": "http://kleintech.software/fhir/terminology/1.3.6.1.4.1.38760.2.803" } }, { "id": "DiagnosticReport.code", "path": "DiagnosticReport.code", "mustSupport": true }, { "id": "DiagnosticReport.code.coding", "path": "DiagnosticReport.code.coding", "min": 1, "max": "1", "fixedCoding": { "system": "http://kleintech.software/fhir/terminology/1.3.6.1.4.1.38760.2.809", "code": "1.3.6.1.4.1.38760.FHIR.1.1.1", "display": "Testēšanas pārskats" }, "mustSupport": true }, { "id": "DiagnosticReport.subject", "path": "DiagnosticReport.subject", "min": 1, "type": [ { "code": "Reference", "targetProfile": [ "http://hl7.org/fhir/StructureDefinition/Patient" ], "aggregation": [ "referenced" ] } ], "mustSupport": true }, { "id": "DiagnosticReport.subject.reference", "path": "DiagnosticReport.subject.reference", "short": "Patient system Id in EHR", "min": 1, "mustSupport": true }, { "id": "DiagnosticReport.effective[x]", "path": "DiagnosticReport.effective[x]", "short": "Diagnostic Report validation time", "definition": "As Laboratory Diagnostic Report contains observations of specimen collected on different dates or in different time and same specimen might be retested later on, no accurate specimen collection datetime is applicable. The approval/ validation datetime will be used instead.", "min": 1, "mustSupport": true }, { "id": "DiagnosticReport.issued", "path": "DiagnosticReport.issued", "definition": "The date and time that this version of the report was made available to LAB IS, typically after the report was reviewed and verified; in case of historical data effective and issued datetime may differ by years.", "min": 1, "mustSupport": true }, { "id": "DiagnosticReport.performer", "path": "DiagnosticReport.performer", "definition": "The diagnostic service that is responsible for issuing the report.", "min": 1, "max": "1", "type": [ { "code": "Reference", "targetProfile": [ "http://hl7.org/fhir/StructureDefinition/Organization" ], "aggregation": [ "referenced" ] } ], "mustSupport": true }, { "id": "DiagnosticReport.performer.reference", "path": "DiagnosticReport.performer.reference", "min": 1, "mustSupport": true }, { "id": "DiagnosticReport.resultsInterpreter", "path": "DiagnosticReport.resultsInterpreter", "min": 1, "type": [ { "code": "Reference", "targetProfile": [ "http://hl7.org/fhir/StructureDefinition/PractitionerRole" ], "aggregation": [ "referenced" ] } ], "mustSupport": true }, { "id": "DiagnosticReport.resultsInterpreter.reference", "path": "DiagnosticReport.resultsInterpreter.reference", "min": 1, "mustSupport": true }, { "id": "DiagnosticReport.specimen", "path": "DiagnosticReport.specimen", "min": 1, "mustSupport": true }, { "id": "DiagnosticReport.specimen.reference", "path": "DiagnosticReport.specimen.reference", "min": 1, "mustSupport": true }, { "id": "DiagnosticReport.result", "path": "DiagnosticReport.result", "min": 1 }, { "id": "DiagnosticReport.result.reference", "path": "DiagnosticReport.result.reference", "min": 1, "mustSupport": true }, { "id": "DiagnosticReport.imagingStudy", "path": "DiagnosticReport.imagingStudy", "max": "0" }, { "id": "DiagnosticReport.media", "path": "DiagnosticReport.media", "short": "Logotypes associated with this report", "definition": "Referemce uz laboratorijas logotipu un LATAK logotipts, ja nepieciešams.", "min": 1 }, { "id": "DiagnosticReport.media.link", "path": "DiagnosticReport.media.link", "mustSupport": true }, { "id": "DiagnosticReport.media.link.reference", "path": "DiagnosticReport.media.link.reference", "min": 1, "mustSupport": true }, { "id": "DiagnosticReport.presentedForm", "path": "DiagnosticReport.presentedForm", "mustSupport": true }, { "id": "DiagnosticReport.presentedForm.contentType", "path": "DiagnosticReport.presentedForm.contentType", "definition": "\"application/pdf\" is expected.", "min": 1, "fixedCode": "application/pdf" }, { "id": "DiagnosticReport.presentedForm.language", "path": "DiagnosticReport.presentedForm.language", "min": 1, "mustSupport": true, "binding": { "extension": [ { "url": "http://hl7.org/fhir/StructureDefinition/elementdefinition-maxValueSet", "valueCanonical": "http://hl7.org/fhir/ValueSet/all-languages" }, { "url": "http://hl7.org/fhir/StructureDefinition/elementdefinition-bindingName", "valueString": "Language" }, { "url": "http://hl7.org/fhir/StructureDefinition/elementdefinition-isCommonBinding", "valueBoolean": true } ], "strength": "required", "valueSet": "http://kleintech.software/fhir/terminology/1.3.6.1.4.1.38760.2.2" } }, { "id": "DiagnosticReport.presentedForm.data", "path": "DiagnosticReport.presentedForm.data", "min": 1, "mustSupport": true }, { "id": "DiagnosticReport.presentedForm.title", "path": "DiagnosticReport.presentedForm.title", "min": 1, "mustSupport": true } ] } }
Izmeklējumu pieprasījums - pacienta iniciatīva
ServiceRequest | I | ServiceRequest | There are no (further) constraints on this element Element IdServiceRequest A request for a service to be performed Alternate namesdiagnostic request, referral, referral request, transfer of care request DefinitionA record of a request for service such as diagnostic investigations, treatments, or operations to be performed.
| |
identifier | S Σ | 1..1 | Identifier | Element IdServiceRequest.identifier Identifiers assigned to this order DefinitionIdentifiers assigned to this order instance by the order fulfiller - Laboratory. | Identifikators, ko piešķir pieprasījuma izpildītājs - laboratorija. The identifier.type element is used to distinguish between the identifiers assigned by the orderer (known as the 'Placer' in HL7 v2) and the producer of the observations in response to the order (known as the 'Filler' in HL7 v2). For further discussion and examples see the resource notes section below.
|
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdServiceRequest.identifier.use 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 . IdentifierUse (required)Constraints
|
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdServiceRequest.identifier.type 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 | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdServiceRequest.identifier.system 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.
General http://www.acme.com/identifiers/patient Mappings
|
value | S Σ | 1..1 | string | Element IdServiceRequest.identifier.value The value that is unique DefinitionA unique identifier assigned to this service request in LIS. Service request identifier MUST follow the following algorithm: [organisation code][resource id][resource version][effective year][unique sequence of 10 digits within organisation] | Unikāls pakalpojumu pieprasījuma identifikators LIS. pakalpojumu pieprasījuma identifikatoram jāatbilst sekojošam veidošanas algoritmam: [organizācijas kods][resursa id][resursa versija][pieprasījuma gads][unikāla 10 ciparu kombinācija organizācijas ietvaros] 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.
40 General 123456 Laboratory Service Request Id 010068303.1.2.1.0.2022.0000000001 Mappings
|
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdServiceRequest.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
|
assigner | Σ I | 0..1 | Reference(Organization) | There are no (further) constraints on this element Element IdServiceRequest.identifier.assigner 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.
|
instantiatesCanonical | Σ | 0..* | canonical(ActivityDefinition | PlanDefinition) | There are no (further) constraints on this element Element IdServiceRequest.instantiatesCanonical Instantiates FHIR protocol or definition DefinitionThe URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this ServiceRequest. Note: This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number. canonical(ActivityDefinition | PlanDefinition) Constraints
|
instantiatesUri | Σ | 0..* | uri | There are no (further) constraints on this element Element IdServiceRequest.instantiatesUri Instantiates external protocol or definition DefinitionThe URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this ServiceRequest. This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.
|
basedOn | Σ I | 0..* | Reference(CarePlan | ServiceRequest | MedicationRequest) | There are no (further) constraints on this element Element IdServiceRequest.basedOn What request fulfills Alternate namesfulfills DefinitionPlan/proposal/order fulfilled by this request. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(CarePlan | ServiceRequest | MedicationRequest) Constraints
|
replaces | Σ I | 0..* | Reference(ServiceRequest) | There are no (further) constraints on this element Element IdServiceRequest.replaces What request replaces Alternate namessupersedes, prior, renewed order DefinitionThe request takes the place of the referenced completed or terminated request(s). References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
requisition | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdServiceRequest.requisition Composite Request ID Alternate namesgrouperId, groupIdentifier DefinitionA shared identifier common to all service requests that were authorized more or less simultaneously by a single author, representing the composite or group identifier. Some business processes need to know if multiple items were ordered as part of the same "requisition" for billing or other purposes. Requests are linked either by a "basedOn" relationship (i.e. one request is fulfilling another) or by having a common requisition. Requests that are part of the same requisition are generally treated independently from the perspective of changing their state or maintaining them after initial creation.
|
status | S Σ ?! | 1..1 | codeBinding | Element IdServiceRequest.status draft | active | on-hold | revoked | completed | entered-in-error | unknown DefinitionThe status of the order. | Pieprasījuma biznesa statuss. The status is generally fully in the control of the requester - they determine whether the order is draft or active and, after it has been activated, competed, cancelled or suspended. States relating to the activities of the performer are reflected on either the corresponding event (see Event Pattern for general discussion) or using the Task resource. The status of a service order. http://kleintech.software/fhir/terminology/1.3.6.1.4.1.38760.2.807 (required)Constraints
|
intent | S Σ ?! | 1..1 | codeBindingFixed Value | Element IdServiceRequest.intent proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option DefinitionWhether the request is a proposal, plan, an original order or a reflex order. This element is labeled as a modifier because the intent alters when and how the resource is actually applicable. The kind of service request. RequestIntent (required)Constraints
original-order
|
category | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element IdServiceRequest.category Classification of service DefinitionA code that classifies the service for searching, sorting and display purposes (e.g. "Surgical Procedure"). Used for filtering what service request are retrieved and displayed. There may be multiple axis of categorization depending on the context or use case for retrieving or displaying the resource. The level of granularity is defined by the category concepts in the value set. Classification of the requested service. ServiceRequestCategoryCodes (example)Constraints
|
priority | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element IdServiceRequest.priority routine | urgent | asap | stat DefinitionIndicates how quickly the ServiceRequest should be addressed with respect to other requests. Note that FHIR strings SHALL NOT exceed 1MB in size Identifies the level of importance to be assigned to actioning the request. RequestPriority (required)Constraints
|
doNotPerform | Σ ?! | 0..1 | boolean | There are no (further) constraints on this element Element IdServiceRequest.doNotPerform True if service/procedure should not be performed DefinitionSet this to true if the record is saying that the service/procedure should NOT be performed. Used for do not ambulate, do not elevate head of bed, do not flush NG tube, do not take blood pressure on a certain arm, etc. In general, only the code and timeframe will be present, though occasional additional qualifiers such as body site or even performer could be included to narrow the scope of the prohibition. If the ServiceRequest.code and ServiceRequest.doNotPerform both contain negation, that will reinforce prohibition and should not have a double negative interpretation.
|
code | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdServiceRequest.code What is being requested/ordered Alternate namesservice requested DefinitionA code that identifies a particular service (i.e., procedure, diagnostic investigation, or panel of investigations) that have been requested. Many laboratory and radiology procedure codes embed the specimen/organ system in the test order name, for example, serum or serum/plasma glucose, or a chest x-ray. The specimen might not be recorded separately from the test code. Codes for tests or services that can be carried out by a designated individual, organization or healthcare service. For laboratory, LOINC is (preferred)[http://build.fhir.org/terminologies.html#preferred] and a valueset using LOINC Order codes is available [here](valueset-diagnostic-requests.html). ProcedureCodes(SNOMEDCT) (example)Constraints
|
orderDetail | Σ I | 0..* | CodeableConcept | There are no (further) constraints on this element Element IdServiceRequest.orderDetail Additional order information Alternate namesdetailed instructions DefinitionAdditional details and instructions about the how the services are to be delivered. For example, and order for a urinary catheter may have an order detail for an external or indwelling catheter, or an order for a bandage may require additional instructions specifying how the bandage should be applied. For information from the medical record intended to support the delivery of the requested services, use the Codified order entry details which are based on order context. ServiceRequestOrderDetailsCodes (example)Constraints
|
quantity[x] | Σ | 0..1 | There are no (further) constraints on this element Element IdServiceRequest.quantity[x] Service amount DefinitionAn amount of service being requested which can be a quantity ( for example $1,500 home modification), a ratio ( for example, 20 half day visits per month), or a range (2.0 to 1.8 Gy per fraction). When ordering a service the number of service items may need to be specified separately from the the service item.
| |
quantityQuantity | Quantity | There are no (further) constraints on this element Data Type | ||
quantityRatio | Ratio | There are no (further) constraints on this element Data Type | ||
quantityRange | Range | There are no (further) constraints on this element Data Type | ||
subject | S Σ I | 1..1 | Reference(Patient) | Element IdServiceRequest.subject Individual or Entity the service is ordered for DefinitionOn whom or what the service is to be performed. This is usually a human patient, but can also be requested on animals, groups of humans or animals, devices such as dialysis machines, or even locations (typically for environmental scans). References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Allowed aggregation: referenced Constraints
|
reference | S Σ I | 1..1 | string | Element IdServiceRequest.subject.reference Reference to patient in EHR DefinitionPatient system id retrieved from EHR by patient type and patient id | Pacienta sistēmas identifikators, kas tika saņemts no EVK ar pieprasījumu pēc pacienta tipa un pacienta id. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdServiceRequest.subject.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
|
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdServiceRequest.subject.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdServiceRequest.subject.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
encounter | Σ I | 0..1 | Reference(Encounter) | There are no (further) constraints on this element Element IdServiceRequest.encounter Encounter in which the request was created Alternate namescontext DefinitionAn encounter that provides additional information about the healthcare context in which this request is made. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
occurrence[x] | Σ | 0..1 | There are no (further) constraints on this element Element IdServiceRequest.occurrence[x] When service should occur Alternate namesschedule DefinitionThe date/time at which the requested service should occur.
| |
occurrenceDateTime | dateTime | There are no (further) constraints on this element Data Type | ||
occurrencePeriod | Period | There are no (further) constraints on this element Data Type | ||
occurrenceTiming | Timing | There are no (further) constraints on this element Data Type | ||
asNeeded[x] | Σ | 0..1 | There are no (further) constraints on this element Element IdServiceRequest.asNeeded[x] Preconditions for service DefinitionIf a CodeableConcept is present, it indicates the pre-condition for performing the service. For example "pain", "on flare-up", etc. A coded concept identifying the pre-condition that should hold prior to performing a procedure. For example "pain", "on flare-up", etc. SNOMEDCTMedicationAsNeededReasonCodes (example)Constraints
| |
asNeededBoolean | boolean | There are no (further) constraints on this element Data Type | ||
asNeededCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data Type | ||
authoredOn | S Σ | 1..1 | dateTime | Element IdServiceRequest.authoredOn Pieprasījuma reģistrācijas datums Alternate namesorderedOn DefinitionWhen the request transitioned to being actionable. | Kad pieprasījums kļuva aktīvs.
|
requester | S Σ I | 1..1 | Reference(Patient) | Element IdServiceRequest.requester Who/what is requesting service Alternate namesauthor, orderer DefinitionThe individual who initiated the request and has responsibility for its activation. This not the dispatcher, but rather who is the authorizer. This element is not intended to handle delegation which would generally be managed through the Provenance resource. Allowed aggregation: referenced Constraints
|
reference | S Σ I | 1..1 | string | Element IdServiceRequest.requester.reference Reference to patient in EHR DefinitionPatient system id retrieved from EHR by patient type and patient id | Pacienta sistēmas identifikators, kas tika saņemts no EVK ar pieprasījumu pēc pacienta tipa un pacienta id. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdServiceRequest.requester.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
|
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdServiceRequest.requester.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdServiceRequest.requester.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
performerType | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdServiceRequest.performerType Performer role Alternate namesspecialty DefinitionDesired type of performer for doing the requested service. This is a role, not a participation type. In other words, does not describe the task but describes the capacity. For example, “compounding pharmacy”, “psychiatrist” or “internal referral”. Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc. ParticipantRoles (example)Constraints
|
performer | Σ I | 0..* | Reference(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson) | There are no (further) constraints on this element Element IdServiceRequest.performer Requested performer Alternate namesrequest recipient DefinitionThe desired performer for doing the requested service. For example, the surgeon, dermatopathologist, endoscopist, etc. If multiple performers are present, it is interpreted as a list of alternative performers without any preference regardless of order. If order of preference is needed use the request-performerOrder extension. Use CareTeam to represent a group of performers (for example, Practitioner A and Practitioner B). Reference(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson) Constraints
|
locationCode | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element IdServiceRequest.locationCode Requested location DefinitionThe preferred location(s) where the procedure should actually happen in coded or free text form. E.g. at home or nursing day care center. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. A location type where services are delivered. v3.ServiceDeliveryLocationRoleType (example)Constraints
|
locationReference | Σ I | 0..* | Reference(Location) | There are no (further) constraints on this element Element IdServiceRequest.locationReference Requested location DefinitionA reference to the the preferred location(s) where the procedure should actually happen. E.g. at home or nursing day care center. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
reasonCode | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element IdServiceRequest.reasonCode Explanation/Justification for procedure or service DefinitionAn explanation or justification for why this service is being requested in coded or textual form. This is often for billing purposes. May relate to the resources referred to in This element represents why the referral is being made and may be used to decide how the service will be performed, or even if it will be performed at all. Use Diagnosis or problem codes justifying the reason for requesting the service investigation. ProcedureReasonCodes (example)Constraints
|
reasonReference | Σ I | 0..* | Reference(Condition | Observation | DiagnosticReport | DocumentReference) | There are no (further) constraints on this element Element IdServiceRequest.reasonReference Explanation/Justification for service or service DefinitionIndicates another resource that provides a justification for why this service is being requested. May relate to the resources referred to in This element represents why the referral is being made and may be used to decide how the service will be performed, or even if it will be performed at all. To be as specific as possible, a reference to Observation or Condition should be used if available. Otherwise when referencing DiagnosticReport it should contain a finding in Reference(Condition | Observation | DiagnosticReport | DocumentReference) Constraints
|
insurance | I | 0..* | Reference(Coverage | ClaimResponse) | There are no (further) constraints on this element Element IdServiceRequest.insurance Associated insurance coverage DefinitionInsurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be needed for delivering the requested service. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Coverage | ClaimResponse) Constraints
|
supportingInfo | I | 0..* | Reference(Resource) | There are no (further) constraints on this element Element IdServiceRequest.supportingInfo Additional clinical information Alternate namesAsk at order entry question, AOE DefinitionAdditional clinical information about the patient or specimen that may influence the services or their interpretations. This information includes diagnosis, clinical findings and other observations. In laboratory ordering these are typically referred to as "ask at order entry questions (AOEs)". This includes observations explicitly requested by the producer (filler) to provide context or supporting information needed to complete the order. For example, reporting the amount of inspired oxygen for blood gas measurements. To represent information about how the services are to be delivered use the
|
specimen | Σ I | 0..* | Reference(Specimen) | There are no (further) constraints on this element Element IdServiceRequest.specimen Procedure Samples DefinitionOne or more specimens that the laboratory procedure will use. Many diagnostic procedures need a specimen, but the request itself is not actually about the specimen. This element is for when the diagnostic is requested on already existing specimens and the request points to the specimen it applies to. Conversely, if the request is entered first with an unknown specimen, then the Specimen resource points to the ServiceRequest.
|
bodySite | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element IdServiceRequest.bodySite Location on Body Alternate nameslocation DefinitionAnatomic location where the procedure should be performed. This is the target site. Knowing where the procedure is performed is important for tracking if multiple sites are possible. Only used if not implicit in the code found in ServiceRequest.code. If the use case requires BodySite to be handled as a separate resource instead of an inline coded element (e.g. to identify and track separately) then use the standard extension procedure-targetBodyStructure. Codes describing anatomical locations. May include laterality. SNOMEDCTBodyStructures (example)Constraints
|
note | 0..* | Annotation | There are no (further) constraints on this element Element IdServiceRequest.note Comments DefinitionAny other notes and comments made about the service request. For example, internal billing notes. For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible).
| |
patientInstruction | Σ | 0..1 | string | There are no (further) constraints on this element Element IdServiceRequest.patientInstruction Patient or consumer-oriented instructions DefinitionInstructions in terms that are understood by the patient or consumer. Note that FHIR strings SHALL NOT exceed 1MB in size
|
relevantHistory | I | 0..* | Reference(Provenance) | There are no (further) constraints on this element Element IdServiceRequest.relevantHistory Request provenance DefinitionKey events in the history of the request. This might not include provenances for all versions of the request – only those deemed “relevant” or important. This SHALL NOT include the Provenance associated with this current version of the resource. (If that provenance is deemed to be a “relevant” change, it will need to be added as part of a later update. Until then, it can be queried directly as the Provenance that points to this version using _revinclude All Provenances should have some historical version of this Request as their subject.
|
JSON struktūra:
{ "resourceType": "StructureDefinition", "id": "1.3.6.1.4.1.38760.FHIR.1.2.1", "url": "https://example.org/fhir/StructureDefinition/LaboratoryServiceRequest", "name": "LaboratoryServiceRequest", "status": "draft", "description": "Pakalpojumu pieprasījums, kuru iniciē pacients. Gadījums, kad pacientam nav ārstējošā ārsta veidota nosūtījuma.", "fhirVersion": "4.0.1", "kind": "resource", "abstract": false, "type": "ServiceRequest", "baseDefinition": "http://hl7.org/fhir/StructureDefinition/ServiceRequest", "derivation": "constraint", "differential": { "element": [ { "id": "ServiceRequest.identifier", "path": "ServiceRequest.identifier", "definition": "Identifiers assigned to this order instance by the order fulfiller - Laboratory. | Identifikators, ko piešķir pieprasījuma izpildītājs - laboratorija.", "min": 1, "max": "1", "mustSupport": true }, { "id": "ServiceRequest.identifier.value", "path": "ServiceRequest.identifier.value", "definition": "A unique identifier assigned to this service request in LIS. Service request identifier MUST follow the following algorithm: [organisation code][resource id][resource version][effective year][unique sequence of 10 digits within organisation] | Unikāls pakalpojumu pieprasījuma identifikators LIS. pakalpojumu pieprasījuma identifikatoram jāatbilst sekojošam veidošanas algoritmam: [organizācijas kods][resursa id][resursa versija][pieprasījuma gads][unikāla 10 ciparu kombinācija organizācijas ietvaros]", "min": 1, "example": [ { "label": "Laboratory Service Request Id", "valueString": "010068303.1.2.1.0.2022.0000000001" } ], "maxLength": 40, "mustSupport": true }, { "id": "ServiceRequest.status", "path": "ServiceRequest.status", "definition": "The status of the order. | Pieprasījuma biznesa statuss.", "mustSupport": true, "binding": { "extension": [ { "url": "http://hl7.org/fhir/StructureDefinition/elementdefinition-bindingName", "valueString": "ServiceRequestStatus" } ], "strength": "required", "valueSet": "http://kleintech.software/fhir/terminology/1.3.6.1.4.1.38760.2.807" } }, { "id": "ServiceRequest.intent", "path": "ServiceRequest.intent", "fixedCode": "original-order", "mustSupport": true }, { "id": "ServiceRequest.subject", "path": "ServiceRequest.subject", "type": [ { "code": "Reference", "targetProfile": [ "http://hl7.org/fhir/StructureDefinition/Patient" ], "aggregation": [ "referenced" ] } ], "mustSupport": true }, { "id": "ServiceRequest.subject.reference", "path": "ServiceRequest.subject.reference", "short": "Reference to patient in EHR", "definition": "Patient system id retrieved from EHR by patient type and patient id | Pacienta sistēmas identifikators, kas tika saņemts no EVK ar pieprasījumu pēc pacienta tipa un pacienta id.", "min": 1, "mustSupport": true }, { "id": "ServiceRequest.authoredOn", "path": "ServiceRequest.authoredOn", "short": "Pieprasījuma reģistrācijas datums", "definition": "When the request transitioned to being actionable. | Kad pieprasījums kļuva aktīvs.", "min": 1, "mustSupport": true }, { "id": "ServiceRequest.requester", "path": "ServiceRequest.requester", "min": 1, "type": [ { "code": "Reference", "targetProfile": [ "http://hl7.org/fhir/StructureDefinition/Patient" ], "aggregation": [ "referenced" ] } ], "mustSupport": true }, { "id": "ServiceRequest.requester.reference", "path": "ServiceRequest.requester.reference", "short": "Reference to patient in EHR", "definition": "Patient system id retrieved from EHR by patient type and patient id | Pacienta sistēmas identifikators, kas tika saņemts no EVK ar pieprasījumu pēc pacienta tipa un pacienta id.", "min": 1, "mustSupport": true } ] } }
Izmeklējumu pieprasījums - papīra nosūtījums
ServiceRequest | I | ServiceRequest | There are no (further) constraints on this element Element IdServiceRequest A request for a service to be performed Alternate namesdiagnostic request, referral, referral request, transfer of care request DefinitionA record of a request for service such as diagnostic investigations, treatments, or operations to be performed.
| |
identifier | S Σ | 1..1 | Identifier | Element IdServiceRequest.identifier Identifiers assigned to this order DefinitionIdentifiers assigned to this order instance by the order fulfiller - Laboratory. | Identifikators, ko piešķir pieprasījuma izpildītājs - laboratorija. The identifier.type element is used to distinguish between the identifiers assigned by the orderer (known as the 'Placer' in HL7 v2) and the producer of the observations in response to the order (known as the 'Filler' in HL7 v2). For further discussion and examples see the resource notes section below.
|
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdServiceRequest.identifier.use 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 . IdentifierUse (required)Constraints
|
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdServiceRequest.identifier.type 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 | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdServiceRequest.identifier.system 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.
General http://www.acme.com/identifiers/patient Mappings
|
value | S Σ | 1..1 | string | Element IdServiceRequest.identifier.value The value that is unique DefinitionA unique identifier assigned to this service request in LIS. Service request identifier MUST follow the following algorithm: [organisation code][resource id][resource version][effective year][unique sequence of 10 digits within organisation] | Unikāls pakalpojumu pieprasījuma identifikators LIS. pakalpojumu pieprasījuma identifikatoram jāatbilst sekojošam veidošanas algoritmam: [organizācijas kods][resursa id][resursa versija][pieprasījuma gads][unikāla 10 ciparu kombinācija organizācijas ietvaros] 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.
40 General 123456 Paper Service Request Id 010068303.1.2.2.0.2022.0000000001 Mappings
|
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdServiceRequest.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
|
assigner | Σ I | 0..1 | Reference(Organization) | There are no (further) constraints on this element Element IdServiceRequest.identifier.assigner 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.
|
instantiatesCanonical | Σ | 0..* | canonical(ActivityDefinition | PlanDefinition) | There are no (further) constraints on this element Element IdServiceRequest.instantiatesCanonical Instantiates FHIR protocol or definition DefinitionThe URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this ServiceRequest. Note: This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number. canonical(ActivityDefinition | PlanDefinition) Constraints
|
instantiatesUri | Σ | 0..* | uri | There are no (further) constraints on this element Element IdServiceRequest.instantiatesUri Instantiates external protocol or definition DefinitionThe URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this ServiceRequest. This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.
|
basedOn | Σ I | 0..* | Reference(CarePlan | ServiceRequest | MedicationRequest) | There are no (further) constraints on this element Element IdServiceRequest.basedOn What request fulfills Alternate namesfulfills DefinitionPlan/proposal/order fulfilled by this request. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(CarePlan | ServiceRequest | MedicationRequest) Constraints
|
replaces | Σ I | 0..* | Reference(ServiceRequest) | There are no (further) constraints on this element Element IdServiceRequest.replaces What request replaces Alternate namessupersedes, prior, renewed order DefinitionThe request takes the place of the referenced completed or terminated request(s). References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
requisition | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdServiceRequest.requisition Composite Request ID Alternate namesgrouperId, groupIdentifier DefinitionA shared identifier common to all service requests that were authorized more or less simultaneously by a single author, representing the composite or group identifier. Some business processes need to know if multiple items were ordered as part of the same "requisition" for billing or other purposes. Requests are linked either by a "basedOn" relationship (i.e. one request is fulfilling another) or by having a common requisition. Requests that are part of the same requisition are generally treated independently from the perspective of changing their state or maintaining them after initial creation.
|
status | S Σ ?! | 1..1 | codeBinding | Element IdServiceRequest.status draft | active | on-hold | revoked | completed | entered-in-error | unknown DefinitionThe status of the order. The status is generally fully in the control of the requester - they determine whether the order is draft or active and, after it has been activated, competed, cancelled or suspended. States relating to the activities of the performer are reflected on either the corresponding event (see Event Pattern for general discussion) or using the Task resource. The status of a service order. http://kleintech.software/fhir/terminology/1.3.6.1.4.1.38760.2.807 (required)Constraints
|
intent | S Σ ?! | 1..1 | codeBindingFixed Value | Element IdServiceRequest.intent proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option DefinitionWhether the request is a proposal, plan, an original order or a reflex order. This element is labeled as a modifier because the intent alters when and how the resource is actually applicable. The kind of service request. RequestIntent (required)Constraints
original-order
|
category | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element IdServiceRequest.category Classification of service DefinitionA code that classifies the service for searching, sorting and display purposes (e.g. "Surgical Procedure"). Used for filtering what service request are retrieved and displayed. There may be multiple axis of categorization depending on the context or use case for retrieving or displaying the resource. The level of granularity is defined by the category concepts in the value set. Classification of the requested service. ServiceRequestCategoryCodes (example)Constraints
|
priority | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element IdServiceRequest.priority routine | urgent | asap | stat DefinitionIndicates how quickly the ServiceRequest should be addressed with respect to other requests. Note that FHIR strings SHALL NOT exceed 1MB in size Identifies the level of importance to be assigned to actioning the request. RequestPriority (required)Constraints
|
doNotPerform | Σ ?! | 0..1 | boolean | There are no (further) constraints on this element Element IdServiceRequest.doNotPerform True if service/procedure should not be performed DefinitionSet this to true if the record is saying that the service/procedure should NOT be performed. Used for do not ambulate, do not elevate head of bed, do not flush NG tube, do not take blood pressure on a certain arm, etc. In general, only the code and timeframe will be present, though occasional additional qualifiers such as body site or even performer could be included to narrow the scope of the prohibition. If the ServiceRequest.code and ServiceRequest.doNotPerform both contain negation, that will reinforce prohibition and should not have a double negative interpretation.
|
code | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdServiceRequest.code What is being requested/ordered Alternate namesservice requested DefinitionA code that identifies a particular service (i.e., procedure, diagnostic investigation, or panel of investigations) that have been requested. Many laboratory and radiology procedure codes embed the specimen/organ system in the test order name, for example, serum or serum/plasma glucose, or a chest x-ray. The specimen might not be recorded separately from the test code. Codes for tests or services that can be carried out by a designated individual, organization or healthcare service. For laboratory, LOINC is (preferred)[http://build.fhir.org/terminologies.html#preferred] and a valueset using LOINC Order codes is available [here](valueset-diagnostic-requests.html). ProcedureCodes(SNOMEDCT) (example)Constraints
|
orderDetail | Σ I | 0..* | CodeableConcept | There are no (further) constraints on this element Element IdServiceRequest.orderDetail Additional order information Alternate namesdetailed instructions DefinitionAdditional details and instructions about the how the services are to be delivered. For example, and order for a urinary catheter may have an order detail for an external or indwelling catheter, or an order for a bandage may require additional instructions specifying how the bandage should be applied. For information from the medical record intended to support the delivery of the requested services, use the Codified order entry details which are based on order context. ServiceRequestOrderDetailsCodes (example)Constraints
|
quantity[x] | Σ | 0..1 | There are no (further) constraints on this element Element IdServiceRequest.quantity[x] Service amount DefinitionAn amount of service being requested which can be a quantity ( for example $1,500 home modification), a ratio ( for example, 20 half day visits per month), or a range (2.0 to 1.8 Gy per fraction). When ordering a service the number of service items may need to be specified separately from the the service item.
| |
quantityQuantity | Quantity | There are no (further) constraints on this element Data Type | ||
quantityRatio | Ratio | There are no (further) constraints on this element Data Type | ||
quantityRange | Range | There are no (further) constraints on this element Data Type | ||
subject | S Σ I | 1..1 | Reference(Patient) | Element IdServiceRequest.subject Individual or Entity the service is ordered for DefinitionOn whom or what the service is to be performed. This is usually a human patient, but can also be requested on animals, groups of humans or animals, devices such as dialysis machines, or even locations (typically for environmental scans). References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Allowed aggregation: referenced Constraints
|
reference | S Σ I | 1..1 | string | Element IdServiceRequest.subject.reference Reference to patient in EHR DefinitionPatient system id retrieved from EHR by patient type and patient id | Pacienta sistēmas identifikators, kas tika saņemts no EVK ar pieprasījumu pēc pacienta tipa un pacienta id. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdServiceRequest.subject.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
|
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdServiceRequest.subject.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdServiceRequest.subject.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
encounter | Σ I | 0..1 | Reference(Encounter) | There are no (further) constraints on this element Element IdServiceRequest.encounter Encounter in which the request was created Alternate namescontext DefinitionAn encounter that provides additional information about the healthcare context in which this request is made. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
occurrence[x] | Σ | 0..1 | There are no (further) constraints on this element Element IdServiceRequest.occurrence[x] When service should occur Alternate namesschedule DefinitionThe date/time at which the requested service should occur.
| |
occurrenceDateTime | dateTime | There are no (further) constraints on this element Data Type | ||
occurrencePeriod | Period | There are no (further) constraints on this element Data Type | ||
occurrenceTiming | Timing | There are no (further) constraints on this element Data Type | ||
asNeeded[x] | Σ | 0..1 | There are no (further) constraints on this element Element IdServiceRequest.asNeeded[x] Preconditions for service DefinitionIf a CodeableConcept is present, it indicates the pre-condition for performing the service. For example "pain", "on flare-up", etc. A coded concept identifying the pre-condition that should hold prior to performing a procedure. For example "pain", "on flare-up", etc. SNOMEDCTMedicationAsNeededReasonCodes (example)Constraints
| |
asNeededBoolean | boolean | There are no (further) constraints on this element Data Type | ||
asNeededCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data Type | ||
authoredOn | S Σ | 1..1 | dateTime | Element IdServiceRequest.authoredOn Pieprasījuma reģistrācijas datums LIS Alternate namesorderedOn DefinitionWhen the request transitioned to being actionable. | Kad pieprasījums kļuva pieejams un aktīvs LIS.
|
requester | S Σ I | 1..1 | Reference(Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | Device) | Element IdServiceRequest.requester Nosūtītājs Alternate namesauthor, orderer DefinitionThe individual who initiated the request and has responsibility for its activation. | Nosūtītājs. Papīra nosūtījuma ievades gadījumā nosūtītāja darbavietas kodu precīzi noteikt nav iespējams, līdz ar jānorāda reference uz ĀP un ĀI, kuras ir noradītas papīra nosūtījumā. This not the dispatcher, but rather who is the authorizer. This element is not intended to handle delegation which would generally be managed through the Provenance resource. Reference(Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | Device) Sliced:Unordered, Open, by type(Value) Constraints
|
RequestingDoctor | S Σ I | 1..1 | Reference(Practitioner) | Element IdServiceRequest.requester:RequestingDoctor ĀP sistēmas id Alternate namesauthor, orderer DefinitionThe individual who initiated the request and has responsibility for its activation. | ĀP sistēmas id This not the dispatcher, but rather who is the authorizer. This element is not intended to handle delegation which would generally be managed through the Provenance resource. Allowed aggregation: referenced Constraints
|
reference | S Σ I | 1..1 | string | Element IdServiceRequest.requester:RequestingDoctor.reference ĀP sistēmas id DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
type | S Σ | 1..1 | uriBindingFixed Value | Element IdServiceRequest.requester:RequestingDoctor.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
Doctor
|
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdServiceRequest.requester:RequestingDoctor.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdServiceRequest.requester:RequestingDoctor.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
RequestingOrganisation | S Σ I | 1..1 | Reference(Organization) | Element IdServiceRequest.requester:RequestingOrganisation Who/what is requesting service Alternate namesauthor, orderer DefinitionThe individual who initiated the request and has responsibility for its activation. This not the dispatcher, but rather who is the authorizer. This element is not intended to handle delegation which would generally be managed through the Provenance resource. Allowed aggregation: referenced Constraints
|
reference | S Σ I | 1..1 | string | Element IdServiceRequest.requester:RequestingOrganisation.reference Organisation system id | Sistēmas organizācijas kods DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
type | S Σ | 1..1 | uriBindingFixed Value | Element IdServiceRequest.requester:RequestingOrganisation.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
Organisation
|
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdServiceRequest.requester:RequestingOrganisation.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdServiceRequest.requester:RequestingOrganisation.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
performerType | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdServiceRequest.performerType Performer role Alternate namesspecialty DefinitionDesired type of performer for doing the requested service. This is a role, not a participation type. In other words, does not describe the task but describes the capacity. For example, “compounding pharmacy”, “psychiatrist” or “internal referral”. Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc. ParticipantRoles (example)Constraints
|
performer | Σ I | 0..* | Reference(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson) | There are no (further) constraints on this element Element IdServiceRequest.performer Requested performer Alternate namesrequest recipient DefinitionThe desired performer for doing the requested service. For example, the surgeon, dermatopathologist, endoscopist, etc. If multiple performers are present, it is interpreted as a list of alternative performers without any preference regardless of order. If order of preference is needed use the request-performerOrder extension. Use CareTeam to represent a group of performers (for example, Practitioner A and Practitioner B). Reference(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson) Constraints
|
locationCode | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element IdServiceRequest.locationCode Requested location DefinitionThe preferred location(s) where the procedure should actually happen in coded or free text form. E.g. at home or nursing day care center. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. A location type where services are delivered. v3.ServiceDeliveryLocationRoleType (example)Constraints
|
locationReference | Σ I | 0..* | Reference(Location) | There are no (further) constraints on this element Element IdServiceRequest.locationReference Requested location DefinitionA reference to the the preferred location(s) where the procedure should actually happen. E.g. at home or nursing day care center. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
reasonCode | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element IdServiceRequest.reasonCode Explanation/Justification for procedure or service DefinitionAn explanation or justification for why this service is being requested in coded or textual form. This is often for billing purposes. May relate to the resources referred to in This element represents why the referral is being made and may be used to decide how the service will be performed, or even if it will be performed at all. Use Diagnosis or problem codes justifying the reason for requesting the service investigation. ProcedureReasonCodes (example)Constraints
|
reasonReference | Σ I | 0..* | Reference(Condition | Observation | DiagnosticReport | DocumentReference) | There are no (further) constraints on this element Element IdServiceRequest.reasonReference Explanation/Justification for service or service DefinitionIndicates another resource that provides a justification for why this service is being requested. May relate to the resources referred to in This element represents why the referral is being made and may be used to decide how the service will be performed, or even if it will be performed at all. To be as specific as possible, a reference to Observation or Condition should be used if available. Otherwise when referencing DiagnosticReport it should contain a finding in Reference(Condition | Observation | DiagnosticReport | DocumentReference) Constraints
|
insurance | I | 0..* | Reference(Coverage | ClaimResponse) | There are no (further) constraints on this element Element IdServiceRequest.insurance Associated insurance coverage DefinitionInsurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be needed for delivering the requested service. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Coverage | ClaimResponse) Constraints
|
supportingInfo | I | 0..* | Reference(Resource) | There are no (further) constraints on this element Element IdServiceRequest.supportingInfo Additional clinical information Alternate namesAsk at order entry question, AOE DefinitionAdditional clinical information about the patient or specimen that may influence the services or their interpretations. This information includes diagnosis, clinical findings and other observations. In laboratory ordering these are typically referred to as "ask at order entry questions (AOEs)". This includes observations explicitly requested by the producer (filler) to provide context or supporting information needed to complete the order. For example, reporting the amount of inspired oxygen for blood gas measurements. To represent information about how the services are to be delivered use the
|
specimen | Σ I | 0..* | Reference(Specimen) | There are no (further) constraints on this element Element IdServiceRequest.specimen Procedure Samples DefinitionOne or more specimens that the laboratory procedure will use. Many diagnostic procedures need a specimen, but the request itself is not actually about the specimen. This element is for when the diagnostic is requested on already existing specimens and the request points to the specimen it applies to. Conversely, if the request is entered first with an unknown specimen, then the Specimen resource points to the ServiceRequest.
|
bodySite | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element IdServiceRequest.bodySite Location on Body Alternate nameslocation DefinitionAnatomic location where the procedure should be performed. This is the target site. Knowing where the procedure is performed is important for tracking if multiple sites are possible. Only used if not implicit in the code found in ServiceRequest.code. If the use case requires BodySite to be handled as a separate resource instead of an inline coded element (e.g. to identify and track separately) then use the standard extension procedure-targetBodyStructure. Codes describing anatomical locations. May include laterality. SNOMEDCTBodyStructures (example)Constraints
|
note | 0..* | Annotation | There are no (further) constraints on this element Element IdServiceRequest.note Comments DefinitionAny other notes and comments made about the service request. For example, internal billing notes. For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible).
| |
patientInstruction | Σ | 0..1 | string | There are no (further) constraints on this element Element IdServiceRequest.patientInstruction Patient or consumer-oriented instructions DefinitionInstructions in terms that are understood by the patient or consumer. Note that FHIR strings SHALL NOT exceed 1MB in size
|
relevantHistory | I | 0..* | Reference(Provenance) | There are no (further) constraints on this element Element IdServiceRequest.relevantHistory Request provenance DefinitionKey events in the history of the request. This might not include provenances for all versions of the request – only those deemed “relevant” or important. This SHALL NOT include the Provenance associated with this current version of the resource. (If that provenance is deemed to be a “relevant” change, it will need to be added as part of a later update. Until then, it can be queried directly as the Provenance that points to this version using _revinclude All Provenances should have some historical version of this Request as their subject.
|
JSON struktūra:
{ "resourceType": "StructureDefinition", "id": "1.3.6.1.4.1.38760.FHIR.1.2.2", "url": "https://example.org/fhir/StructureDefinition/PaperLaboratoryServiceRequest", "name": "PaperLaboratoryServiceRequest", "status": "draft", "description": "Paper Service Request enetered by laboratory", "fhirVersion": "4.0.1", "kind": "resource", "abstract": false, "type": "ServiceRequest", "baseDefinition": "http://hl7.org/fhir/StructureDefinition/ServiceRequest", "derivation": "constraint", "differential": { "element": [ { "id": "ServiceRequest.identifier", "path": "ServiceRequest.identifier", "definition": "Identifiers assigned to this order instance by the order fulfiller - Laboratory. | Identifikators, ko piešķir pieprasījuma izpildītājs - laboratorija.", "min": 1, "max": "1", "mustSupport": true }, { "id": "ServiceRequest.identifier.value", "path": "ServiceRequest.identifier.value", "definition": "A unique identifier assigned to this service request in LIS. Service request identifier MUST follow the following algorithm: [organisation code][resource id][resource version][effective year][unique sequence of 10 digits within organisation] | Unikāls pakalpojumu pieprasījuma identifikators LIS. pakalpojumu pieprasījuma identifikatoram jāatbilst sekojošam veidošanas algoritmam: [organizācijas kods][resursa id][resursa versija][pieprasījuma gads][unikāla 10 ciparu kombinācija organizācijas ietvaros]", "min": 1, "example": [ { "label": "Paper Service Request Id", "valueString": "010068303.1.2.2.0.2022.0000000001" } ], "maxLength": 40, "mustSupport": true }, { "id": "ServiceRequest.status", "path": "ServiceRequest.status", "mustSupport": true, "binding": { "extension": [ { "url": "http://hl7.org/fhir/StructureDefinition/elementdefinition-bindingName", "valueString": "ServiceRequestStatus" } ], "strength": "required", "valueSet": "http://kleintech.software/fhir/terminology/1.3.6.1.4.1.38760.2.807" } }, { "id": "ServiceRequest.intent", "path": "ServiceRequest.intent", "fixedCode": "original-order", "mustSupport": true }, { "id": "ServiceRequest.subject", "path": "ServiceRequest.subject", "type": [ { "code": "Reference", "targetProfile": [ "http://hl7.org/fhir/StructureDefinition/Patient" ], "aggregation": [ "referenced" ] } ], "mustSupport": true }, { "id": "ServiceRequest.subject.reference", "path": "ServiceRequest.subject.reference", "short": "Reference to patient in EHR", "definition": "Patient system id retrieved from EHR by patient type and patient id | Pacienta sistēmas identifikators, kas tika saņemts no EVK ar pieprasījumu pēc pacienta tipa un pacienta id.", "min": 1, "mustSupport": true }, { "id": "ServiceRequest.authoredOn", "path": "ServiceRequest.authoredOn", "short": "Pieprasījuma reģistrācijas datums LIS", "definition": "When the request transitioned to being actionable. | Kad pieprasījums kļuva pieejams un aktīvs LIS.", "min": 1, "mustSupport": true }, { "id": "ServiceRequest.requester", "path": "ServiceRequest.requester", "slicing": { "discriminator": [ { "type": "value", "path": "type" } ], "rules": "open" }, "short": "Nosūtītājs", "definition": "The individual who initiated the request and has responsibility for its activation. | Nosūtītājs. Papīra nosūtījuma ievades gadījumā nosūtītāja darbavietas kodu precīzi noteikt nav iespējams, līdz ar jānorāda reference uz ĀP un ĀI, kuras ir noradītas papīra nosūtījumā.", "min": 1, "mustSupport": true }, { "id": "ServiceRequest.requester:RequestingDoctor", "path": "ServiceRequest.requester", "sliceName": "RequestingDoctor", "short": "ĀP sistēmas id", "definition": "The individual who initiated the request and has responsibility for its activation. | ĀP sistēmas id", "min": 1, "type": [ { "code": "Reference", "targetProfile": [ "http://hl7.org/fhir/StructureDefinition/Practitioner" ], "aggregation": [ "referenced" ] } ], "mustSupport": true }, { "id": "ServiceRequest.requester:RequestingDoctor.reference", "path": "ServiceRequest.requester.reference", "short": "ĀP sistēmas id", "min": 1, "mustSupport": true }, { "id": "ServiceRequest.requester:RequestingDoctor.type", "path": "ServiceRequest.requester.type", "min": 1, "fixedUri": "Doctor", "mustSupport": true }, { "id": "ServiceRequest.requester:RequestingOrganisation", "path": "ServiceRequest.requester", "sliceName": "RequestingOrganisation", "min": 1, "type": [ { "code": "Reference", "targetProfile": [ "http://hl7.org/fhir/StructureDefinition/Organization" ], "aggregation": [ "referenced" ] } ], "mustSupport": true }, { "id": "ServiceRequest.requester:RequestingOrganisation.reference", "path": "ServiceRequest.requester.reference", "short": "Organisation system id | Sistēmas organizācijas kods", "min": 1, "mustSupport": true }, { "id": "ServiceRequest.requester:RequestingOrganisation.type", "path": "ServiceRequest.requester.type", "min": 1, "fixedUri": "Organisation", "mustSupport": true } ] } }
Paraugs
Parauga objektam trūkst parauga materiālu klasifikators. Klasifikācijas uzdevums pievienots atvērtajiem jautājumiem.
Specimen | I | Specimen | Element IdSpecimen Sample for analysis DefinitionA sample to be used for analysis. | Izmeklējamā materiāla paraugs
| |
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdSpecimen.identifier External Identifier DefinitionId for specimen.
|
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdSpecimen.identifier.use 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 . IdentifierUse (required)Constraints
|
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdSpecimen.identifier.type 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 | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdSpecimen.identifier.system 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.
General http://www.acme.com/identifiers/patient Mappings
|
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdSpecimen.identifier.value 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.
40 General 123456 Mappings
|
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdSpecimen.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
|
assigner | Σ I | 0..1 | Reference(Organization) | There are no (further) constraints on this element Element IdSpecimen.identifier.assigner 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.
|
accessionIdentifier | S Σ | 1..1 | Identifier | Element IdSpecimen.accessionIdentifier Identifier assigned by the lab DefinitionThe identifier assigned by the lab when accessioning specimen(s). This is not necessarily the same as the specimen identifier, depending on local lab procedures. | Parauga identifikators LIS
|
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdSpecimen.accessionIdentifier.use 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 . IdentifierUse (required)Constraints
|
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdSpecimen.accessionIdentifier.type 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 | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdSpecimen.accessionIdentifier.system 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.
General http://www.acme.com/identifiers/patient Mappings
|
value | S Σ | 1..1 | string | Element IdSpecimen.accessionIdentifier.value The value that is unique DefinitionA unique identifier assigned to this specimen in LIS. Specimen identifier MUST follow the following algorithm: [organisation code][resource id][resource version][effective year][unique sequence of 10 digits within organisation] | Unikāls parauga identifikators LIS. Parauga identifikatoram jāatbilst sekojošam veidošanas algoritmam: [organizācijas kods][resursa id][resursa versija][izmeklējuma gads][unikāla 10 ciparu kombinācija organizācijas ietvaros] 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.
40 General 123456 Laboratory Specimen Id 010068303.1.5.1.0.2022.0000000001 Mappings
|
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdSpecimen.accessionIdentifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
|
assigner | Σ I | 0..1 | Reference(Organization) | There are no (further) constraints on this element Element IdSpecimen.accessionIdentifier.assigner 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.
|
status | Σ ?! | 1..1 | codeBinding | Element IdSpecimen.status available | unavailable | unsatisfactory | entered-in-error DefinitionThe availability of the specimen. | Materiāla parauga pieejamība un kvalitāte atbilstoši FHIR vērtībām. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. Codes providing the status/availability of a specimen. http://kleintech.software/fhir/terminology/1.3.6.1.4.1.38760.2.806 (required)Constraints
|
type | S Σ | 1..1 | CodeableConcept | There are no (further) constraints on this element Element IdSpecimen.type Kind of material that forms the specimen DefinitionThe kind of material that forms the specimen. The type can change the way that a specimen is handled and drives what kind of analyses can properly be performed on the specimen. It is frequently used in diagnostic work flow decision making systems. The type of the specimen. v2.0487 (example)Constraints
|
coding | Σ | 1..1 | Coding | There are no (further) constraints on this element Element IdSpecimen.type.coding 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 | S Σ | 1..1 | uriBinding | Element IdSpecimen.type.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously. Material types http://kleintech.software/fhir/terminology/1.3.6.1.4.1.38760.2.808 (required)Constraints
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element IdSpecimen.type.coding.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
code | S Σ | 1..1 | code | Element IdSpecimen.type.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). | Parauga materiāla klasifikatora kods Need to refer to a particular code in the system. Note that FHIR strings SHALL NOT exceed 1MB in size
|
display | S Σ | 1..1 | string | Element IdSpecimen.type.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. | Parauga materiāla koda nosaukums Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings SHALL NOT exceed 1MB in size
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element IdSpecimen.type.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
text | Σ | 0..1 | string | Element IdSpecimen.type.text 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. | Parauga materiāla tekstuālā reprezentācija latviešu valodā 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.
|
subject | S Σ I | 1..1 | Reference(Patient) | Element IdSpecimen.subject Where the specimen came from. This may be from patient(s), from a location (e.g., the source of an environmental sample), or a sampling of a substance or a device DefinitionWhere the specimen came from. This may be from patient(s), from a location (e.g., the source of an environmental sample), or a sampling of a substance or a device. Must know the subject context. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Allowed aggregation: referenced Constraints
|
reference | S Σ I | 1..1 | string | Element IdSpecimen.subject.reference Patient system Id in EHR DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdSpecimen.subject.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
|
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdSpecimen.subject.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdSpecimen.subject.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
receivedTime | S Σ | 1..1 | dateTime | Element IdSpecimen.receivedTime The time when specimen was received for processing DefinitionTime when specimen was received for processing or testing. | Parauga materiāla saņemšanas laiks laboratorijā.
|
parent | I | 0..* | Reference(Specimen) | There are no (further) constraints on this element Element IdSpecimen.parent Specimen from which this specimen originated DefinitionReference to the parent (source) specimen which is used when the specimen was either derived from or a component of another specimen. The parent specimen could be the source from which the current specimen is derived by some processing step (e.g. an aliquot or isolate or extracted nucleic acids from clinical samples) or one of many specimens that were combined to create a pooled sample.
|
request | I | 0..* | Reference(ServiceRequest) | There are no (further) constraints on this element Element IdSpecimen.request Why the specimen was collected DefinitionDetails concerning a service request that required a specimen to be collected. The request may be explicit or implied such with a ServiceRequest that requires a blood draw.
|
collection | S | 0..1 | BackboneElement | There are no (further) constraints on this element Element IdSpecimen.collection Collection details DefinitionDetails concerning the specimen collection.
|
collector | S Σ I | 0..1 | Reference(Practitioner | PractitionerRole) | Element IdSpecimen.collection.collector Who collected the specimen DefinitionPerson who collected the specimen. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Practitioner | PractitionerRole) Allowed aggregation: referenced Constraints
|
reference | S Σ I | 0..1 | string | Element IdSpecimen.collection.collector.reference Reference to collector DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. | Reference uz ĀP vai ĀP darbavietu. Ja parauga materiāla ņemējs ir zināms laboratorijai, reference ir jāpievienojama. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdSpecimen.collection.collector.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
|
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdSpecimen.collection.collector.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdSpecimen.collection.collector.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
collected[x] | S Σ | 0..1 | Element IdSpecimen.collection.collected[x] Collection time DefinitionTime when specimen was collected from subject - the physiologically relevant time. | Parauga materiāla iegūšanas datums un laiks vai peroids.
| |
collectedDateTime | dateTime | There are no (further) constraints on this element Data Type | ||
collectedPeriod | Period | There are no (further) constraints on this element Data Type | ||
duration | Σ I | 0..1 | DurationBinding | There are no (further) constraints on this element Element IdSpecimen.collection.duration How long it took to collect specimen DefinitionThe span of time over which the collection of a specimen occurred. The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator. Appropriate units for Duration. CommonUCUMCodesForDuration (extensible)Constraints
|
quantity | I | 0..1 | SimpleQuantity | There are no (further) constraints on this element Element IdSpecimen.collection.quantity The quantity of specimen collected DefinitionThe quantity of specimen collected; for instance the volume of a blood sample, or the physical measurement of an anatomic pathology sample. The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator.
|
value | Σ | 0..1 | decimal | There are no (further) constraints on this element Element IdSpecimen.collection.quantity.value 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..0 | codeBinding | There are no (further) constraints on this element Element IdSpecimen.collection.quantity.comparator < | <= | >= | > - how to understand the value DefinitionNot allowed to be used in this context Need a framework for handling measures where the value is <5ug/L or >400mg/L due to the limitations of measuring methodology. Note that FHIR strings SHALL NOT exceed 1MB in size How the Quantity should be understood and represented. QuantityComparator (required)Constraints
|
unit | Σ | 0..1 | string | There are no (further) constraints on this element Element IdSpecimen.collection.quantity.unit 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. Note that FHIR strings SHALL NOT exceed 1MB in size
|
system | Σ I | 0..1 | uri | There are no (further) constraints on this element Element IdSpecimen.collection.quantity.system 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. see http://en.wikipedia.org/wiki/Uniform_resource_identifier
|
code | Σ | 0..1 | code | There are no (further) constraints on this element Element IdSpecimen.collection.quantity.code 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.
|
method | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdSpecimen.collection.method Technique used to perform collection DefinitionA coded value specifying the technique that is used to perform the procedure. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. The technique that is used to perform the procedure. FHIRSpecimenCollectionMethod (example)Constraints
| |
bodySite | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdSpecimen.collection.bodySite Anatomical collection site DefinitionAnatomical location from which the specimen was collected (if subject is a patient). This is the target site. This element is not used for environmental specimens. If the use case requires BodySite to be handled as a separate resource instead of an inline coded element (e.g. to identify and track separately) then use the standard extension bodySite. Codes describing anatomical locations. May include laterality. SNOMEDCTBodyStructures (example)Constraints
| |
fastingStatus[x] | Σ | 0..1 | Binding | There are no (further) constraints on this element Element IdSpecimen.collection.fastingStatus[x] Whether or how long patient abstained from food and/or drink DefinitionAbstinence or reduction from some or all food, drink, or both, for a period of time prior to sample collection. Many diagnostic tests require fasting to facilitate accurate interpretation. Representing fasting status using this element is preferred to representing it with an observation using a 'pre-coordinated code' such as LOINC 2005-7 (Calcium [Moles/time] in 2 hour Urine --12 hours fasting), or using a component observation Codes describing the fasting status of the patient. v2.0916 (extensible)Constraints
|
fastingStatusCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data Type | ||
fastingStatusDuration | Duration | There are no (further) constraints on this element Data Type | ||
processing | 0..* | BackboneElement | There are no (further) constraints on this element Element IdSpecimen.processing Processing and processing step details DefinitionDetails concerning processing and processing steps for the specimen.
| |
description | 0..1 | string | There are no (further) constraints on this element Element IdSpecimen.processing.description Textual description of procedure DefinitionTextual description of procedure. Note that FHIR strings SHALL NOT exceed 1MB in size
| |
procedure | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdSpecimen.processing.procedure Indicates the treatment step applied to the specimen DefinitionA coded value specifying the procedure used to process the specimen. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Type indicating the technique used to process the specimen. SpecimenProcessingProcedure (example)Constraints
| |
additive | I | 0..* | Reference(Substance) | There are no (further) constraints on this element Element IdSpecimen.processing.additive Material used in the processing step DefinitionMaterial used in the processing step. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
time[x] | 0..1 | There are no (further) constraints on this element Element IdSpecimen.processing.time[x] Date and time of specimen processing DefinitionA record of the time or period when the specimen processing occurred. For example the time of sample fixation or the period of time the sample was in formalin.
| ||
timeDateTime | dateTime | There are no (further) constraints on this element Data Type | ||
timePeriod | Period | There are no (further) constraints on this element Data Type | ||
container | 0..* | BackboneElement | There are no (further) constraints on this element Element IdSpecimen.container Direct container of specimen (tube/slide, etc.) DefinitionThe container holding the specimen. The recursive nature of containers; i.e. blood in tube in tray in rack is not addressed here.
| |
identifier | Σ | 0..* | Identifier | There are no (further) constraints on this element Element IdSpecimen.container.identifier Id for the container DefinitionId for container. There may be multiple; a manufacturer's bar code, lab assigned identifier, etc. The container ID may differ from the specimen id in some circumstances.
|
description | 0..1 | string | There are no (further) constraints on this element Element IdSpecimen.container.description Textual description of the container DefinitionTextual description of the container. Note that FHIR strings SHALL NOT exceed 1MB in size
| |
type | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdSpecimen.container.type Kind of container directly associated with specimen DefinitionThe type of container associated with the specimen (e.g. slide, aliquot, etc.). Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Type of specimen container. SpecimenContainerType (example)Constraints
| |
capacity | I | 0..1 | SimpleQuantity | There are no (further) constraints on this element Element IdSpecimen.container.capacity Container volume or size DefinitionThe capacity (volume or other measure) the container may contain. The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator.
|
specimenQuantity | I | 0..1 | SimpleQuantity | There are no (further) constraints on this element Element IdSpecimen.container.specimenQuantity Quantity of specimen within container DefinitionThe quantity of specimen in the container; may be volume, dimensions, or other appropriate measurements, depending on the specimen type. The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator.
|
additive[x] | 0..1 | There are no (further) constraints on this element Element IdSpecimen.container.additive[x] Additive associated with container DefinitionIntroduced substance to preserve, maintain or enhance the specimen. Examples: Formalin, Citrate, EDTA. Substance added to specimen container. v2.0371 (example)Constraints
| ||
additiveCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data Type | ||
additiveReference | Reference(Substance) | There are no (further) constraints on this element Data Type | ||
condition | Σ | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element IdSpecimen.condition State of the specimen DefinitionA mode or state of being that describes the nature of the specimen. The specimen condition can be used to assess its quality or appropriateness for a specific test. Specimen condition is an observation made about the specimen. It's a point-in-time assessment. It can be used to assess its quality or appropriateness for a specific test. Codes describing the state of the specimen. v2.0493 (extensible)Constraints
|
note | S | 0..* | Annotation | There are no (further) constraints on this element Element IdSpecimen.note Comments DefinitionTo communicate any details or issues about the specimen or during the specimen collection. (for example: broken vial, sent with patient, frozen). For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible).
|
author[x] | Σ | 0..1 | There are no (further) constraints on this element Element IdSpecimen.note.author[x] 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 Type Reference(Practitioner | Patient | RelatedPerson | Organization) | ||
time | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element IdSpecimen.note.time When the annotation was made DefinitionIndicates when this particular annotation was made.
|
text | S Σ | 1..1 | markdown | Element IdSpecimen.note.text The annotation - text content (as markdown) DefinitionThe text of the annotation in markdown format. | Piezīme par parauga materiālu. Ieteicama lietošanai, ja parauga materiāls nav nedrīgs izmeklējumu veikšanai. Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/
|
JSON struktūra:
{ "resourceType": "StructureDefinition", "id": "1.3.6.1.4.1.38760.FHIR.1.5.1", "url": "https://example.org/fhir/StructureDefinition/LaboratorySpecimen", "version": "0", "name": "LaboratorySpecimen", "status": "draft", "description": "Laboratorisko izmeklējumu parauga materiāls", "fhirVersion": "4.0.1", "kind": "resource", "abstract": false, "type": "Specimen", "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Specimen", "derivation": "constraint", "differential": { "element": [ { "id": "Specimen", "path": "Specimen", "definition": "A sample to be used for analysis. | Izmeklējamā materiāla paraugs" }, { "id": "Specimen.identifier", "path": "Specimen.identifier", "max": "1" }, { "id": "Specimen.identifier.value", "path": "Specimen.identifier.value", "maxLength": 40, "mustSupport": false }, { "id": "Specimen.accessionIdentifier", "path": "Specimen.accessionIdentifier", "definition": "The identifier assigned by the lab when accessioning specimen(s). This is not necessarily the same as the specimen identifier, depending on local lab procedures. | Parauga identifikators LIS", "min": 1, "mustSupport": true }, { "id": "Specimen.accessionIdentifier.value", "path": "Specimen.accessionIdentifier.value", "definition": "A unique identifier assigned to this specimen in LIS. Specimen identifier MUST follow the following algorithm: [organisation code][resource id][resource version][effective year][unique sequence of 10 digits within organisation] | Unikāls parauga identifikators LIS. Parauga identifikatoram jāatbilst sekojošam veidošanas algoritmam: [organizācijas kods][resursa id][resursa versija][izmeklējuma gads][unikāla 10 ciparu kombinācija organizācijas ietvaros]", "min": 1, "example": [ { "label": "Laboratory Specimen Id", "valueString": "010068303.1.5.1.0.2022.0000000001" } ], "maxLength": 40, "mustSupport": true }, { "id": "Specimen.status", "path": "Specimen.status", "definition": "The availability of the specimen. | Materiāla parauga pieejamība un kvalitāte atbilstoši FHIR vērtībām.", "min": 1, "binding": { "extension": [ { "url": "http://hl7.org/fhir/StructureDefinition/elementdefinition-bindingName", "valueString": "SpecimenStatus" } ], "strength": "required", "valueSet": "http://kleintech.software/fhir/terminology/1.3.6.1.4.1.38760.2.806" } }, { "id": "Specimen.type", "path": "Specimen.type", "min": 1, "mustSupport": true }, { "id": "Specimen.type.coding", "path": "Specimen.type.coding", "min": 1, "max": "1" }, { "id": "Specimen.type.coding.system", "path": "Specimen.type.coding.system", "min": 1, "mustSupport": true, "binding": { "strength": "required", "description": "Material types", "valueSet": "http://kleintech.software/fhir/terminology/1.3.6.1.4.1.38760.2.808" } }, { "id": "Specimen.type.coding.code", "path": "Specimen.type.coding.code", "definition": "A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). | Parauga materiāla klasifikatora kods", "min": 1, "mustSupport": true }, { "id": "Specimen.type.coding.display", "path": "Specimen.type.coding.display", "definition": "A representation of the meaning of the code in the system, following the rules of the system. | Parauga materiāla koda nosaukums", "min": 1, "mustSupport": true }, { "id": "Specimen.type.text", "path": "Specimen.type.text", "definition": "A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. | Parauga materiāla tekstuālā reprezentācija latviešu valodā", "mustSupport": false }, { "id": "Specimen.subject", "path": "Specimen.subject", "min": 1, "type": [ { "code": "Reference", "targetProfile": [ "http://hl7.org/fhir/StructureDefinition/Patient" ], "aggregation": [ "referenced" ] } ], "mustSupport": true }, { "id": "Specimen.subject.reference", "path": "Specimen.subject.reference", "short": "Patient system Id in EHR", "min": 1, "mustSupport": true }, { "id": "Specimen.receivedTime", "path": "Specimen.receivedTime", "definition": "Time when specimen was received for processing or testing. | Parauga materiāla saņemšanas laiks laboratorijā.", "min": 1, "mustSupport": true }, { "id": "Specimen.collection", "path": "Specimen.collection", "mustSupport": true }, { "id": "Specimen.collection.collector", "path": "Specimen.collection.collector", "type": [ { "code": "Reference", "aggregation": [ "referenced" ] } ], "mustSupport": true }, { "id": "Specimen.collection.collector.reference", "path": "Specimen.collection.collector.reference", "short": "Reference to collector", "definition": "A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. | Reference uz ĀP vai ĀP darbavietu. Ja parauga materiāla ņemējs ir zināms laboratorijai, reference ir jāpievienojama.", "mustSupport": true }, { "id": "Specimen.collection.collected[x]", "path": "Specimen.collection.collected[x]", "definition": "Time when specimen was collected from subject - the physiologically relevant time. | Parauga materiāla iegūšanas datums un laiks vai peroids.", "mustSupport": true }, { "id": "Specimen.collection.quantity", "path": "Specimen.collection.quantity", "mustSupport": false }, { "id": "Specimen.collection.quantity.value", "path": "Specimen.collection.quantity.value", "mustSupport": false }, { "id": "Specimen.collection.quantity.unit", "path": "Specimen.collection.quantity.unit", "mustSupport": false }, { "id": "Specimen.collection.bodySite", "path": "Specimen.collection.bodySite", "mustSupport": false }, { "id": "Specimen.note", "path": "Specimen.note", "mustSupport": true }, { "id": "Specimen.note.text", "path": "Specimen.note.text", "definition": "The text of the annotation in markdown format. | Piezīme par parauga materiālu. Ieteicama lietošanai, ja parauga materiāls nav nedrīgs izmeklējumu veikšanai.", "mustSupport": true } ] } }
Izmeklējums
Observation | I | Observation | Element IdObservation Measurements and simple assertions Alternate namesVital Signs, Measurement, Results, Tests DefinitionLaboratory test measurements made about a patient, other person involved in testing, device | Izmeklējuma rezultāti par pacientu, izmeklējumā iesaistītajām personām, ar pacientu saistītajiem izmeklējamajiem priekšmetiem 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.
| |
identifier | S Σ | 1..1 | Identifier | Element IdObservation.identifier Business Identifier for observation DefinitionA unique identifier assigned to this observation in LIS | Unikāls izmeklējuma identifikators LIS Allows observations to be distinguished and referenced.
|
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdObservation.identifier.use 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 . IdentifierUse (required)Constraints
|
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdObservation.identifier.type 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 | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdObservation.identifier.system 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.
General http://www.acme.com/identifiers/patient Mappings
|
value | S Σ | 1..1 | string | Element IdObservation.identifier.value The value that is unique DefinitionA unique identifier assigned to this observation in LIS. Observation identifier MUST follow the following algorithm: [organisation code][resource id][resource version][effective year][unique sequence of 10 digits within organisation] | Unikāls izmeklējuma identifikators LIS. Izmeklējuma identifikatoram jāatbilst sekojošam veidošanas algoritmam: [organizācijas kods][resursa id][resursa versija][izmeklējuma gads][unikāla 10 ciparu kombinācija organizācijas ietvaros] 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.
40 General 123456 LaboratoryObservationIdentifier 010068303.1.4.1.0.0000000001 Mappings
|
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdObservation.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
|
assigner | Σ I | 0..1 | Reference(Organization) | There are no (further) constraints on this element Element IdObservation.identifier.assigner 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.
|
basedOn | Σ I | 0..1 | Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest) | There are no (further) constraints on this element Element IdObservation.basedOn 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. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest) Constraints
|
reference | Σ I | 1..1 | string | There are no (further) constraints on this element Element IdObservation.basedOn.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdObservation.basedOn.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
|
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdObservation.basedOn.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdObservation.basedOn.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
partOf | Σ I | 0..* | Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy) | There are no (further) constraints on this element Element IdObservation.partOf 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 | Element IdObservation.status registered | preliminary | final | amended + DefinitionThe status of the result value. | Izmeklējuma rezultāta statuss 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. http://kleintech.software/fhir/terminology/1.3.6.1.4.1.38760.2.804 (required)Constraints
|
category | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element IdObservation.category 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 | CodeableConcept | There are no (further) constraints on this element Element IdObservation.code 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. LOINCCodes (example)Constraints
|
coding | Σ | 1..1 | Coding | There are no (further) constraints on this element Element IdObservation.code.coding 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 | S Σ | 1..1 | uriFixed Value | Element IdObservation.code.coding.system Lokālais LOINC klasifikators DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
http://kleintech.software/fhir/terminology/1.3.6.1.4.1.38760.2.805
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element IdObservation.code.coding.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
code | S Σ | 1..1 | codeBinding | Element IdObservation.code.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings SHALL NOT exceed 1MB in size Lokālā LOINC klasifikatora kods http://kleintech.software/fhir/terminology/1.3.6.1.4.1.38760.2.805 (required)Constraints
|
display | S Σ | 1..1 | string | Element IdObservation.code.coding.display Representation defined by the system DefinitionKoda nosaukums Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings SHALL NOT exceed 1MB in size
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element IdObservation.code.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
text | S Σ | 1..1 | string | Element IdObservation.code.text LIS izmantotais izmeklējuma nosaukums DefinitionLaboratorijas sistēmā izmantotais izmeklējuma nosaukums. Tiks izmantots lietotāju saskarnēs. 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.
|
subject | S Σ I | 1..1 | Reference(Patient) | Element IdObservation.subject 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. Allowed aggregation: referenced Constraints
|
reference | S Σ I | 1..1 | string | Element IdObservation.subject.reference Literal reference, Relative, internal or absolute URL DefinitionPatient/[Patient Identifier in eHealth] Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdObservation.subject.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
|
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdObservation.subject.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdObservation.subject.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
focus | Σ I | 0..* | Reference(Resource) | There are no (further) constraints on this element Element IdObservation.focus 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 | Σ I | 0..1 | Reference(Encounter) | There are no (further) constraints on this element Element IdObservation.encounter 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] | S Σ | 1..1 | There are no (further) constraints on this element Element IdObservation.effective[x] 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 | Data Type | ||
issued | S Σ | 1..1 | instant | There are no (further) constraints on this element Element IdObservation.issued 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 | S Σ I | 1..1 | Reference(PractitionerRole) | Element IdObservation.performer 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. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Allowed aggregation: referenced Constraints
|
reference | S Σ I | 1..1 | string | There are no (further) constraints on this element Element IdObservation.performer.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdObservation.performer.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
|
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdObservation.performer.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdObservation.performer.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
value[x] | S Σ I | 1..1 | There are no (further) constraints on this element Element IdObservation.value[x] 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.
| |
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 | S I | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdObservation.dataAbsentReason 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 (`Observation.value[x]`) is missing. DataAbsentReason (extensible)Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element IdObservation.dataAbsentReason.coding 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.
|
text | S Σ | 0..1 | string | There are no (further) constraints on this element Element IdObservation.dataAbsentReason.text 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.
|
interpretation | S | 1..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdObservation.interpretation 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
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element IdObservation.interpretation.coding 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.
|
text | S Σ | 1..1 | string | There are no (further) constraints on this element Element IdObservation.interpretation.text 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.
|
note | S | 0..* | Annotation | There are no (further) constraints on this element Element IdObservation.note 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.
|
author[x] | Σ | 0..1 | There are no (further) constraints on this element Element IdObservation.note.author[x] 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 | |