Befundbericht - DiagnosticReport
Beschreibung
Dieses Profil beschreibt molekulargenetischen Befundbericht der Medizininformatik-Initiative.
Name | Canonical |
---|---|
MII_PR_MolGen_MolekulargenetischerBefundbericht | https://www.medizininformatik-initiative.de/fhir/ext/modul-molgen/StructureDefinition/molekulargenetischer-befundbericht |
Das Profil ist abgeleitet vom Profil Genomics Report aus HL7 Genomics Reporting Implementation Guide.
Für den Use Case, dass die EBM Abrechnungsziffern in einem Befund angegeben werden,
wird die Supporting Information Extension in DiagnosticReport.extension mit Reference auf ChargeItem Ressource verwendet.
Ein passendes Profil für ChargeItem kann aus den deutschen FHIR Basisprofilen verwendet werden.
Diff
MII_PR_MolGen_MolekulargenetischerBefundbericht (DiagnosticReport) | I | GenomicReport | 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.
| |
id | Σ | 0..1 | id | There are no (further) constraints on this element Element idDiagnosticReport.id Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idDiagnosticReport.meta Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
|
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idDiagnosticReport.implicitRules A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
|
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idDiagnosticReport.language Language of the resource content DefinitionThe base language in which the resource is written. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). A human language.
| |
text | 0..1 | Narrative | There are no (further) constraints on this element Element idDiagnosticReport.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
| |
contained | 0..* | Resource | There are no (further) constraints on this element Element idDiagnosticReport.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.extension Extension DefinitionAn Extension Unordered, Open, by url(Value) Constraints
|
recommended-action | S I | 0..* | Extension(Reference(MII_PR_MolGen_Medikationsempfehlung | MII_PR_MolGen_EmpfohleneFolgemassnahme)) | Element idDiagnosticReport.extension:recommended-action MII EX MolGen Empfohlene Maßnahme DefinitionDie Extension verweist auf eine vorgeschlagene Maßnahme, die auf der Grundlage der Ergebnisse des Befundberichts empfohlen wird. Extension(Reference(MII_PR_MolGen_Medikationsempfehlung | MII_PR_MolGen_EmpfohleneFolgemassnahme)) Extension URL Constraints
|
genomic-risk-assessment | S I | 0..* | Extension(Reference(RiskAssessment)) | Element idDiagnosticReport.extension:genomic-risk-assessment Genomic Risk Assessment DefinitionRiskAssessment delivered as part of a genomics report or observation Extension(Reference(RiskAssessment)) Extension URLhttp://hl7.org/fhir/uv/genomics-reporting/StructureDefinition/genomic-risk-assessment Constraints
|
coded-note | S I | 0..* | Extension(CodedAnnotation) | Element idDiagnosticReport.extension:coded-note Comments about the report that also contain a coded type DefinitionAdds codified notes to a report to capture additional content Need to be able to provide free text additional information. Notes SHALL NOT contain information which can be captured in a structured way. May include general statements about the report, or statements about significant, unexpected or unreliable results values, or information about its source when relevant to its interpretation. The CodedAnnotation data type, while not allowing for or intending to make the content computable, does allow the author to indicate the type of note. This does not replace the use of results or conclusion or conclusionCode. One important note is that Annotation is a FHIR data type, this is NOT about annotations in the genomic context. http://hl7.org/fhir/uv/genomics-reporting/StructureDefinition/genomic-report-note Constraints
|
supporting-info | S I | 0..* | Extension(Reference(Resource)) | Element idDiagnosticReport.extension:supporting-info Other information that may be relevant to this event. DefinitionOther resources from the patient record that may be relevant to the event. The information from these resources was either used to create the instance or is provided to help with its interpretation. This extension should not be used if more specific inline elements or extensions are available. For example, use Extension(Reference(Resource)) Extension URLhttp://hl7.org/fhir/StructureDefinition/workflow-supportingInfo Constraints
|
genomic-study | I | 0..* | Extension(Reference(GenomicStudy)) | There are no (further) constraints on this element Element idDiagnosticReport.extension:genomic-study Reference to full details of an genomic study associated with the diagnostic report DefinitionUsed to reference a GenomicStudy profile Extension(Reference(GenomicStudy)) Extension URLhttp://hl7.org/fhir/uv/genomics-reporting/StructureDefinition/genomic-study-reference Constraints
|
hla-genotyping-results-allele-database | I | 0..1 | Extension(CodeableConcept) | There are no (further) constraints on this element Element idDiagnosticReport.extension:hla-genotyping-results-allele-database Allele Database DefinitionAllele Database. http://hl7.org/fhir/StructureDefinition/hla-genotyping-results-allele-database Constraints
|
hla-genotyping-results-glstring | I | 0..1 | Extension(Complex) | There are no (further) constraints on this element Element idDiagnosticReport.extension:hla-genotyping-results-glstring glstring Definitionglstring. Extension(Complex) Extension URLhttp://hl7.org/fhir/StructureDefinition/hla-genotyping-results-glstring Constraints
|
workflow-relatedArtifact | S I | 0..* | Extension(RelatedArtifact) | Element idDiagnosticReport.extension:workflow-relatedArtifact Documentation relevant to the 'parent' resource DefinitionDocuments the 'knowledge artifacts' relevant to the base resource such as citations, supporting evidence, documentation of processes, caveats around testing methodology. Note that in contrast this extension, the supportingInfo extension references other resources from the patient record that were used in creating the resource. http://hl7.org/fhir/StructureDefinition/workflow-relatedArtifact Constraints
|
modifierExtension | ?! I | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
identifier | Σ | 0..* | Identifier | There are no (further) constraints on this element Element idDiagnosticReport.identifier 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).
|
basedOn | 0..* | Reference(CarePlan | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest) | There are no (further) constraints on this element 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. Reference(CarePlan | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest) Constraints
| |
status | S Σ ?! | 1..1 | codeBinding | Element idDiagnosticReport.status registered | partial | preliminary | final + Alternate namesBerichtstatus DefinitionThe status of the diagnostic report. Diagnostic services routinely issue provisional/incomplete reports, and sometimes withdraw previously released reports. The status of the diagnostic report.
|
category | Σ | 1..* | 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. Unordered, Open, by coding(Value) Slice based on the category code pattern Binding Codes for diagnostic service sections.
|
Genetics | Σ | 1..1 | CodeableConcept | There are no (further) constraints on this element Element idDiagnosticReport.category:Genetics 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.category:Genetics.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.category:Genetics.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 1..1 | CodingPattern | There are no (further) constraints on this element Element idDiagnosticReport.category:Genetics.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://terminology.hl7.org/CodeSystem/v2-0074", "code": "GE" }
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.category:Genetics.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.
|
code | Σ | 1..1 | CodeableConceptBindingPattern | 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. Codes that describe Diagnostic Reports.
{ "coding": [ { "system": "http://loinc.org", "code": "51969-4" } ] }
|
subject | S Σ | 1..1 | Reference(Patient | Group) | 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.
|
encounter | S Σ | 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] | Σ | 0..1 | There are no (further) constraints on this element Element idDiagnosticReport.effective[x] Clinically relevant time/time-period for report Alternate namesObservation time, Effective Time, Occurrence DefinitionThe 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. 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 | ||
issued | S Σ | 0..1 | instant | Element idDiagnosticReport.issued DateTime this version was made Alternate namesDate published, Date Issued, Date Verified, Datum des Berichtes DefinitionThe date and time that this version of the report was made available to providers, typically after the report was reviewed and verified. 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 Σ | 0..* | Reference(Practitioner | PractitionerRole | Organization | CareTeam) | Element idDiagnosticReport.performer Responsible Diagnostic Service Alternate namesLaboratory, Service, Practitioner, Department, Company, Authorized by, Director, Labor / Institution/ Ansprechpartner 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. Reference(Practitioner | PractitionerRole | Organization | CareTeam) Constraints
|
resultsInterpreter | S Σ | 0..* | Reference(Practitioner | PractitionerRole | Organization | CareTeam) | Element idDiagnosticReport.resultsInterpreter Primary result interpreter Alternate namesAnalyzed by, Reported by, Labor / Institution/ Ansprechpartner 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. Reference(Practitioner | PractitionerRole | Organization | CareTeam) Constraints
|
specimen | S | 0..* | 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.
|
result | S | 0..* | 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. Unordered, Open, by resolve()(Profile) Slice based on the reference profile and code pattern Constraints
|
diagnostic-implication | S | 0..* | Reference(MII_PR_MolGen_DiagnostischeImplikation) | Element idDiagnosticReport.result:diagnostic-implication Diagnostic Implication 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(MII_PR_MolGen_DiagnostischeImplikation) Constraints
|
therapeutic-implication | S | 0..* | Reference(MII_PR_MolGen_TherapeutischeImplikation) | Element idDiagnosticReport.result:therapeutic-implication Therapeutic Implication 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(MII_PR_MolGen_TherapeutischeImplikation) Constraints
|
molecular-consequence | 0..* | Reference(MolecularConsequence) | There are no (further) constraints on this element Element idDiagnosticReport.result:molecular-consequence Molecular Consequence 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(MolecularConsequence) Constraints
| |
variant | S | 0..* | Reference(MII_PR_MolGen_Variante) | Element idDiagnosticReport.result:variant Variant 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(MII_PR_MolGen_Variante) Constraints
|
sequence-phase-relation | S | 0..* | Reference(SequencePhaseRelationship) | There are no (further) constraints on this element Element idDiagnosticReport.result:sequence-phase-relation Sequence Phase Relationship 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(SequencePhaseRelationship) Constraints
|
genotype | S | 0..* | Reference(MII_PR_MolGen_Genotyp) | Element idDiagnosticReport.result:genotype Genotype 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(MII_PR_MolGen_Genotyp) Constraints
|
haplotype | S | 0..* | Reference(Haplotype) | There are no (further) constraints on this element Element idDiagnosticReport.result:haplotype Haplotype 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.
|
biomarker | 0..* | Reference(MolecularBiomarker) | There are no (further) constraints on this element Element idDiagnosticReport.result:biomarker MolecularBiomarker 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.
| |
tumor-mutation-burden | S | 0..* | Reference(MII_PR_MolGen_Mutationslast) | Element idDiagnosticReport.result:tumor-mutation-burden 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(MII_PR_MolGen_Mutationslast) Constraints
|
microsatellite-instability | S | 0..* | Reference(MII_PR_MolGen_Mikrosatelliteninstabilitaet) | Element idDiagnosticReport.result:microsatellite-instability 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(MII_PR_MolGen_Mikrosatelliteninstabilitaet) Constraints
|
imagingStudy | 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 | S Σ | 0..* | BackboneElement | Element idDiagnosticReport.media Key images associated with this report Alternate namesDICOM, Slides, Scans DefinitionA list of key images associated with this report. The images 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 in the report as part of their service.
|
id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.media.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.media.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.media.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
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 | Σ | 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.
|
conclusion | S | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.conclusion Assessment of overall 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.
|
conclusionCode | S | 0..* | CodeableConcept | There are no (further) constraints on this element Element idDiagnosticReport.conclusionCode Coarse overall interpretation of the genomic results DefinitionOne or more codes that represent the summary conclusion (interpretation/impression) of the diagnostic report. Diagnosis codes provided as adjuncts to the report.
|
presentedForm | 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.
|
Snapshot
MII_PR_MolGen_MolekulargenetischerBefundbericht (DiagnosticReport) | I | GenomicReport | 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.
| |
id | Σ | 0..1 | id | There are no (further) constraints on this element Element idDiagnosticReport.id Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idDiagnosticReport.meta Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
|
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idDiagnosticReport.implicitRules A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
|
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idDiagnosticReport.language Language of the resource content DefinitionThe base language in which the resource is written. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). A human language.
| |
text | 0..1 | Narrative | There are no (further) constraints on this element Element idDiagnosticReport.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
| |
contained | 0..* | Resource | There are no (further) constraints on this element Element idDiagnosticReport.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.extension Extension DefinitionAn Extension Unordered, Open, by url(Value) Constraints
|
recommended-action | S I | 0..* | Extension(Reference(MII_PR_MolGen_Medikationsempfehlung | MII_PR_MolGen_EmpfohleneFolgemassnahme)) | Element idDiagnosticReport.extension:recommended-action MII EX MolGen Empfohlene Maßnahme DefinitionDie Extension verweist auf eine vorgeschlagene Maßnahme, die auf der Grundlage der Ergebnisse des Befundberichts empfohlen wird. Extension(Reference(MII_PR_MolGen_Medikationsempfehlung | MII_PR_MolGen_EmpfohleneFolgemassnahme)) Extension URL Constraints
|
genomic-risk-assessment | S I | 0..* | Extension(Reference(RiskAssessment)) | Element idDiagnosticReport.extension:genomic-risk-assessment Genomic Risk Assessment DefinitionRiskAssessment delivered as part of a genomics report or observation Extension(Reference(RiskAssessment)) Extension URLhttp://hl7.org/fhir/uv/genomics-reporting/StructureDefinition/genomic-risk-assessment Constraints
|
coded-note | S I | 0..* | Extension(CodedAnnotation) | Element idDiagnosticReport.extension:coded-note Comments about the report that also contain a coded type DefinitionAdds codified notes to a report to capture additional content Need to be able to provide free text additional information. Notes SHALL NOT contain information which can be captured in a structured way. May include general statements about the report, or statements about significant, unexpected or unreliable results values, or information about its source when relevant to its interpretation. The CodedAnnotation data type, while not allowing for or intending to make the content computable, does allow the author to indicate the type of note. This does not replace the use of results or conclusion or conclusionCode. One important note is that Annotation is a FHIR data type, this is NOT about annotations in the genomic context. http://hl7.org/fhir/uv/genomics-reporting/StructureDefinition/genomic-report-note Constraints
|
supporting-info | S I | 0..* | Extension(Reference(Resource)) | Element idDiagnosticReport.extension:supporting-info Other information that may be relevant to this event. DefinitionOther resources from the patient record that may be relevant to the event. The information from these resources was either used to create the instance or is provided to help with its interpretation. This extension should not be used if more specific inline elements or extensions are available. For example, use Extension(Reference(Resource)) Extension URLhttp://hl7.org/fhir/StructureDefinition/workflow-supportingInfo Constraints
|
genomic-study | I | 0..* | Extension(Reference(GenomicStudy)) | There are no (further) constraints on this element Element idDiagnosticReport.extension:genomic-study Reference to full details of an genomic study associated with the diagnostic report DefinitionUsed to reference a GenomicStudy profile Extension(Reference(GenomicStudy)) Extension URLhttp://hl7.org/fhir/uv/genomics-reporting/StructureDefinition/genomic-study-reference Constraints
|
hla-genotyping-results-allele-database | I | 0..1 | Extension(CodeableConcept) | There are no (further) constraints on this element Element idDiagnosticReport.extension:hla-genotyping-results-allele-database Allele Database DefinitionAllele Database. http://hl7.org/fhir/StructureDefinition/hla-genotyping-results-allele-database Constraints
|
hla-genotyping-results-glstring | I | 0..1 | Extension(Complex) | There are no (further) constraints on this element Element idDiagnosticReport.extension:hla-genotyping-results-glstring glstring Definitionglstring. Extension(Complex) Extension URLhttp://hl7.org/fhir/StructureDefinition/hla-genotyping-results-glstring Constraints
|
workflow-relatedArtifact | S I | 0..* | Extension(RelatedArtifact) | Element idDiagnosticReport.extension:workflow-relatedArtifact Documentation relevant to the 'parent' resource DefinitionDocuments the 'knowledge artifacts' relevant to the base resource such as citations, supporting evidence, documentation of processes, caveats around testing methodology. Note that in contrast this extension, the supportingInfo extension references other resources from the patient record that were used in creating the resource. http://hl7.org/fhir/StructureDefinition/workflow-relatedArtifact Constraints
|
modifierExtension | ?! I | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
identifier | Σ | 0..* | Identifier | There are no (further) constraints on this element Element idDiagnosticReport.identifier 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).
|
basedOn | 0..* | Reference(CarePlan | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest) | There are no (further) constraints on this element 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. Reference(CarePlan | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest) Constraints
| |
status | S Σ ?! | 1..1 | codeBinding | Element idDiagnosticReport.status registered | partial | preliminary | final + Alternate namesBerichtstatus DefinitionThe status of the diagnostic report. Diagnostic services routinely issue provisional/incomplete reports, and sometimes withdraw previously released reports. The status of the diagnostic report.
|
category | Σ | 1..* | 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. Unordered, Open, by coding(Value) Slice based on the category code pattern Binding Codes for diagnostic service sections.
|
Genetics | Σ | 1..1 | CodeableConcept | There are no (further) constraints on this element Element idDiagnosticReport.category:Genetics 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.category:Genetics.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.category:Genetics.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 1..1 | CodingPattern | There are no (further) constraints on this element Element idDiagnosticReport.category:Genetics.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://terminology.hl7.org/CodeSystem/v2-0074", "code": "GE" }
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.category:Genetics.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.
|
code | Σ | 1..1 | CodeableConceptBindingPattern | 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. Codes that describe Diagnostic Reports.
{ "coding": [ { "system": "http://loinc.org", "code": "51969-4" } ] }
|
subject | S Σ | 1..1 | Reference(Patient | Group) | 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.
|
encounter | S Σ | 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] | Σ | 0..1 | There are no (further) constraints on this element Element idDiagnosticReport.effective[x] Clinically relevant time/time-period for report Alternate namesObservation time, Effective Time, Occurrence DefinitionThe 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. 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 | ||
issued | S Σ | 0..1 | instant | Element idDiagnosticReport.issued DateTime this version was made Alternate namesDate published, Date Issued, Date Verified, Datum des Berichtes DefinitionThe date and time that this version of the report was made available to providers, typically after the report was reviewed and verified. 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 Σ | 0..* | Reference(Practitioner | PractitionerRole | Organization | CareTeam) | Element idDiagnosticReport.performer Responsible Diagnostic Service Alternate namesLaboratory, Service, Practitioner, Department, Company, Authorized by, Director, Labor / Institution/ Ansprechpartner 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. Reference(Practitioner | PractitionerRole | Organization | CareTeam) Constraints
|
resultsInterpreter | S Σ | 0..* | Reference(Practitioner | PractitionerRole | Organization | CareTeam) | Element idDiagnosticReport.resultsInterpreter Primary result interpreter Alternate namesAnalyzed by, Reported by, Labor / Institution/ Ansprechpartner 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. Reference(Practitioner | PractitionerRole | Organization | CareTeam) Constraints
|
specimen | S | 0..* | 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.
|
result | S | 0..* | 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. Unordered, Open, by resolve()(Profile) Slice based on the reference profile and code pattern Constraints
|
diagnostic-implication | S | 0..* | Reference(MII_PR_MolGen_DiagnostischeImplikation) | Element idDiagnosticReport.result:diagnostic-implication Diagnostic Implication 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(MII_PR_MolGen_DiagnostischeImplikation) Constraints
|
therapeutic-implication | S | 0..* | Reference(MII_PR_MolGen_TherapeutischeImplikation) | Element idDiagnosticReport.result:therapeutic-implication Therapeutic Implication 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(MII_PR_MolGen_TherapeutischeImplikation) Constraints
|
molecular-consequence | 0..* | Reference(MolecularConsequence) | There are no (further) constraints on this element Element idDiagnosticReport.result:molecular-consequence Molecular Consequence 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(MolecularConsequence) Constraints
| |
variant | S | 0..* | Reference(MII_PR_MolGen_Variante) | Element idDiagnosticReport.result:variant Variant 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(MII_PR_MolGen_Variante) Constraints
|
sequence-phase-relation | S | 0..* | Reference(SequencePhaseRelationship) | There are no (further) constraints on this element Element idDiagnosticReport.result:sequence-phase-relation Sequence Phase Relationship 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(SequencePhaseRelationship) Constraints
|
genotype | S | 0..* | Reference(MII_PR_MolGen_Genotyp) | Element idDiagnosticReport.result:genotype Genotype 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(MII_PR_MolGen_Genotyp) Constraints
|
haplotype | S | 0..* | Reference(Haplotype) | There are no (further) constraints on this element Element idDiagnosticReport.result:haplotype Haplotype 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.
|
biomarker | 0..* | Reference(MolecularBiomarker) | There are no (further) constraints on this element Element idDiagnosticReport.result:biomarker MolecularBiomarker 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.
| |
tumor-mutation-burden | S | 0..* | Reference(MII_PR_MolGen_Mutationslast) | Element idDiagnosticReport.result:tumor-mutation-burden 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(MII_PR_MolGen_Mutationslast) Constraints
|
microsatellite-instability | S | 0..* | Reference(MII_PR_MolGen_Mikrosatelliteninstabilitaet) | Element idDiagnosticReport.result:microsatellite-instability 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(MII_PR_MolGen_Mikrosatelliteninstabilitaet) Constraints
|
imagingStudy | 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 | S Σ | 0..* | BackboneElement | Element idDiagnosticReport.media Key images associated with this report Alternate namesDICOM, Slides, Scans DefinitionA list of key images associated with this report. The images 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 in the report as part of their service.
|
id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.media.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.media.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.media.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
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 | Σ | 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.
|
conclusion | S | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.conclusion Assessment of overall 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.
|
conclusionCode | S | 0..* | CodeableConcept | There are no (further) constraints on this element Element idDiagnosticReport.conclusionCode Coarse overall interpretation of the genomic results DefinitionOne or more codes that represent the summary conclusion (interpretation/impression) of the diagnostic report. Diagnosis codes provided as adjuncts to the report.
|
presentedForm | 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.
|
Extensions
Genomics Artifact
- Name: Genomics Artifact
- Definition: Erfasst Zitate, Beweise und andere unterstützende Unterlagen für die Beobachtung oder den Bericht.
- url: http://hl7.org/fhir/uv/genomics-reporting/StructureDefinition/genomics-artifact
Snapshot
Genomics File
- Name: Genomics File
- Definition: Wird verwendet, um den Inhalt von oder Links zu Dateien zu übermitteln, die als Teil des Testprozesses erstellt wurden. Beispiele sind VCF-, BAM-, CRAM- und andere ähnliche Dateien.
- url: http://hl7.org/fhir/uv/genomics-reporting/StructureDefinition/genomics-file
Snapshot
Empfohlene Maßnahme
- Name: Empfohlene Maßnahme
- Definition: Die Extension verweist auf eine vorgeschlagene Maßnahme, die auf der Grundlage der Ergebnisse des Befundberichts empfohlen wird.
- url: https://www.medizininformatik-initiative.de/fhir/ext/modul-molgen/StructureDefinition/empfohlene-massnahme
Snapshot
MII_EX_MolGen_EmpfohleneMassnahme (Extension) | I | RecommendedAction | Element idExtension MII EX MolGen Empfohlene Maßnahme DefinitionDie Extension verweist auf eine vorgeschlagene Maßnahme, die auf der Grundlage der Ergebnisse des Befundberichts empfohlen wird.
| |
id | 0..1 | string | There are no (further) constraints on this element Element idExtension.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..0 | Extension | There are no (further) constraints on this element Element idExtension.extension Extension DefinitionAn Extension Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idExtension.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/genomics-reporting/StructureDefinition/recommended-action
| |
value[x] | 0..1 | There are no (further) constraints on this element Element idExtension.value[x] Value of extension DefinitionValue of extension - must be one of a constrained set of the data types (see Extensibility for a list).
| ||
valueReference | Reference(MII_PR_MolGen_Medikationsempfehlung | MII_PR_MolGen_EmpfohleneFolgemassnahme) | Data type Reference(MII_PR_MolGen_Medikationsempfehlung | MII_PR_MolGen_EmpfohleneFolgemassnahme) |
Genomics Risk Assessment
- Name: Genomics Risk Assessment
- Definition: RiskAssessment als Teil eines genomischen Berichtes oder einer Beobachtung.
- url: http://hl7.org/fhir/uv/genomics-reporting/StructureDefinition/genomics-risk-assessment
Snapshot
Coded Note
- Name: Coded Note
- Definition: Kommentare zum Bericht, die auch einen kodierten Typ enthalten.
- url: http://hl7.org/fhir/uv/genomics-reporting/StructureDefinition/genomic-report-note
Snapshot
GenomicReportNote (Extension) | I | Extension | Element idExtension Genomic Report Note DefinitionAdds codified notes to a report to capture additional content
| |
id | 0..1 | string | There are no (further) constraints on this element Element idExtension.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..0 | Extension | There are no (further) constraints on this element Element idExtension.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
url | 1..1 | uriFixed Value | Element idExtension.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/genomics-reporting/StructureDefinition/genomic-report-note
| |
value[x] | 0..1 | Element idExtension.value[x] Text node with attribution DefinitionA text note which also contains information about who made the statement and when. 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).
| ||
valueAnnotation | CodedAnnotation | Data type |
Supporting Info
- Name: Supporting Info
- Definition: Weitere Informationen, die für diese Beobachtung relevant sein könnten.
- url: http://hl7.org/fhir/StructureDefinition/workflow-supportingInfo
Snapshot
supportingInfo (Extension) | I | Extension | Element idExtension Other information that may be relevant to this event. DefinitionOther resources from the patient record that may be relevant to the event. The information from these resources was either used to create the instance or is provided to help with its interpretation. This extension should not be used if more specific inline elements or extensions are available. For example, use
| |
id | 0..1 | string | There are no (further) constraints on this element Element idExtension.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..0 | Extension | There are no (further) constraints on this element Element idExtension.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
url | 1..1 | uriFixed Value | Element idExtension.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/StructureDefinition/workflow-supportingInfo
| |
value[x] | 1..1 | There are no (further) constraints on this element Element idExtension.value[x] Value of extension DefinitionValue of extension - must be one of a constrained set of the data types (see Extensibility for a list).
| ||
valueReference | Reference(Resource) | Data type |
FHIR-Element | Logischer Datensatz |
---|---|
DiagnosticReport.status | Weiteres.Berichtstatus |
DiagnosticReport.issued | Weiteres.Datum des Berichts |
DiagnosticReport.performer | Weiteres.Labor / Institution/ Ansprechpartner |
DiagnosticReport.resultsInterpreter | Weiteres.Labor / Institution/ Ansprechpartner |
DiagnosticReport.media | Ergebnisse.Daten |
DiagnosticReport.media | Weiteres.Anhänge |
DiagnosticReport.subject | Probeninformationen.Patient |
DiagnosticReport.specimen | Probeninformationen.Probe |
DiagnosticReport.identifier | Weiteres.Bericht ID |
DiagnosticReport.extension:supporting-info(ChargeItem) | Anforderung.Einheitlicher Bewertungsmaßstab |
DiagnosticReport.supporting-info | Methoden.Relevante Parameter |
Suchparameter
Folgende Suchparameter sind für das Modul Pathologie-Befund relevant, auch in Kombination:
Der Suchparameter
_id
MUSS unterstützt werden:Beispiele:
GET [base]/DiagnosticReport?_id=example-mii-molgen-molekulargenetischer-befundbericht-1
Anwendungshinweise: Weitere Informationen zur Suche nach "_id" finden sich in der FHIR-Basisspezifikation - Abschnitt "Parameters for all resources".
Der Suchparameter "_profile" MUSS unterstützt werden:
Beispiele:
GET [base]/DiagnosticReport?_profile=https://www.medizininformatik-initiative.de/fhir/ext/modul-molgen/StructureDefinition/molekulargenetischer-befundbericht
Anwendungshinweise: Weitere Informationen zur Suche nach "_profile" finden sich in der FHIR-Basisspezifikation - Abschnitt "Parameters for all resources".
Der Suchparameter "code" MUSS unterstützt werden:
Beispiele:
GET [base]/DiagnosticReport?code=http://loinc.org|51969-4
Anwendungshinweise: Weitere Informationen zur Suche nach "code" finden sich in der FHIR-Basisspezifikation - Abschnitt "token".
Der Suchparameter "subject" MUSS unterstützt werden:
Beispiele:
GET [base]/DiagnosticReport?subject=Patient/example-mii-molgen-patient
Anwendungshinweise: Weitere Informationen zur Suche nach "subject" finden sich in der FHIR-Basisspezifikation - Abschnitt "reference".
Der Suchparameter "category" MUSS unterstützt werden:
Beispiele:
GET [base]/DiagnosticReport?category=http://terminology.hl7.org/CodeSystem/v2-0074|GE
Anwendungshinweise: Weitere Informationen zur Suche nach "category" finden sich in der FHIR-Basisspezifikation - Abschnitt "token".
Der Suchparameter "encounter" MUSS unterstützt werden:
Beispiele:
GET [base]/DiagnosticReport?encounter=Encounter/12345
Anwendungshinweise: Weitere Informationen zur Suche nach "encounter" finden sich in der FHIR-Basisspezifikation - Abschnitt "reference".
Der Suchparameter "date" MUSS unterstützt werden:
Beispiele:
GET [base]/DiagnosticReport?date=2022-07-13
Anwendungshinweise: Weitere Informationen zur Suche nach "date" finden sich in der FHIR-Basisspezifikation - Abschnitt "date".
Der Suchparameter "issued" MUSS unterstützt werden:
Beispiele:
GET [base]/DiagnosticReport?issued=2022-07-13
Anwendungshinweise: Weitere Informationen zur Suche nach "issued" finden sich in der FHIR-Basisspezifikation - Abschnitt "date".
Der Suchparameter "performer" MUSS unterstützt werden:
Beispiele:
GET [base]/DiagnosticReport?performer=Practioner/example-mii-molgen-practitioner-laboratory
Anwendungshinweise: Weitere Informationen zur Suche nach "performer" finden sich in der FHIR-Basisspezifikation - Abschnitt "reference".
Der Suchparameter "requestor" MUSS unterstützt werden:
Beispiele:
GET [base]/DiagnosticReport?requestor=Practioner/example-mii-molgen-practitioner-physician
Anwendungshinweise: Weitere Informationen zur Suche nach "requestor" finden sich in der FHIR-Basisspezifikation - Abschnitt "reference".
Der Suchparameter "specimen" MUSS unterstützt werden:
Beispiele:
GET [base]/DiagnosticReport?specimen=Specimen/example-mii-molgen-specimen
Anwendungshinweise: Weitere Informationen zur Suche nach "specimen" finden sich in der FHIR-Basisspezifikation - Abschnitt "reference".
Der Suchparameter "status" MUSS unterstützt werden:
Beispiele:
GET [base]/DiagnosticReport?status=final
Anwendungshinweise: Weitere Informationen zur Suche nach "status" finden sich in der FHIR-Basisspezifikation - Abschnitt "token".
Der Suchparameter "result" MUSS unterstützt werden:
Beispiele:
GET [base]/DiagnosticReport?result=Observation/example-mii-molgen-variante-1
Anwendungshinweise: Weitere Informationen zur Suche nach "result" finden sich in der FHIR-Basisspezifikation - Abschnitt "reference".
Der Suchparameter "media" MUSS unterstützt werden:
Beispiele:
GET [base]/DiagnosticReport?media=Media/12345
Anwendungshinweise: Weitere Informationen zur Suche nach "media" finden sich in der FHIR-Basisspezifikation - Abschnitt "reference".
Der Suchparameter "conclusion" MUSS unterstützt werden:
Beispiele:
GET [base]/DiagnosticReport?conclusion=http://snomed.info/sct|830150003
Anwendungshinweise: Weitere Informationen zur Suche nach "conclusion" finden sich in der FHIR-Basisspezifikation - Abschnitt "token".
Examples
Befundbericht-1 BRAF
Befundbericht-2 NIPBL
Die in Befundbericht-2 abzurechnenden EBM-Ziffern werden separat in ChargeItem Ressourcen erfasst.
{ "resourceType": "ChargeItem", "id": "mii-exa-molgen-chargeitem-ebm-21", "meta": { "profile": [ "http://fhir.de/StructureDefinition/chargeitem-de-ebm" ] }, "code": { "coding": [ { "system": "https://fhir.kbv.de/NamingSystem/KBV_NS_Base_EBM", "code": "11513", "display": "Postnatale Mutationssuche zum Nachweis oder Ausschluss einer krankheitsrelevanten oder krankheitsauslösenden konstitutionellen genomischen Mutation" } ] }, "status": "billable", "subject": { "reference": "Patient/mii-exa-molgen-patient-2" }, "quantity": { "value": 72 } }
Befundbericht-3 Risk-Panel