DSTU2
This page is part of the FHIR Specification (v1.0.2: DSTU 2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions 
. Page versions: R5 R4B R4 R3 R2
LipidProfile
<StructureDefinition xmlns="http://hl7.org/fhir"> <id value="lipidprofile"/> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml">to do</div> </text> <url value="http://hl7.org/fhir/StructureDefinition/lipidprofile"/> <name value="Example Lipid Profile"/> <status value="draft"/> <publisher value="Grahame Grieve"/> <contact> <telecom> <system value="other"/> <value value="grahame@healthintersections.com.au"/> </telecom> </contact> <date value="2012-05-12"/> <description value="Lipid Lab Report"/> <fhirVersion value="1.0.2"/> <kind value="resource"/> <constrainedType value="DiagnosticReport"/> <abstract value="false"/> <base value="http://hl7.org/fhir/StructureDefinition/DiagnosticReport"/> <snapshot> <element> <path value="DiagnosticReport"/> <name value="LipidProfile"/> <short value="Lipid Lab Report"/> <definition value="The findings and interpretation of a general lipd lab profile."/> <comments value="In this profile, mustSupport means that authoring systems must include the ability to report these elements, and processing systems must cater for them by either displaying them to the user or considering them appropriately in decision support systems."/> <alias value="Report"/> <alias value="Test"/> <alias value="Result"/> <alias value="Results"/> <alias value="Labs"/> <alias value="Laboratory"/> <min value="1"/> <max value="1"/> <base> <path value="DiagnosticReport"/> <min value="0"/> <max value="*"/> </base> <type> <code value="DiagnosticReport"/> </type> <mapping> <identity value="v2"/> <map value="ORU -> OBR"/> </mapping> <mapping> <identity value="rim"/> <map value="Observation[classCode=OBS, moodCode=EVN]"/> </mapping> <mapping> <identity value="w5"/> <map value="clinical.diagnostics"/> </mapping> </element> <element> <path value="DiagnosticReport.id"/> <short value="Logical id of this artifact"/> <definition value="The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes."/> <comments value="The only time that a resource does not have an id is when it is being submitted to the server using a create operation. Bundles always have an id, though it is usually a generated UUID."/> <min value="0"/> <max value="1"/> <base> <path value="DiagnosticReport.id"/> <min value="0"/> <max value="1"/> </base> <type> <code value="id"/> </type> <isSummary value="true"/> </element> <element> <path value="DiagnosticReport.meta"/> <short value="Metadata about the resource"/> <definition value="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."/> <min value="0"/> <max value="1"/> <base> <path value="DiagnosticReport.meta"/> <min value="0"/> <max value="1"/> </base> <type> <code value="Meta"/> </type> <isSummary value="true"/> </element> <element> <path value="DiagnosticReport.implicitRules"/> <short value="A set of rules under which this content was created"/> <definition value="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 value="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 as much as possible."/> <min value="0"/> <max value="1"/> <base> <path value="DiagnosticReport.implicitRules"/> <min value="0"/> <max value="1"/> </base> <type> <code value="uri"/> </type> <isModifier value="true"/> <isSummary value="true"/> </element> <element> <path value="DiagnosticReport.language"/> <short value="Language of the resource content"/> <definition value="The base language in which the resource is written."/> <comments value="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)."/> <min value="0"/> <max value="1"/> <base> <path value="DiagnosticReport.language"/> <min value="0"/> <max value="1"/> </base> <type> <code value="code"/> </type> <binding> <strength value="required"/> <description value="A human language."/> <valueSetUri value="http://tools.ietf.org/html/bcp47"/> </binding> </element> <element> <path value="DiagnosticReport.text"/> <short value="Text summary of the resource, for human interpretation"/> <definition value="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 value="Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative."/> <alias value="narrative"/> <alias value="html"/> <alias value="xhtml"/> <alias value="display"/> <min value="0"/> <max value="1"/> <base> <path value="DiagnosticReport.text"/> <min value="0"/> <max value="1"/> </base> <type> <code value="Narrative"/> </type> <condition value="dom-1"/> <mapping> <identity value="rim"/> <map value="Act.text?"/> </mapping> </element> <element> <path value="DiagnosticReport.contained"/> <short value="Contained, inline Resources"/> <definition value="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 value="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."/> <alias value="inline resources"/> <alias value="anonymous resources"/> <alias value="contained resources"/> <min value="0"/> <max value="*"/> <base> <path value="DiagnosticReport.contained"/> <min value="0"/> <max value="*"/> </base> <type> <code value="Resource"/> </type> <mapping> <identity value="rim"/> <map value="N/A"/> </mapping> </element> <element> <path value="DiagnosticReport.extension"/> <short value="Additional Content defined by implementations"/> <definition value="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 value="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."/> <alias value="extensions"/> <alias value="user content"/> <min value="0"/> <max value="*"/> <base> <path value="DiagnosticReport.extension"/> <min value="0"/> <max value="*"/> </base> <type> <code value="Extension"/> </type> <mapping> <identity value="rim"/> <map value="N/A"/> </mapping> </element> <element> <path value="DiagnosticReport.modifierExtension"/> <short value="Extensions that cannot be ignored"/> <definition value="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 value="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."/> <alias value="extensions"/> <alias value="user content"/> <min value="0"/> <max value="*"/> <base> <path value="DiagnosticReport.modifierExtension"/> <min value="0"/> <max value="*"/> </base> <type> <code value="Extension"/> </type> <isModifier value="true"/> <mapping> <identity value="rim"/> <map value="N/A"/> </mapping> </element> <element> <path value="DiagnosticReport.identifier"/> <short value="Id for external references to this report"/> <definition value="The local ID assigned to the report by the order filler, usually by the Information System of the diagnostic service provider."/> <requirements value="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."/> <alias value="ReportID"/> <min value="0"/> <max value="*"/> <base> <path value="DiagnosticReport.identifier"/> <min value="0"/> <max value="*"/> </base> <type> <code value="Identifier"/> </type> <isSummary value="true"/> <mapping> <identity value="v2"/> <map value="OBR-51"/> </mapping> <mapping> <identity value="rim"/> <map value="id"/> </mapping> <mapping> <identity value="w5"/> <map value="id"/> </mapping> </element> <element> <path value="DiagnosticReport.status"/> <short value="registered | partial | final | corrected | appended | cancelled | entered-in-error"/> <definition value="The status of the diagnostic report as a whole."/> <comments value="This is labeled as "Is Modifier" because applications need to take appropriate action if a report is withdrawn."/> <requirements value="Diagnostic services routinely issue provisional/incomplete reports, and sometimes withdraw previously released reports."/> <min value="1"/> <max value="1"/> <base> <path value="DiagnosticReport.status"/> <min value="1"/> <max value="1"/> </base> <type> <code value="code"/> </type> <isModifier value="true"/> <isSummary value="true"/> <binding> <strength value="required"/> <description value="The status of the diagnostic report as a whole."/> <valueSetReference> <reference value="http://hl7.org/fhir/ValueSet/diagnostic-report-status"/> </valueSetReference> </binding> <mapping> <identity value="v2"/> <map value="OBR-25 (not 1:1 mapping)"/> </mapping> <mapping> <identity value="rim"/> <map value="statusCode Note: final and amended are distinguished by whether observation is the subject of a ControlAct event of type "revise""/> </mapping> <mapping> <identity value="w5"/> <map value="status"/> </mapping> </element> <element> <path value="DiagnosticReport.category"/> <short value="Service category"/> <definition value="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 value="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."/> <alias value="Department"/> <alias value="Sub-department"/> <alias value="service"/> <alias value="discipline"/> <min value="0"/> <max value="1"/> <base> <path value="DiagnosticReport.category"/> <min value="0"/> <max value="1"/> </base> <type> <code value="CodeableConcept"/> </type> <isSummary value="true"/> <binding> <strength value="example"/> <description value="Codes for diagnostic service sections."/> <valueSetReference> <reference value="http://hl7.org/fhir/ValueSet/diagnostic-service-sections"/> </valueSetReference> </binding> <mapping> <identity value="v2"/> <map value="OBR-24"/> </mapping> <mapping> <identity value="rim"/> <map value="inboundRelationship[typeCode=COMP].source[classCode=LIST, moodCode=EVN, code < LabService].code"/> </mapping> <mapping> <identity value="w5"/> <map value="class"/> </mapping> </element> <element> <path value="DiagnosticReport.code"/> <short value="LOINC Code for Lipid Panel with LDL"/> <definition value="LOINC Code for Lipid Panel with LDL."/> <comments value="LOINC code includes "direct" LDL - does this mean LDL derived by measuring VLDL by ultracentrifugation? This panel includes both measured and calculated LDL."/> <min value="1"/> <max value="1"/> <base> <path value="DiagnosticReport.code"/> <min value="1"/> <max value="1"/> </base> <type> <code value="CodeableConcept"/> </type> <fixedCodeableConcept> <coding> <system value="http://loinc.org"/> <code value="57698-3"/> <display value="Lipid panel with direct LDL - Serum or Plasma"/> </coding> </fixedCodeableConcept> <isSummary value="true"/> <binding> <strength value="preferred"/> <description value="Codes that describe Diagnostic Reports."/> <valueSetReference> <reference value="http://hl7.org/fhir/ValueSet/report-codes"/> </valueSetReference> </binding> <mapping> <identity value="v2"/> <map value="OBR-4 (HL7 v2 doesn't provide an easy way to indicate both the ordered test and the performed panel)"/> </mapping> <mapping> <identity value="rim"/> <map value="code"/> </mapping> <mapping> <identity value="w5"/> <map value="what"/> </mapping> </element> <element> <path value="DiagnosticReport.subject"/> <short value="The subject of the report, usually, but not always, the patient"/> <definition value="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 value="SHALL know the subject context."/> <alias value="Patient"/> <min value="1"/> <max value="1"/> <base> <path value="DiagnosticReport.subject"/> <min value="1"/> <max value="1"/> </base> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/StructureDefinition/Patient"/> </type> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/StructureDefinition/Group"/> </type> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/StructureDefinition/Device"/> </type> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/StructureDefinition/Location"/> </type> <isSummary value="true"/> <mapping> <identity value="v2"/> <map value="PID-3 (no HL7 v2 mapping for Group or Device)"/> </mapping> <mapping> <identity value="rim"/> <map value="participation[typeCode=SBJ]"/> </mapping> <mapping> <identity value="w5"/> <map value="who.focus"/> </mapping> </element> <element> <path value="DiagnosticReport.encounter"/> <short value="Health care event when test ordered"/> <definition value="The link to the health care event (encounter) when the order was made."/> <min value="0"/> <max value="1"/> <base> <path value="DiagnosticReport.encounter"/> <min value="0"/> <max value="1"/> </base> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/StructureDefinition/Encounter"/> </type> <isSummary value="true"/> <mapping> <identity value="v2"/> <map value="PV1-19"/> </mapping> <mapping> <identity value="rim"/> <map value="inboundRelationship[typeCode=COMP].source[classCode=ENC, moodCode=EVN]"/> </mapping> <mapping> <identity value="w5"/> <map value="context"/> </mapping> </element> <element> <path value="DiagnosticReport.effective[x]"/> <short value="Clinically Relevant time/time-period for report"/> <definition value="The time or time-period the observed values are related to. When the subject of the report is a patient, this is usually either the time of the procedure or of specimen collection(s), but very often the source of the date/time is not known, only the date/time itself."/> <comments value="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."/> <requirements value="Need to know where in the patient history to file/present this report."/> <alias value="Observation time"/> <alias value="Effective Time"/> <min value="1"/> <max value="1"/> <base> <path value="DiagnosticReport.effective[x]"/> <min value="1"/> <max value="1"/> </base> <type> <code value="dateTime"/> </type> <type> <code value="Period"/> </type> <isSummary value="true"/> <mapping> <identity value="v2"/> <map value="OBR-7"/> </mapping> <mapping> <identity value="rim"/> <map value="effectiveTime"/> </mapping> <mapping> <identity value="w5"/> <map value="when.done"/> </mapping> </element> <element> <path value="DiagnosticReport.issued"/> <short value="DateTime this version was released"/> <definition value="The date and time that this version of the report was released from the source diagnostic service."/> <comments value="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."/> <requirements value="Clinicians need to be able to check the date that the report was released."/> <alias value="Date Created"/> <alias value="Date published"/> <alias value="Date Issued"/> <min value="1"/> <max value="1"/> <base> <path value="DiagnosticReport.issued"/> <min value="1"/> <max value="1"/> </base> <type> <code value="instant"/> </type> <isSummary value="true"/> <mapping> <identity value="v2"/> <map value="OBR-22"/> </mapping> <mapping> <identity value="rim"/> <map value="participation[typeCode=VRF or AUT].time"/> </mapping> <mapping> <identity value="w5"/> <map value="when.recorded"/> </mapping> </element> <element> <path value="DiagnosticReport.performer"/> <short value="Responsible Diagnostic Service"/> <definition value="The diagnostic service that is responsible for issuing the report."/> <comments value="This is not necessarily the source of the atomic data items. It is the entity that takes responsibility for the clinical report."/> <requirements value="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."/> <alias value="Laboratory"/> <alias value="Service"/> <alias value="Practitioner"/> <alias value="Department"/> <alias value="Company"/> <min value="1"/> <max value="1"/> <base> <path value="DiagnosticReport.performer"/> <min value="1"/> <max value="1"/> </base> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/StructureDefinition/Practitioner"/> </type> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/StructureDefinition/Organization"/> </type> <isSummary value="true"/> <mapping> <identity value="v2"/> <map value="PRT-8 (where this PRT-4-Participation = "PO")"/> </mapping> <mapping> <identity value="rim"/> <map value="participation[typeCode=AUT].role[classCode=ASSIGN].scoper"/> </mapping> <mapping> <identity value="w5"/> <map value="who.witness"/> </mapping> </element> <element> <path value="DiagnosticReport.request"/> <short value="What was requested"/> <definition value="Details concerning a test or procedure requested."/> <comments value="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."/> <requirements value="Need to be able to track completion of requests based on reports issued and also to report what diagnostic tests were requested (not always the same as what is delivered)."/> <min value="0"/> <max value="*"/> <base> <path value="DiagnosticReport.request"/> <min value="0"/> <max value="*"/> </base> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/StructureDefinition/DiagnosticOrder"/> </type> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/StructureDefinition/ProcedureRequest"/> </type> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/StructureDefinition/ReferralRequest"/> </type> <mapping> <identity value="v2"/> <map value="ORC? OBR-2/3?"/> </mapping> <mapping> <identity value="rim"/> <map value="outboundRelationship[typeCode=FLFS].target"/> </mapping> </element> <element> <path value="DiagnosticReport.specimen"/> <short value="Specimens this report is based on"/> <definition value="Details about the specimens on which this diagnostic report is based."/> <comments value="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."/> <requirements value="Need to be able to report information about the collected specimens on which the report is based."/> <min value="0"/> <max value="*"/> <base> <path value="DiagnosticReport.specimen"/> <min value="0"/> <max value="*"/> </base> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/StructureDefinition/Specimen"/> </type> <mapping> <identity value="v2"/> <map value="SPM"/> </mapping> <mapping> <identity value="rim"/> <map value="participation[typeCode=SBJ]"/> </mapping> </element> <element> <path value="DiagnosticReport.result"/> <slicing> <discriminator value="reference.code"/> <ordered value="true"/> <rules value="closed"/> </slicing> <short value="Observations - simple, or complex nested groups"/> <definition value="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 value="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."/> <alias value="Data"/> <alias value="Atomic Value"/> <alias value="Result"/> <alias value="Atomic result"/> <alias value="Data"/> <alias value="Test"/> <alias value="Analyte"/> <alias value="Battery"/> <alias value="Organizer"/> <min value="0"/> <max value="*"/> <base> <path value="DiagnosticReport.result"/> <min value="0"/> <max value="*"/> </base> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/StructureDefinition/Observation"/> </type> <mapping> <identity value="v2"/> <map value="OBXs"/> </mapping> <mapping> <identity value="rim"/> <map value="outboundRelationship[typeCode=COMP].target"/> </mapping> </element> <element> <path value="DiagnosticReport.result"/> <name value="Cholesterol"/> <short value="Cholesterol Result"/> <definition value="Reference to Cholesterol Result."/> <requirements value="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."/> <alias value="Data"/> <alias value="Atomic Value"/> <alias value="Result"/> <alias value="Atomic result"/> <alias value="Data"/> <alias value="Test"/> <alias value="Analyte"/> <alias value="Battery"/> <alias value="Organizer"/> <min value="1"/> <max value="1"/> <base> <path value="DiagnosticReport.result"/> <min value="0"/> <max value="*"/> </base> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/StructureDefinition/cholesterol"/> </type> <mustSupport value="true"/> <mapping> <identity value="v2"/> <map value="OBXs"/> </mapping> <mapping> <identity value="rim"/> <map value="outboundRelationship[typeCode=COMP].target"/> </mapping> </element> <element> <path value="DiagnosticReport.result"/> <name value="Triglyceride"/> <short value="Triglyceride Result"/> <definition value="Group of elements for Triglyceride result."/> <requirements value="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."/> <alias value="Data"/> <alias value="Atomic Value"/> <alias value="Result"/> <alias value="Atomic result"/> <alias value="Data"/> <alias value="Test"/> <alias value="Analyte"/> <alias value="Battery"/> <alias value="Organizer"/> <min value="1"/> <max value="1"/> <base> <path value="DiagnosticReport.result"/> <min value="0"/> <max value="*"/> </base> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/StructureDefinition/triglyceride"/> </type> <mustSupport value="true"/> <mapping> <identity value="v2"/> <map value="OBXs"/> </mapping> <mapping> <identity value="rim"/> <map value="outboundRelationship[typeCode=COMP].target"/> </mapping> </element> <element> <path value="DiagnosticReport.result"/> <name value="HDL Cholesterol"/> <short value="HDL Cholesterol Result"/> <definition value="Group of elements for HDL Cholesterol result."/> <requirements value="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."/> <alias value="Data"/> <alias value="Atomic Value"/> <alias value="Result"/> <alias value="Atomic result"/> <alias value="Data"/> <alias value="Test"/> <alias value="Analyte"/> <alias value="Battery"/> <alias value="Organizer"/> <min value="1"/> <max value="1"/> <base> <path value="DiagnosticReport.result"/> <min value="0"/> <max value="*"/> </base> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/StructureDefinition/hdlcholesterol"/> </type> <mustSupport value="true"/> <mapping> <identity value="v2"/> <map value="OBXs"/> </mapping> <mapping> <identity value="rim"/> <map value="outboundRelationship[typeCode=COMP].target"/> </mapping> </element> <element> <path value="DiagnosticReport.result"/> <name value="LDL Cholesterol"/> <short value="LDL Cholesterol result, if reported"/> <definition value="LDL Cholesterol result, if reported."/> <requirements value="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."/> <alias value="Data"/> <alias value="Atomic Value"/> <alias value="Result"/> <alias value="Atomic result"/> <alias value="Data"/> <alias value="Test"/> <alias value="Analyte"/> <alias value="Battery"/> <alias value="Organizer"/> <min value="0"/> <max value="1"/> <base> <path value="DiagnosticReport.result"/> <min value="0"/> <max value="*"/> </base> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/StructureDefinition/ldlcholesterol"/> </type> <mustSupport value="true"/> <mapping> <identity value="v2"/> <map value="OBXs"/> </mapping> <mapping> <identity value="rim"/> <map value="outboundRelationship[typeCode=COMP].target"/> </mapping> </element> <element> <path value="DiagnosticReport.imagingStudy"/> <short value="Reference to full details of imaging associated with the diagnostic report"/> <definition value="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 value="ImagingStudy and ImageObjectStudy 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."/> <min value="0"/> <max value="*"/> <base> <path value="DiagnosticReport.imagingStudy"/> <min value="0"/> <max value="*"/> </base> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/StructureDefinition/ImagingStudy"/> </type> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/StructureDefinition/ImagingObjectSelection"/> </type> <mapping> <identity value="rim"/> <map value="outboundRelationship[typeCode=COMP].target[classsCode=DGIMG, moodCode=EVN]"/> </mapping> </element> <element> <path value="DiagnosticReport.image"/> <short value="Key images associated with this report"/> <definition value="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 value="Many diagnostic services include images in the report as part of their service."/> <alias value="DICOM"/> <alias value="Slides"/> <alias value="Scans"/> <min value="0"/> <max value="*"/> <base> <path value="DiagnosticReport.image"/> <min value="0"/> <max value="*"/> </base> <type> <code value="BackboneElement"/> </type> <isSummary value="true"/> <mapping> <identity value="v2"/> <map value="OBX?"/> </mapping> <mapping> <identity value="rim"/> <map value="outboundRelationship[typeCode=COMP].target"/> </mapping> </element> <element> <path value="DiagnosticReport.image.id"/> <representation value="xmlAttr"/> <short value="xml:id (or equivalent in JSON)"/> <definition value="unique id for the element within a resource (for internal references)."/> <min value="0"/> <max value="1"/> <base> <path value="DiagnosticReport.image.id"/> <min value="0"/> <max value="1"/> </base> <type> <code value="id"/> </type> <mapping> <identity value="rim"/> <map value="n/a"/> </mapping> </element> <element> <path value="DiagnosticReport.image.extension"/> <short value="Additional Content defined by implementations"/> <definition value="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 value="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."/> <alias value="extensions"/> <alias value="user content"/> <min value="0"/> <max value="*"/> <base> <path value="DiagnosticReport.image.extension"/> <min value="0"/> <max value="*"/> </base> <type> <code value="Extension"/> </type> <mapping> <identity value="rim"/> <map value="n/a"/> </mapping> </element> <element> <path value="DiagnosticReport.image.modifierExtension"/> <short value="Extensions that cannot be ignored"/> <definition value="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 value="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."/> <alias value="extensions"/> <alias value="user content"/> <alias value="modifiers"/> <min value="0"/> <max value="*"/> <base> <path value="DiagnosticReport.image.modifierExtension"/> <min value="0"/> <max value="*"/> </base> <type> <code value="Extension"/> </type> <isModifier value="true"/> <mapping> <identity value="rim"/> <map value="N/A"/> </mapping> </element> <element> <path value="DiagnosticReport.image.comment"/> <short value="Comment about the image (e.g. explanation)"/> <definition value="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."/> <comments value="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."/> <requirements value="The provider of the report should make a comment about each image included in the report."/> <min value="0"/> <max value="1"/> <base> <path value="DiagnosticReport.image.comment"/> <min value="0"/> <max value="1"/> </base> <type> <code value="string"/> </type> <mapping> <identity value="rim"/> <map value=".inboundRelationship[typeCode=COMP].source[classCode=OBS, moodCode=EVN, code="annotation"] .value"/> </mapping> </element> <element> <path value="DiagnosticReport.image.link"/> <short value="Reference to the image source"/> <definition value="Reference to the image source."/> <min value="1"/> <max value="1"/> <base> <path value="DiagnosticReport.image.link"/> <min value="1"/> <max value="1"/> </base> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/StructureDefinition/Media"/> </type> <isSummary value="true"/> <mapping> <identity value="rim"/> <map value=".value.reference"/> </mapping> </element> <element> <path value="DiagnosticReport.conclusion"/> <short value="Clinical Interpretation of Lipid Panel"/> <definition value="May include diagnosis or suggestions for follow up testing."/> <comments value="It's not unusual for the lab to make some kind of interpretative comment on the set of results."/> <requirements value="Need to be able to provide a conclusion that is not lost among the basic result data."/> <alias value="Report"/> <min value="0"/> <max value="1"/> <base> <path value="DiagnosticReport.conclusion"/> <min value="0"/> <max value="1"/> </base> <type> <code value="string"/> </type> <mustSupport value="true"/> <mapping> <identity value="v2"/> <map value="OBX"/> </mapping> <mapping> <identity value="rim"/> <map value="inboundRelationship[typeCode="SPRT"].source[classCode=OBS, moodCode=EVN, code=LOINC:48767- 8].value (type=ST)"/> </mapping> </element> <element> <path value="DiagnosticReport.codedDiagnosis"/> <short value="No codes for a lipid panel"/> <definition value="No codes for a lipid panel."/> <comments value="Not used in this context."/> <min value="0"/> <max value="0"/> <base> <path value="DiagnosticReport.codedDiagnosis"/> <min value="0"/> <max value="*"/> </base> <type> <code value="CodeableConcept"/> </type> <binding> <strength value="example"/> <description value="Diagnoses codes provided as adjuncts to the report."/> <valueSetReference> <reference value="http://hl7.org/fhir/ValueSet/clinical-findings"/> </valueSetReference> </binding> <mapping> <identity value="v2"/> <map value="OBX"/> </mapping> <mapping> <identity value="rim"/> <map value="inboundRelationship[typeCode=SPRT].source[classCode=OBS, moodCode=EVN, code=LOINC:54531-9].value (type=CD)"/> </mapping> </element> <element> <path value="DiagnosticReport.presentedForm"/> <short value="Entire report as issued"/> <definition value="Rich text representation of the entire result as issued by the diagnostic service. Multiple formats are allowed but they SHALL be semantically equivalent."/> <comments value=""application/pdf" is recommended as the most reliable and interoperable in this context."/> <requirements value="Gives Laboratory the ability to provide its own fully formatted report for clinical fidelity."/> <min value="0"/> <max value="*"/> <base> <path value="DiagnosticReport.presentedForm"/> <min value="0"/> <max value="*"/> </base> <type> <code value="Attachment"/> </type> <mapping> <identity value="v2"/> <map value="OBX"/> </mapping> <mapping> <identity value="rim"/> <map value="text (type=ED)"/> </mapping> </element> </snapshot> <differential> <element> <path value="DiagnosticReport"/> <name value="LipidProfile"/> <short value="Lipid Lab Report"/> <definition value="The findings and interpretation of a general lipd lab profile."/> <comments value="In this profile, mustSupport means that authoring systems must include the ability to report these elements, and processing systems must cater for them by either displaying them to the user or considering them appropriately in decision support systems."/> <min value="1"/> <max value="1"/> <type> <code value="DiagnosticReport"/> </type> </element> <element> <path value="DiagnosticReport.code"/> <short value="LOINC Code for Lipid Panel with LDL"/> <definition value="LOINC Code for Lipid Panel with LDL."/> <comments value="LOINC code includes "direct" LDL - does this mean LDL derived by measuring VLDL by ultracentrifugation? This panel includes both measured and calculated LDL."/> <min value="1"/> <max value="1"/> <type> <code value="CodeableConcept"/> </type> <fixedCodeableConcept> <coding> <system value="http://loinc.org"/> <code value="57698-3"/> <display value="Lipid panel with direct LDL - Serum or Plasma"/> </coding> </fixedCodeableConcept> </element> <element> <path value="DiagnosticReport.result"/> <name value="Cholesterol"/> <slicing> <discriminator value="reference.code"/> <ordered value="true"/> <rules value="closed"/> </slicing> <short value="Cholesterol Result"/> <definition value="Reference to Cholesterol Result."/> <min value="1"/> <max value="1"/> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/StructureDefinition/cholesterol"/> </type> <mustSupport value="true"/> </element> <element> <path value="DiagnosticReport.result"/> <name value="Triglyceride"/> <short value="Triglyceride Result"/> <definition value="Group of elements for Triglyceride result."/> <min value="1"/> <max value="1"/> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/StructureDefinition/triglyceride"/> </type> <mustSupport value="true"/> </element> <element> <path value="DiagnosticReport.result"/> <name value="HDL Cholesterol"/> <short value="HDL Cholesterol Result"/> <definition value="Group of elements for HDL Cholesterol result."/> <min value="1"/> <max value="1"/> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/StructureDefinition/hdlcholesterol"/> </type> <mustSupport value="true"/> </element> <element> <path value="DiagnosticReport.result"/> <name value="LDL Cholesterol"/> <short value="LDL Cholesterol result, if reported"/> <definition value="LDL Cholesterol result, if reported."/> <min value="0"/> <max value="1"/> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/StructureDefinition/ldlcholesterol"/> </type> <mustSupport value="true"/> </element> <element> <path value="DiagnosticReport.conclusion"/> <short value="Clinical Interpretation of Lipid Panel"/> <definition value="May include diagnosis or suggestions for follow up testing."/> <comments value="It's not unusual for the lab to make some kind of interpretative comment on the set of results."/> <min value="0"/> <max value="1"/> <type> <code value="string"/> </type> <mustSupport value="true"/> </element> <element> <path value="DiagnosticReport.codedDiagnosis"/> <short value="No codes for a lipid panel"/> <definition value="No codes for a lipid panel."/> <comments value="Not used in this context."/> <min value="0"/> <max value="0"/> <type> <code value="CodeableConcept"/> </type> </element> </differential> </StructureDefinition>
© HL7.org 2011+. FHIR DSTU2 (v1.0.2-7202) generated on Sat, Oct 24, 2015 07:43+1100.
Links: Search |
Version History |
Table of Contents |
Compare to DSTU1 |
|
Propose a change