Mayo Enterprise FHIR

Diagnostic Report

USCoreDiagnosticReport	I		DiagnosticReport	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport Short description US Core Diagnostic Report Profile Alternate names Report, Test, Result, Results, Labs, Laboratory, Lab Result, Lab Report Definition The US Core Diagnostic Report Profile is based upon the core FHIR DiagnosticReport Resource and created to meet the 2015 Edition Common Clinical Data Set 'Laboratory test(s) and Laboratory value(s)/result(s)' requirements. Comments 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. Data type DiagnosticReport Constraints dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources `contained.contained.empty()` dom-1: If the resource is contained in another resource, it SHALL NOT contain any narrative `contained.text.empty()` dom-4: 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()` dom-3: If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource `contained.where(('#'+id in %resource.descendants().reference).not()).empty()` Mappings rim: Entity. Role, or Act workflow: Event v2: ORU -> OBR rim: Observation[classCode=OBS, moodCode=EVN] w5: clinical.diagnostics argonaut-dq-dstu2: DiagnosticReport
id	Σ	0..1	id	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.id Short description Logical id of this artifact Definition The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. Comments The only time that a resource does not have an id is when it is being submitted to the server using a create operation. Data type id
meta	Σ	0..1	Meta	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.meta Short description Metadata about the resource Definition The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource. Data type Meta
implicitRules	Σ ?!	0..1	uri	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.implicitRules Short description A set of rules under which this content was created Definition A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Comments Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. Data type uri
language		0..1	codeBinding	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.language Short description Language of the resource content Definition The base language in which the resource is written. Comments Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). Data type code Binding A human language. ?? (extensible)
text	I	0..1	Narrative	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.text Short description Text summary of the resource, for human interpretation Alternate names narrative, html, xhtml, display Definition A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Comments Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later. Data type Narrative Mappings rim: Act.text?
contained		0..*	Resource	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.contained Short description Contained, inline Resources Alternate names inline resources, anonymous resources, contained resources Definition These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. Comments This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Data type Resource Mappings rim: N/A
extension		0..*	Extension	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.extension Short description Additional Content defined by implementations Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the resource. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Mappings rim: N/A
modifierExtension	?!	0..*	Extension	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.modifierExtension Short description Extensions that cannot be ignored Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Mappings rim: N/A
identifier	Σ	0..*	Identifier	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.identifier Short description Business identifier for report Alternate names ReportID, Filler ID, Placer ID Definition Identifiers assigned to this report by the performer or other systems. Requirements 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. Comments Usually assigned by the Information System of the diagnostic service provider (filler id). Data type Identifier Mappings workflow: Event.identifier v2: OBR-51 rim: id w5: id
basedOn		0..*	Reference(http://hl7.org/fhir/StructureDefinition/CarePlan \| http://hl7.org/fhir/StructureDefinition/ImmunizationRecommendation \| http://hl7.org/fhir/StructureDefinition/MedicationRequest \| http://hl7.org/fhir/StructureDefinition/NutritionOrder \| http://hl7.org/fhir/StructureDefinition/ProcedureRequest \| http://hl7.org/fhir/StructureDefinition/ReferralRequest)	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.basedOn Short description What was requested Alternate names Request Definition Details concerning a test or procedure requested. Requirements This allows tracing of authorization for the report and tracking whether proposals/recommendations were acted upon. Comments 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. Data type Reference(http://hl7.org/fhir/StructureDefinition/CarePlan \| http://hl7.org/fhir/StructureDefinition/ImmunizationRecommendation \| http://hl7.org/fhir/StructureDefinition/MedicationRequest \| http://hl7.org/fhir/StructureDefinition/NutritionOrder \| http://hl7.org/fhir/StructureDefinition/ProcedureRequest \| http://hl7.org/fhir/StructureDefinition/ReferralRequest) Mappings workflow: Event.basedOn v2: ORC? OBR-2/3? rim: outboundRelationship[typeCode=FLFS].target
status	S Σ ?!	1..1	codeBinding	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.status Short description registered \| partial \| preliminary \| final + Definition The status of the diagnostic report as a whole. Requirements Diagnostic services routinely issue provisional/incomplete reports, and sometimes withdraw previously released reports. Comments This is labeled as "Is Modifier" because applications need to take appropriate action if a report is withdrawn. Data type code Binding ?? (required) Mappings workflow: Event.status v2: OBR-25 (not 1:1 mapping) rim: statusCode Note: final and amended are distinguished by whether observation is the subject of a ControlAct event of type "revise" w5: status argonaut-dq-dstu2: DiagnosticReport.status
category	S Σ	1..1	CodeableConceptPattern	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.category Short description Service category Alternate names Department, Sub-department, Service, Discipline, Department, Sub-department, service, discipline Definition 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. Comments 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. Data type CodeableConcept Binding Codes for diagnostic service sections. ?? (example) Pattern { "coding": [ { "system": "http://hl7.org/fhir/v2/0074", "code": "LAB" } ] } Mappings v2: OBR-24 rim: inboundRelationship[typeCode=COMP].source[classCode=LIST, moodCode=EVN, code < LabService].code w5: class argonaut-dq-dstu2: DiagnosticReport.category
code	S Σ	1..1	CodeableConceptBinding	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.code Short description US Core Laboratory Report Order Code Alternate names Type Definition The test, panel or battery that was ordered. Comments UsageNote= The typical patterns for codes are: 1) a LOINC code either as a translation from a "local" code or as a primary code, or 2) a local code only if no suitable LOINC exists, or 3) both the local and the LOINC translation. Systems SHALL be capable of sending the local code if one exists. Data type CodeableConcept Binding LOINC codes ?? (extensible) Mappings workflow: Event.code v2: OBR-4 (HL7 v2 doesn't provide an easy way to indicate both the ordered test and the performed panel) rim: code w5: what argonaut-dq-dstu2: DiagnosticReport.code
subject	S Σ	1..1	Reference(http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient)	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.subject Short description The subject of the report - usually, but not always, the patient Alternate names Patient Definition 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. Requirements SHALL know the subject context. Data type Reference(http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient) Mappings workflow: Event.subject v2: PID-3 (no HL7 v2 mapping for Group or Device) rim: participation[typeCode=SBJ] w5: who.focus argonaut-dq-dstu2: DiagnosticReport.subject
context	Σ	0..1	Reference(http://hl7.org/fhir/StructureDefinition/Encounter \| http://hl7.org/fhir/StructureDefinition/EpisodeOfCare)	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.context Short description Health care event when test ordered Alternate names Encounter Definition The healthcare event (e.g. a patient and healthcare provider interaction) which this DiagnosticReport per is about. Requirements Links the request to the Encounter context. Comments This will typically be the encounter the event occurred within, but some events may be initiated prior to or after the official completion of an encounter or episode but still be tied to the context of the encounter or episode (e.g. pre-admission lab tests). Data type Reference(http://hl7.org/fhir/StructureDefinition/Encounter \| http://hl7.org/fhir/StructureDefinition/EpisodeOfCare) Mappings workflow: Event.context v2: PV1-19 rim: inboundRelationship[typeCode=COMP].source[classCode=ENC, moodCode=EVN] w5: context
effective[x]	S Σ	1..1		There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.effective[x] Short description Specimen Collection Datetime or Period Alternate names Observation time, Effective Time, Occurrence Definition This is the Specimen Collection Datetime or Period which is the physically relevent dateTime for laboratory tests. Requirements Need to know where in the patient history to file/present this report. Comments 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. Mappings workflow: Event.occurrence[x] v2: OBR-7 rim: effectiveTime w5: when.done argonaut-dq-dstu2: DiagnosticReport.effective[x]
effectiveDateTime			dateTime	There are no (further) constraints on this element Data type dateTime
effectivePeriod			Period	There are no (further) constraints on this element Data type Period
issued	S Σ	1..1	instant	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.issued Short description DateTime this version was released Alternate names Date Created, Date published, Date Issued Definition The date and time that this version of the report was released from the source diagnostic service. Requirements Clinicians need to be able to check the date that the report was released. Comments 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. Data type instant Mappings v2: OBR-22 rim: participation[typeCode=VRF or AUT].time w5: when.recorded argonaut-dq-dstu2: DiagnosticReport.issued
performer	S Σ	0..*	BackboneElement	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.performer Short description Participants in producing the report Alternate names Laboratory, Service, Practitioner, Department, Company Definition Indicates who or what participated in producing the report. Data type BackboneElement Constraints ele-1: All FHIR elements must have a @value or children `children().count() > id.count()` Mappings workflow: Event.performer v2: PRT-8 (where this PRT-4-Participation = "PO") rim: .participation[typeCode=PRF] w5: who.witness argonaut-dq-dstu2: NA (new element in STU3)
id		0..1	string	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.performer.id Short description xml:id (or equivalent in JSON) Definition unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.performer.extension Short description Additional Content defined by implementations Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Mappings rim: n/a
modifierExtension	Σ ?!	0..*	Extension	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.performer.modifierExtension Short description Extensions that cannot be ignored Alternate names extensions, user content, modifiers Definition May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Mappings rim: N/A
role	Σ	0..1	CodeableConcept	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.performer.role Short description Type of performer Definition Describes the type of participation (e.g. a responsible party, author, or verifier). Data type CodeableConcept Binding Indicate a role of diagnostic report performer ?? (example) Mappings workflow: Event.performer.role v2: PRT-8 (where this PRT-4-Participation = "PO") rim: .functionCode
actor	S Σ	1..1	Reference(http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner \| http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization)	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.performer.actor Short description Practitioner or Organization participant Definition The reference to the practitioner or organization involved in producing the report. For example, the diagnostic service that is responsible for issuing the report. Requirements 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. Comments This is not necessarily the source of the atomic data items. It is the entity that takes responsibility for the clinical report. Data type Reference(http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner \| http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization) Mappings workflow: Event.performer.actor v2: PRT-8 (where this PRT-4-Participation = "PO") rim: .role argonaut-dq-dstu2: DiagnosticReport.performer
specimen		0..*	Reference(http://hl7.org/fhir/StructureDefinition/Specimen)	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.specimen Short description Specimens this report is based on Definition Details about the specimens on which this diagnostic report is based. Requirements Need to be able to report information about the collected specimens on which the report is based. Comments 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. Data type Reference(http://hl7.org/fhir/StructureDefinition/Specimen) Mappings v2: SPM rim: participation[typeCode=SBJ]
result	S	0..*	Reference(http://hl7.org/fhir/us/core/StructureDefinition/us-core-observationresults)	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.result Short description Observations - simple, or complex nested groups Alternate names Data, Atomic Value, Result, Atomic result, Data, Test, Analyte, Battery, Organizer Definition Observations that are part of this diagnostic report. Observations can be simple name/value pairs (e.g. "atomic" results), or they can be grouping observations that include references to other members of the group (e.g. "panels"). Requirements Need to support individual results, or report groups of results, where the result grouping is arbitrary, but meaningful. This structure is recursive - observations can contain observations. Data type Reference(http://hl7.org/fhir/us/core/StructureDefinition/us-core-observationresults) Mappings v2: OBXs rim: outboundRelationship[typeCode=COMP].target argonaut-dq-dstu2: DiagnosticReport.result
imagingStudy		0..*	Reference(http://hl7.org/fhir/StructureDefinition/ImagingStudy \| http://hl7.org/fhir/StructureDefinition/ImagingManifest)	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.imagingStudy Short description Reference to full details of imaging associated with the diagnostic report Definition One 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. Comments ImagingStudy and ImageManifest 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. Data type Reference(http://hl7.org/fhir/StructureDefinition/ImagingStudy \| http://hl7.org/fhir/StructureDefinition/ImagingManifest) Mappings rim: outboundRelationship[typeCode=COMP].target[classsCode=DGIMG, moodCode=EVN]
image	S Σ	0..*	BackboneElement	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.image Short description Key images associated with this report Alternate names DICOM, Slides, Scans Definition A 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). Requirements Many diagnostic services include images in the report as part of their service. Data type BackboneElement Constraints ele-1: All FHIR elements must have a @value or children `children().count() > id.count()` Mappings v2: OBX? rim: outboundRelationship[typeCode=COMP].target argonaut-dq-dstu2: DiagnosticReport.image
id		0..1	string	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.image.id Short description xml:id (or equivalent in JSON) Definition unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.image.extension Short description Additional Content defined by implementations Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Mappings rim: n/a
modifierExtension	Σ ?!	0..*	Extension	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.image.modifierExtension Short description Extensions that cannot be ignored Alternate names extensions, user content, modifiers Definition May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Mappings rim: N/A
comment		0..1	string	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.image.comment Short description Comment about the image (e.g. explanation) Definition A 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. Requirements The provider of the report should make a comment about each image included in the report. Comments 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. Data type string Mappings rim: .inboundRelationship[typeCode=COMP].source[classCode=OBS, moodCode=EVN, code="annotation"].value
link	Σ	1..1	Reference(http://hl7.org/fhir/StructureDefinition/Media)	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.image.link Short description Reference to the image source Definition Reference to the image source. Data type Reference(http://hl7.org/fhir/StructureDefinition/Media) Mappings rim: .value.reference
conclusion		0..1	string	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.conclusion Short description Clinical Interpretation of test results Alternate names Report Definition Concise and clinically contextualized impression / summary of the diagnostic report. Requirements Need to be able to provide a conclusion that is not lost among the basic result data. Data type string Mappings v2: OBX rim: inboundRelationship[typeCode="SPRT"].source[classCode=OBS, moodCode=EVN, code=LOINC:48767-8].value (type=ST)
codedDiagnosis		0..*	CodeableConcept	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.codedDiagnosis Short description Codes for the conclusion Definition Codes for the conclusion. Data type CodeableConcept Binding Diagnosis codes provided as adjuncts to the report. ?? (example) Mappings v2: OBX rim: inboundRelationship[typeCode=SPRT].source[classCode=OBS, moodCode=EVN, code=LOINC:54531-9].value (type=CD)
presentedForm	S	0..*	Attachment	There are no (further) constraints on this element Element id DiagnosticReport:uscorediagnosticreport.presentedForm Short description Entire report as issued Definition Rich text representation of the entire result as issued by the diagnostic service. Multiple formats are allowed but they SHALL be semantically equivalent. Requirements Gives laboratory the ability to provide its own fully formatted report for clinical fidelity. Comments "application/pdf" is recommended as the most reliable and interoperable in this context. Data type Attachment Mappings v2: OBX rim: text (type=ED) argonaut-dq-dstu2: DiagnosticReport.presentedForm