Generated Narrative: StructureDefinition hr-diagnostic-report Name Flags Card. Type Description & Constraints DiagnosticReport 0..* DiagnosticReport A Diagnostic report - a combination of request information, atomic results, images, interpretation, as well as formatted reports Slices for extension 1..* Extension Extension Slice: Unordered, Open by value:url extension:tenant S 1..1 Identifier Owning site tenant URL: https://fhir.savannahghi.org/ig/healthy-route/StructureDefinition/hr-tenant basedOn S 0..* Reference(Healthy Route Investigation Request) What was requested status S 1..1 code registered | partial | preliminary | modified | final | amended | corrected | appended | cancelled | entered-in-error | unknown code S 1..1 CodeableConcept Kind of report subject S 1..1 Reference(Healthy Route Patient) The subject of the report - usually, but not always, the patient encounter S 1..1 Reference(Healthy Route Screening Visit) Health care event when test ordered effective[x] S 0..1 dateTime, Period When the samples were taken issued S 0..1 instant When the laboratory released the report performer S 0..* Reference(Healthy Route Organization | Healthy Route Practitioner) Responsible Diagnostic Service specimen S 0..* Reference(Specimen) Specimens this report is based on result S 0..* Reference(Healthy Route Measurement) Observations conclusion S 0..1 markdown Clinical conclusion (interpretation) of test results presentedForm S 0..* Attachment The report as issued Documentation for this format
What a laboratory returned for one participant, gathering the individual results.
Gathers results that were reported together and records who reported them. The individual values are HRObservation resources and are usable on their own; this resource is what ties them to a single issuing laboratory and a single point in time, which is what a query for the laboratory record has to return.
A Diagnostic report - a combination of request information, atomic results, images, interpretation, as well as formatted reports
The findings and interpretation of diagnostic tests performed on patients, groups of patients, products, substances, devices, and locations, and/or specimens derived from these. The report includes clinical context such as requesting provider information, and some mix of atomic results, images, textual and coded interpretations, and formatted representation of diagnostic reports. The report also includes non-clinical context such as batch analysis and stability reporting of products and substances.
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.
When a Composition is referenced in `Diagnostic.composition`, all Observation resources referenced in `Composition.entry` must also be referenced in `Diagnostic.entry` or in the references Observations in `Observation.hasMember`
composition.exists() implies (composition.resolve().section.entry.reference.where(resolve() is Observation) in (result.reference|result.reference.resolve().hasMember.reference))
If the resource is contained in another resource, it SHALL NOT contain nested Resources
If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().ofType(canonical) | %resource.descendants().ofType(uri) | %resource.descendants().ofType(url))) or descendants().where(reference = '#').exists() or descendants().where(ofType(canonical) = '#').exists() or descendants().where(ofType(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
If a resource is contained in another resource, it SHALL NOT have a security label
When a resource has no narrative, only systems that fully understand the data can display the resource to a human safely. Including a human readable representation in the resource makes for a much more robust eco-system and cheaper handling of resources by intermediary systems. Some ecosystems restrict distribution of resources to only those systems that do fully understand the resources, and as a consequence implementers may believe that the narrative is superfluous. However experience shows that such eco-systems often open up to new participants over time.
A resource should have narrative for robust management
Entity, Role, or Act,Observation[classCode=OBS, moodCode=EVN]
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.
The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
A set of rules under which this content was created
A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.
Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.
This element is labeled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies its meaning or interpretation
The base language in which the resource is written.
Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
Text summary of the resource, for human interpretation
A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.
This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.
Must have either extensions or value[x], not both
Identifies the site tenant that owns the resource.
May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R5/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them
Identifiers assigned to this report by the performer or other systems.
Usually assigned by the Information System of the diagnostic service provider (filler id).
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.
OBR-51/ for globally unique filler ID - OBR-3 , For non-globally unique filler-id the flller/placer number must be combined with the universal service Id - OBR-2(if present)+OBR-3+OBR-4
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.
This allows tracing of authorization for the report and tracking whether proposals/recommendations were acted upon.
registered | partial | preliminary | modified | final | amended | corrected | appended | cancelled | entered-in-error | unknown
Diagnostic services routinely issue provisional/incomplete reports, and sometimes withdraw previously released reports.
This element is labeled as a modifier because it is a status element that contains status entered-in-error which means that the resource should not be treated as valid
statusCode Note: final and amended are distinguished by whether observation is the subject of a ControlAct event of type "revise"
A 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.
inboundRelationship[typeCode=COMP].source[classCode=LIST, moodCode=EVN, code < LabService].code
A code or name that describes this diagnostic report.
OBR-4 (HL7 V2 doesn't provide an easy way to indicate both the ordered test and the performed panel)
The subject of the report - usually, but not always, the patient
The 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.
PID-3 (no HL7 V2 mapping for Group or Device)
The healthcare event (e.g. a patient and healthcare provider interaction) which this DiagnosticReport is about.
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).
Links the request to the Encounter context.
inboundRelationship[typeCode=COMP].source[classCode=ENC, moodCode=EVN]
The time or time-period the observed values are related to. When the subject of the report is a patient, this is usually either the time of the procedure or of specimen collection(s), but very often the source of the date/time is not known, only the date/time itself.
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.
Need to know where in the patient history to file/present this report.
The date and time that this version of the report was made available to providers, typically after the report was reviewed and verified.
Distinct from effective[x]. The interval between a sample being drawn and a result being released is what a site is asked about when a participant has already left.
Clinicians need to be able to check the date that the report was released.
The diagnostic service that is responsible for issuing the report.
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.
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.
PRT-8 (where this PRT-4-Participation = "PO")
The practitioner or organization that is responsible for the report's conclusions and interpretations.
Might not be the same entity that takes responsibility for the clinical report.
OBR-32, PRT-8 (where this PRT-4-Participation = "PI")
Details about the specimens on which this diagnostic report is based.
References the base Specimen resource. This guide does not yet profile it.
Need to be able to report information about the collected specimens on which the report is based.
[Observations](http://hl7.org/fhir/R5/observation.html) that are part of this diagnostic report.
The values themselves. Constrained to this guide's profile so that a report cannot gather observations that carry no tenant and no encounter.
May include general statements about the diagnostic report, or statements about significant, unexpected or unreliable results values contained within the diagnostic report, or information about its source when relevant to its interpretation.
Need to be able to provide free text additional information.
Reference to full details of an analysis associated with the diagnostic report
One or more links to full details of any study performed during the diagnostic investigation. An ImagingStudy might comprise a set of radiologic images obtained via a procedure that are analyzed as a group. 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. A GenomicStudy might comprise one or more analyses, each serving a specific purpose. These analyses may vary in method (e.g., karyotyping, CNV, or SNV detection), performer, software, devices used, or regions targeted.
For laboratory-type studies like GenomeStudy, type resources will be used for tracking additional metadata and workflow aspects of complex studies. ImagingStudy and the media element are somewhat overlapping - typically, the list of image references in the media 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.
Additional information supporting the diagnostic report
This backbone element contains supporting information that was used in the creation of the report not included in the results already included in the report.
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
Extensions that cannot be ignored even if unrecognized
May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
The code value for the role of the supporting information in the diagnostic report.
The reference for the supporting information in the diagnostic report.
Key images or data associated with this report
A list of key images or data associated with this report. The images or data are generally created during the diagnostic process, and may be directly of the patient, or of treated specimens (i.e. slides of interest).
Many diagnostic services include images or data in the report as part of their service.
Comment about the image or data (e.g. explanation)
A comment about the image or data. Typically, this is used to provide an explanation for why the image or data is included, or to draw the viewer's attention to important features.
The comment should be displayed with the image or data. It would be common for the report to include additional discussion of the image or data contents or in other sections such as the conclusion.
The provider of the report should make a comment about each image or data included in the report.
.inboundRelationship[typeCode=COMP].source[classCode=OBS, moodCode=EVN, code="annotation"].value
Reference to a Composition resource for the DiagnosticReport structure
Reference to a Composition resource instance that provides structure for organizing the contents of the DiagnosticReport.
The Composition provides structure to the content of the DiagnosticReport (and only contains contents referenced in the DiagnosticReport) - e.g., to order the sections of an anatomic pathology structured report.
Clinical conclusion (interpretation) of test results
Concise 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.
inboundRelationship[typeCode="SPRT"].source[classCode=OBS, moodCode=EVN, code=LOINC:48767-8].value (type=ST)
Codes for the clinical conclusion of test results
One or more codes that represent the summary conclusion (interpretation/impression) of the diagnostic report.
inboundRelationship[typeCode=SPRT].source[classCode=OBS, moodCode=EVN, code=LOINC:54531-9].value (type=CD)
Rich text representation of the entire result as issued by the diagnostic service. Multiple formats are allowed but they SHALL be semantically equivalent.
The laboratory's own document, where one is returned. Held as an attachment here rather than as a DocumentReference, because it has no life independent of this report.
Gives laboratory the ability to provide its own fully formatted report for clinical fidelity.