DSTU2 QA Preview
This page is part of the FHIR Specification (v1.0.0: DSTU 2 Ballot 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions 
StructureDefinition for US Realm Laboratory Report
{
"resourceType": "StructureDefinition",
"id": "uslab-dr",
"text": {
"status": "generated",
"div": "<div>!-- Snipped for Brevity --></div>"
},
"url": "http://hl7.org/fhir/StructureDefinition/uslab-dr",
"name": "US Laboratory Diagnostic Report Profile",
"status": "draft",
"publisher": "Health Level Seven International (Orders and Observations - US Lab)",
"contact": [
{
"telecom": [
{
"system": "other",
"value": "http://hl7.org"
}
]
}
],
"date": "2014-11-19",
"description": "US Realm Laboratory Report",
"kind": "resource",
"constrainedType": "DiagnosticReport",
"abstract": false,
"base": "http://hl7.org/fhir/StructureDefinition/DiagnosticReport",
"snapshot": {
"element": [
{
"path": "DiagnosticReport",
"name": "USLab-DR",
"short": "US Realm Laboratory Report",
"definition": "The scope is the sending of lab results from a laboratory to an ambulatory provider.",
"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.",
"alias": [
"Report",
"Test",
"Result",
"Results",
"Labs",
"Laboratory",
"Lab Result",
"Lab Report"
],
"min": 0,
"max": "*",
"base": {
"path": "DiagnosticReport",
"min": 0,
"max": "*"
},
"type": [
{
"code": "DiagnosticReport"
}
],
"mapping": [
{
"identity": "rim",
"map": "Observation[classCode=OBS, moodCode=EVN]"
},
{
"identity": "w5",
"map": "clinical.diagnostics"
}
]
},
{
"path": "DiagnosticReport.id",
"short": "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. Bundles always have an id, though it is usually a generated UUID.",
"min": 0,
"max": "1",
"base": {
"path": "DiagnosticReport.id",
"min": 0,
"max": "1"
},
"type": [
{
"code": "id"
}
],
"isSummary": true
},
{
"path": "DiagnosticReport.meta",
"short": "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.",
"min": 0,
"max": "1",
"base": {
"path": "DiagnosticReport.meta",
"min": 0,
"max": "1"
},
"type": [
{
"code": "Meta"
}
],
"isSummary": true
},
{
"path": "DiagnosticReport.implicitRules",
"short": "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 as much as possible.",
"min": 0,
"max": "1",
"base": {
"path": "DiagnosticReport.implicitRules",
"min": 0,
"max": "1"
},
"type": [
{
"code": "uri"
}
],
"isModifier": true,
"isSummary": true
},
{
"path": "DiagnosticReport.language",
"short": "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).",
"min": 0,
"max": "1",
"base": {
"path": "DiagnosticReport.language",
"min": 0,
"max": "1"
},
"type": [
{
"code": "code"
}
],
"binding": {
"strength": "required",
"description": "A human language",
"valueSetUri": "http://tools.ietf.org/html/bcp47"
}
},
{
"path": "DiagnosticReport.text",
"short": "Text summary of the resource, for human interpretation",
"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.",
"alias": [
"narrative",
"html",
"xhtml",
"display"
],
"min": 0,
"max": "1",
"base": {
"path": "DiagnosticReport.text",
"min": 0,
"max": "1"
},
"type": [
{
"code": "Narrative"
}
],
"condition": [
"dom-1"
],
"mapping": [
{
"identity": "rim",
"map": "Act.text?"
}
]
},
{
"path": "DiagnosticReport.contained",
"short": "Contained, inline 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.",
"alias": [
"inline resources",
"anonymous resources",
"contained resources"
],
"min": 0,
"max": "*",
"base": {
"path": "DiagnosticReport.contained",
"min": 0,
"max": "*"
},
"type": [
{
"code": "Resource"
}
],
"mapping": [
{
"identity": "rim",
"map": "N/A"
}
]
},
{
"path": "DiagnosticReport.extension",
"short": "Additional Content defined by implementations",
"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.",
"alias": [
"extensions",
"user content"
],
"min": 0,
"max": "*",
"base": {
"path": "DiagnosticReport.extension",
"min": 0,
"max": "*"
},
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "N/A"
}
]
},
{
"path": "DiagnosticReport.modifierExtension",
"short": "Extensions that cannot be ignored",
"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.",
"alias": [
"extensions",
"user content"
],
"min": 0,
"max": "*",
"base": {
"path": "DiagnosticReport.modifierExtension",
"min": 0,
"max": "*"
},
"type": [
{
"code": "Extension"
}
],
"isModifier": true,
"mapping": [
{
"identity": "rim",
"map": "N/A"
}
]
},
{
"path": "DiagnosticReport.identifier",
"short": "Id for external references to this report",
"definition": "The local ID assigned to the report by the order filler, usually by the Information System of the diagnostic service provider.",
"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.",
"alias": [
"ReportID"
],
"min": 1,
"max": "*",
"base": {
"path": "DiagnosticReport.identifier",
"min": 0,
"max": "*"
},
"type": [
{
"code": "Identifier"
}
],
"mustSupport": true,
"isSummary": true,
"mapping": [
{
"identity": "v2",
"map": "OBR-51-Observation Group ID (todo: check semantic intent of OBR-51 with OOWG)"
},
{
"identity": "rim",
"map": "id"
},
{
"identity": "w5",
"map": "id"
}
]
},
{
"path": "DiagnosticReport.identifier.id",
"representation": [
"xmlAttr"
],
"short": "xml:id (or equivalent in JSON)",
"definition": "unique id for the element within a resource (for internal references).",
"min": 0,
"max": "1",
"base": {
"path": "Identifier.id",
"min": 0,
"max": "1"
},
"type": [
{
"code": "id"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "DiagnosticReport.identifier.extension",
"short": "Additional Content defined by implementations",
"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.",
"alias": [
"extensions",
"user content"
],
"min": 0,
"max": "*",
"base": {
"path": "Identifier.extension",
"min": 0,
"max": "*"
},
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "DiagnosticReport.identifier.use",
"short": "usual | official | temp | secondary (If known)",
"definition": "The purpose of this identifier.",
"comments": "This is labeled as \"Is Modifier\" because applications should not mistake a temporary id for a permanent one. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.",
"requirements": "Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.",
"min": 1,
"max": "1",
"base": {
"path": "Identifier.use",
"min": 0,
"max": "1"
},
"type": [
{
"code": "code"
}
],
"mustSupport": true,
"isModifier": true,
"isSummary": true,
"binding": {
"strength": "required",
"description": "Identifies the purpose for this identifier, if known",
"valueSetReference": {
"reference": "http://hl7.org/fhir/ValueSet/identifier-use"
}
},
"mapping": [
{
"identity": "v2",
"map": "N/A"
},
{
"identity": "rim",
"map": "Role.code or implied by context"
}
]
},
{
"path": "DiagnosticReport.identifier.type",
"short": "Description of identifier",
"definition": "A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.",
"comments": "This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. \n\nWhere the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.",
"requirements": "Allows users to make use of identifiers when the identifier system is not known.",
"min": 0,
"max": "1",
"base": {
"path": "Identifier.type",
"min": 0,
"max": "1"
},
"type": [
{
"code": "CodeableConcept"
}
],
"isSummary": true,
"binding": {
"strength": "extensible",
"description": "A coded type for an identifier that can be used to determine which identifier to use for a specific purpose",
"valueSetReference": {
"reference": "http://hl7.org/fhir/ValueSet/identifier-type"
}
},
"mapping": [
{
"identity": "v2",
"map": "CX.5"
},
{
"identity": "rim",
"map": "Role.code or implied by context"
}
]
},
{
"path": "DiagnosticReport.identifier.system",
"short": "Lab URI",
"definition": "The URI for the laboratory Issuing the report. This establishes the namespace in which set of possible id values is unique.",
"requirements": "There are many sequences of identifiers. To perform matching, we need to know what sequence we're dealing with. The system identifies a particular sequence or set of unique identifiers.",
"min": 1,
"max": "1",
"base": {
"path": "Identifier.system",
"min": 0,
"max": "1"
},
"type": [
{
"code": "uri"
}
],
"exampleUri": "http://www.acme.com/identifiers/patient or urn:ietf:rfc:3986 if the Identifier.value itself is a full uri",
"mustSupport": true,
"isSummary": true,
"mapping": [
{
"identity": "v2",
"map": "CX.4 / EI-2-4"
},
{
"identity": "rim",
"map": "II.root or Role.id.root"
},
{
"identity": "servd",
"map": "./IdentifierType"
}
]
},
{
"path": "DiagnosticReport.identifier.value",
"short": "The value that is unique",
"definition": "The portion of the identifier typically displayed to the user and which is unique within the context of the system.",
"comments": "If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986.",
"min": 1,
"max": "1",
"base": {
"path": "Identifier.value",
"min": 0,
"max": "1"
},
"type": [
{
"code": "string"
}
],
"exampleString": "123456",
"mustSupport": true,
"isSummary": true,
"mapping": [
{
"identity": "v2",
"map": "CX.1 / EI.1"
},
{
"identity": "rim",
"map": "II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)"
},
{
"identity": "servd",
"map": "./Value"
}
]
},
{
"path": "DiagnosticReport.identifier.period",
"short": "Time period when id is/was valid for use",
"definition": "Time period during which identifier is/was valid for use.",
"min": 0,
"max": "1",
"base": {
"path": "Identifier.period",
"min": 0,
"max": "1"
},
"type": [
{
"code": "Period"
}
],
"isSummary": true,
"mapping": [
{
"identity": "v2",
"map": "CX.7 + CX.8"
},
{
"identity": "rim",
"map": "Role.effectiveTime or implied by context"
},
{
"identity": "servd",
"map": "./StartDate and ./EndDate"
}
]
},
{
"path": "DiagnosticReport.identifier.assigner",
"short": "Organization that issued id (may be just text)",
"definition": "Organization that issued/manages the identifier.",
"comments": "The reference may be just a text description of the assigner.",
"min": 0,
"max": "1",
"base": {
"path": "Identifier.assigner",
"min": 0,
"max": "1"
},
"type": [
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/Organization"
]
}
],
"isSummary": true,
"mapping": [
{
"identity": "v2",
"map": "CX.4 / (CX.4,CX.9,CX.10)"
},
{
"identity": "rim",
"map": "II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper"
},
{
"identity": "servd",
"map": "./IdentifierIssuingAuthority"
}
]
},
{
"path": "DiagnosticReport.status",
"short": "registered | partial | final | corrected | appended | cancelled | entered-in-error",
"definition": "The status of the diagnostic report as a whole.",
"comments": "This is labeled as \"Is Modifier\" because applications need to take appropriate action if a report is withdrawn.",
"requirements": "Diagnostic services routinely issue provisional/incomplete reports, and sometimes withdraw previously released reports.",
"min": 1,
"max": "1",
"base": {
"path": "DiagnosticReport.status",
"min": 1,
"max": "1"
},
"type": [
{
"code": "code"
}
],
"mustSupport": true,
"isModifier": true,
"isSummary": true,
"binding": {
"strength": "required",
"description": "The status of the diagnostic report as a whole",
"valueSetReference": {
"reference": "http://hl7.org/fhir/ValueSet/diagnostic-report-status"
}
},
"mapping": [
{
"identity": "v2",
"map": "OBR-25-Result Status (not 1:1 mapping)"
},
{
"identity": "rim",
"map": "statusCode Note: final and amended are distinguished by whether observation is the subject of a ControlAct event of type \"revise\""
},
{
"identity": "w5",
"map": "status"
}
]
},
{
"path": "DiagnosticReport.category",
"short": "Service category",
"definition": "A code that classifies the dlinical 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.",
"alias": [
"Department",
"Sub-department",
"service",
"discipline"
],
"min": 0,
"max": "1",
"base": {
"path": "DiagnosticReport.category",
"min": 0,
"max": "1"
},
"type": [
{
"code": "CodeableConcept"
}
],
"isSummary": true,
"binding": {
"strength": "example",
"description": "Codes for diagnostic service sections",
"valueSetReference": {
"reference": "http://hl7.org/fhir/ValueSet/diagnostic-service-sections"
}
},
"mapping": [
{
"identity": "v2",
"map": "OBR-24-Diagnostic Service Section ID"
},
{
"identity": "rim",
"map": "inboundRelationship[typeCode=COMP].source[classCode=LIST, moodCode=EVN, code < LabService].code"
},
{
"identity": "w5",
"map": "class"
}
]
},
{
"path": "DiagnosticReport.code",
"short": "US Realm Laboratory Report Order Code",
"definition": "The laboratory 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.",
"min": 1,
"max": "1",
"base": {
"path": "DiagnosticReport.code",
"min": 1,
"max": "1"
},
"type": [
{
"code": "CodeableConcept"
}
],
"mustSupport": true,
"isSummary": true,
"binding": {
"strength": "preferred",
"description": "Codes that describe Diagnostic Reports",
"valueSetReference": {
"reference": "http://hl7.org/fhir/ValueSet/report-codes"
}
},
"mapping": [
{
"identity": "v2",
"map": "OBR-4-Universal Service ID (V2 doesn't provide an easy way to indicate both the ordered test and the performed panel)"
},
{
"identity": "rim",
"map": "code"
},
{
"identity": "w5",
"map": "what"
}
]
},
{
"path": "DiagnosticReport.code.id",
"representation": [
"xmlAttr"
],
"short": "xml:id (or equivalent in JSON)",
"definition": "unique id for the element within a resource (for internal references).",
"min": 0,
"max": "1",
"base": {
"path": "CodeableConcept.id",
"min": 0,
"max": "1"
},
"type": [
{
"code": "id"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "DiagnosticReport.code.extension",
"short": "Additional Content defined by implementations",
"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.",
"alias": [
"extensions",
"user content"
],
"min": 0,
"max": "*",
"base": {
"path": "CodeableConcept.extension",
"min": 0,
"max": "*"
},
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "DiagnosticReport.code.coding",
"name": "USLabLOINCCoding",
"short": "Code defined by a terminology system",
"definition": "A reference to a code defined by a terminology system.",
"comments": "Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the 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 labelled as UserSelected = true.",
"requirements": "Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings.",
"min": 1,
"max": "*",
"base": {
"path": "CodeableConcept.coding",
"min": 0,
"max": "*"
},
"type": [
{
"code": "Coding"
}
],
"mustSupport": true,
"isSummary": true,
"binding": {
"strength": "required",
"description": "LOINC codes",
"valueSetReference": {
"reference": "http://hl7.org/fhir/ValueSet/uslab-obs-codes"
}
},
"mapping": [
{
"identity": "orim",
"map": "fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding"
},
{
"identity": "v2",
"map": "C*E.1-8, C*E.10-22"
},
{
"identity": "rim",
"map": "union(., ./translation)"
}
]
},
{
"path": "DiagnosticReport.code.coding.id",
"representation": [
"xmlAttr"
],
"short": "xml:id (or equivalent in JSON)",
"definition": "unique id for the element within a resource (for internal references).",
"min": 0,
"max": "1",
"base": {
"path": "Coding.id",
"min": 0,
"max": "1"
},
"type": [
{
"code": "id"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "DiagnosticReport.code.coding.extension",
"short": "Additional Content defined by implementations",
"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.",
"alias": [
"extensions",
"user content"
],
"min": 0,
"max": "*",
"base": {
"path": "Coding.extension",
"min": 0,
"max": "*"
},
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "DiagnosticReport.code.coding.system",
"short": "Identity of the terminology system",
"definition": "The identification of the code system that defines the meaning of the symbol in the code.",
"comments": "The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously.",
"requirements": "Need to be unambiguous about the source of the definition of the symbol.",
"min": 1,
"max": "1",
"base": {
"path": "Coding.system",
"min": 0,
"max": "1"
},
"type": [
{
"code": "uri"
}
],
"mustSupport": true,
"isSummary": true,
"mapping": [
{
"identity": "orim",
"map": "fhir:Coding.system rdfs:subPropertyOf dt:CDCoding.codeSystem"
},
{
"identity": "v2",
"map": "C*E.3"
},
{
"identity": "rim",
"map": "./codeSystem"
}
]
},
{
"path": "DiagnosticReport.code.coding.version",
"short": "Version of the system - if relevant",
"definition": "The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.",
"comments": "Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.",
"min": 0,
"max": "1",
"base": {
"path": "Coding.version",
"min": 0,
"max": "1"
},
"type": [
{
"code": "string"
}
],
"isSummary": true,
"mapping": [
{
"identity": "orim",
"map": "fhir:Coding.version rdfs:subPropertyOf dt:CDCoding.codeSystemVersion"
},
{
"identity": "v2",
"map": "C*E.7"
},
{
"identity": "rim",
"map": "./codeSystemVersion"
}
]
},
{
"path": "DiagnosticReport.code.coding.code",
"short": "Symbol in syntax defined by the system",
"definition": "A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).",
"comments": "Logical Observation Identifiers Names and Codes (LOINC) is a database and universal standard for identifying medical laboratory observations.",
"requirements": "Need to refer to a particular code in the system.",
"min": 1,
"max": "1",
"base": {
"path": "Coding.code",
"min": 0,
"max": "1"
},
"type": [
{
"code": "code"
}
],
"mustSupport": true,
"isSummary": true,
"mapping": [
{
"identity": "orim",
"map": "fhir:Coding.code rdfs:subPropertyOf dt:CDCoding.code"
},
{
"identity": "v2",
"map": "C*E.1"
},
{
"identity": "rim",
"map": "./code"
}
]
},
{
"path": "DiagnosticReport.code.coding.display",
"short": "Representation defined by the system",
"definition": "A representation of the meaning of the code in the system, following the rules of the system.",
"comments": "When using LOINC 'long common name' is preferred although the LOINC 'short name' or the LOINC 'fully-specified name can also be used. ( http://lionc.org.terms-of-use).",
"requirements": "Need to be able to carry a human-readable meaning of the code for readers that do not know the system.",
"min": 0,
"max": "1",
"base": {
"path": "Coding.display",
"min": 0,
"max": "1"
},
"type": [
{
"code": "string"
}
],
"mustSupport": true,
"isSummary": true,
"mapping": [
{
"identity": "orim",
"map": "fhir:Coding.display rdfs:subPropertyOf dt:CDCoding.displayName"
},
{
"identity": "v2",
"map": "C*E.2 - but note this is not well followed"
},
{
"identity": "rim",
"map": "CV.displayName"
}
]
},
{
"path": "DiagnosticReport.code.coding.userSelected",
"short": "If this coding was chosen directly by the user",
"definition": "Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays).",
"comments": "Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.",
"requirements": "This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.",
"min": 0,
"max": "1",
"base": {
"path": "Coding.userSelected",
"min": 0,
"max": "1"
},
"type": [
{
"code": "boolean"
}
],
"isSummary": true,
"mapping": [
{
"identity": "orim",
"map": "fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map; fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\\#true a [ fhir:source \"true\"; fhir:target dt:CDCoding.codingRationale\\#O ]"
},
{
"identity": "v2",
"map": "Sometimes implied by being first"
},
{
"identity": "rim",
"map": "CD.codingRationale"
}
]
},
{
"path": "DiagnosticReport.code.text",
"short": "Display text",
"definition": "This is the laboratory defined display text for the report if different from the code display text(s).",
"comments": "If this exists, this is the text to be used for display.",
"requirements": "Used when the laboratory define how the dsplay text if different from the code display text.",
"min": 0,
"max": "1",
"base": {
"path": "CodeableConcept.text",
"min": 0,
"max": "1"
},
"type": [
{
"code": "string"
}
],
"mustSupport": true,
"isSummary": true,
"mapping": [
{
"identity": "orim",
"map": "fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText"
},
{
"identity": "v2",
"map": "C*E.9. But note many systems use C*E.2 for this"
},
{
"identity": "rim",
"map": "./originalText[mediaType/code=\"text/plain\"]/data"
}
]
},
{
"path": "DiagnosticReport.subject",
"short": "The subject of the report, usually, but not always, the 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.",
"alias": [
"Patient"
],
"min": 1,
"max": "1",
"base": {
"path": "DiagnosticReport.subject",
"min": 1,
"max": "1"
},
"type": [
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/uslab-patient"
]
},
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/uslab-phpatient"
]
}
],
"mustSupport": true,
"isSummary": true,
"mapping": [
{
"identity": "v2",
"map": "PID-3-Patient ID List (no V2 mapping for Group or Device)"
},
{
"identity": "rim",
"map": "participation[typeCode=SBJ]"
},
{
"identity": "w5",
"map": "who.focus"
}
]
},
{
"path": "DiagnosticReport.encounter",
"short": "Health care event when test ordered",
"definition": "The link to the health care event (encounter) when the order was made.",
"min": 0,
"max": "1",
"base": {
"path": "DiagnosticReport.encounter",
"min": 0,
"max": "1"
},
"type": [
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/Encounter"
]
}
],
"isSummary": true,
"mapping": [
{
"identity": "rim",
"map": "inboundRelationship[typeCode=COMP].source[classCode=ENC, moodCode=EVN]"
},
{
"identity": "w5",
"map": "context"
}
]
},
{
"path": "DiagnosticReport.effective[x]",
"short": "Specimen Collection Datetime or Period",
"definition": "This is the Specimen Collection Datetime or Period which is the physically relevent dateTime for laboratory tests.",
"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.",
"requirements": "Need to know where in the patient history to file/present this report.",
"alias": [
"Observation time",
"Effective Time"
],
"min": 1,
"max": "1",
"base": {
"path": "DiagnosticReport.effective[x]",
"min": 1,
"max": "1"
},
"type": [
{
"code": "dateTime"
},
{
"code": "Period"
}
],
"mustSupport": true,
"isSummary": true,
"mapping": [
{
"identity": "v2",
"map": "OBR-7-Observation Date/Time"
},
{
"identity": "rim",
"map": "effectiveTime"
},
{
"identity": "w5",
"map": "when.done"
}
]
},
{
"path": "DiagnosticReport.issued",
"short": "DateTime this version was released",
"definition": "The date and time that this version of the report was released from the source diagnostic service.",
"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 .",
"requirements": "Clinicians need to be able to check the date that the report was released.",
"alias": [
"Date Created",
"Date published",
"Date Issued"
],
"min": 1,
"max": "1",
"base": {
"path": "DiagnosticReport.issued",
"min": 1,
"max": "1"
},
"type": [
{
"code": "instant"
}
],
"mustSupport": true,
"isSummary": true,
"mapping": [
{
"identity": "v2",
"map": "OBR-22-Results Rpt/Status Chng - Date/Time"
},
{
"identity": "rim",
"map": "participation[typeCode=VRF or AUT].time"
},
{
"identity": "w5",
"map": "when.recorded"
}
]
},
{
"path": "DiagnosticReport.performer",
"short": "Responsible Diagnostic Service",
"definition": "The diagnostic service that is responsible for issuing the report.",
"comments": "This is not necessarily the source of the atomic data items - it is the entity that takes responsibility for the clinical 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.",
"alias": [
"Laboratory",
"Service",
"Practitioner",
"Department",
"Company"
],
"min": 0,
"max": "1",
"base": {
"path": "DiagnosticReport.performer",
"min": 1,
"max": "1"
},
"type": [
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/uslab-pract"
]
}
],
"mustSupport": true,
"isSummary": true,
"mapping": [
{
"identity": "v2",
"map": "PRT-8-Participation Organization (where this PRT-4-Participation = \"PO\")"
},
{
"identity": "rim",
"map": "participation[typeCode=AUT].role[classCode=ASSIGN].scoper"
},
{
"identity": "w5",
"map": "who.witness"
}
]
},
{
"path": "DiagnosticReport.request",
"short": "What was requested",
"definition": "Details concerning a test or procedure requested.",
"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.",
"requirements": "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": 1,
"max": "*",
"base": {
"path": "DiagnosticReport.request",
"min": 0,
"max": "*"
},
"type": [
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/uslab-do"
]
}
],
"mustSupport": true,
"mapping": [
{
"identity": "rim",
"map": "outboundRelationship[typeCode=FLFS].target"
}
]
},
{
"path": "DiagnosticReport.specimen",
"short": "Specimens this report is based on",
"definition": "Details about the specimens on which this diagnostic 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.",
"requirements": "Need to be able to report information about the collected specimens on which the report is based.",
"min": 0,
"max": "*",
"base": {
"path": "DiagnosticReport.specimen",
"min": 0,
"max": "*"
},
"type": [
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/uslab-spec"
]
}
],
"mustSupport": true,
"mapping": [
{
"identity": "v2",
"map": "SPM"
},
{
"identity": "rim",
"map": "participation[typeCode=SBJ]"
}
]
},
{
"path": "DiagnosticReport.result",
"short": "Observations - simple, or complex nested groups",
"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 be able to individual results, or report groups of results, where the result grouping is arbitrary, but meaningful. This structure is recursive - observations can contain observations.",
"alias": [
"Data",
"Atomic Value",
"Result",
"Atomic result",
"Data",
"Test",
"Analyte",
"Battery",
"Organiser"
],
"min": 0,
"max": "*",
"base": {
"path": "DiagnosticReport.result",
"min": 0,
"max": "*"
},
"type": [
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/uslab-obscode"
]
},
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/uslab-obsquantity"
]
},
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/uslab-obsother"
]
},
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/uslab-obsratio"
]
},
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/uslab-obspanel"
]
},
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/uslab-obsrange"
]
}
],
"mustSupport": true,
"mapping": [
{
"identity": "rim",
"map": "outboundRelationship[typeCode=COMP].target"
}
]
},
{
"path": "DiagnosticReport.imagingStudy",
"short": "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": "dImagingStudy 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": 0,
"max": "0",
"base": {
"path": "DiagnosticReport.imagingStudy",
"min": 0,
"max": "*"
},
"type": [
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/ImagingStudy"
]
},
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/ImagingObjectSelection"
]
}
],
"mapping": [
{
"identity": "rim",
"map": "outboundRelationship[typeCode=COMP].target[classsCode=DGIMG, moodCode=EVN]"
}
]
},
{
"path": "DiagnosticReport.image",
"short": "Key images associated with this report",
"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.",
"alias": [
"DICOM",
"Slides",
"Scans"
],
"min": 0,
"max": "*",
"base": {
"path": "DiagnosticReport.image",
"min": 0,
"max": "*"
},
"type": [
{
"code": "BackboneElement"
}
],
"isSummary": true,
"mapping": [
{
"identity": "v2",
"map": "OBX?"
},
{
"identity": "rim",
"map": "outboundRelationship[typeCode=COMP].target"
}
]
},
{
"path": "DiagnosticReport.image.id",
"representation": [
"xmlAttr"
],
"short": "xml:id (or equivalent in JSON)",
"definition": "unique id for the element within a resource (for internal references).",
"min": 0,
"max": "1",
"base": {
"path": "DiagnosticReport.image.id",
"min": 0,
"max": "1"
},
"type": [
{
"code": "id"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "DiagnosticReport.image.extension",
"short": "Additional Content defined by implementations",
"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.",
"alias": [
"extensions",
"user content"
],
"min": 0,
"max": "*",
"base": {
"path": "DiagnosticReport.image.extension",
"min": 0,
"max": "*"
},
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "DiagnosticReport.image.modifierExtension",
"short": "Extensions that cannot be ignored",
"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.",
"alias": [
"extensions",
"user content",
"modifiers"
],
"min": 0,
"max": "*",
"base": {
"path": "DiagnosticReport.image.modifierExtension",
"min": 0,
"max": "*"
},
"type": [
{
"code": "Extension"
}
],
"isModifier": true,
"mapping": [
{
"identity": "rim",
"map": "N/A"
}
]
},
{
"path": "DiagnosticReport.image.comment",
"short": "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.",
"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.",
"requirements": "The provider of the report should make a comment about each image included in the report.",
"min": 0,
"max": "1",
"base": {
"path": "DiagnosticReport.image.comment",
"min": 0,
"max": "1"
},
"type": [
{
"code": "string"
}
],
"mapping": [
{
"identity": "rim",
"map": ".inboundRelationship[typeCode=COMP].source[classCode=OBS, moodCode=EVN, code=\"annotation\"].value"
}
]
},
{
"path": "DiagnosticReport.image.link",
"short": "Reference to the image source",
"definition": "Reference to the image source.",
"min": 1,
"max": "1",
"base": {
"path": "DiagnosticReport.image.link",
"min": 1,
"max": "1"
},
"type": [
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/Media"
]
}
],
"isSummary": true,
"mapping": [
{
"identity": "rim",
"map": ".value.reference"
}
]
},
{
"path": "DiagnosticReport.conclusion",
"short": "Clinical Interpretation of test results",
"definition": "Concise and clinically contextualized narrative interpretation of the diagnostic report.",
"comments": "Typically, a report is either [all data, no narrative (e.g. Core lab)] or [a mix of data with some concluding narrative (e.g. Structured Pathology Report, Bone Density)], or [all narrative (e.g. typical imaging report, histopathology)]. In all of these cases, the narrative goes in \"text\".",
"requirements": "Need to be able to provide a conclusion that is not lost amongst the basic result data.",
"alias": [
"Report"
],
"min": 0,
"max": "1",
"base": {
"path": "DiagnosticReport.conclusion",
"min": 0,
"max": "1"
},
"type": [
{
"code": "string"
}
],
"mustSupport": true,
"mapping": [
{
"identity": "v2",
"map": "OBX"
},
{
"identity": "rim",
"map": "inboundRelationship[typeCode=\"SPRT\"].source[classCode=OBS, moodCode=EVN, code=LOINC:48767-8].value (type=ST)"
}
]
},
{
"path": "DiagnosticReport.codedDiagnosis",
"short": "Codes for the conclusion",
"definition": "Codes for the conclusion.",
"min": 0,
"max": "*",
"base": {
"path": "DiagnosticReport.codedDiagnosis",
"min": 0,
"max": "*"
},
"type": [
{
"code": "CodeableConcept"
}
],
"mustSupport": true,
"binding": {
"strength": "preferred",
"description": "SNOMED CT findings codes provided as adjunct diagnosis to the report",
"valueSetReference": {
"reference": "http://hl7.org/fhir/ValueSet/uslab-clinical-findings"
}
},
"mapping": [
{
"identity": "v2",
"map": "OBX"
},
{
"identity": "rim",
"map": "inboundRelationship[typeCode=SPRT].source[classCode=OBS, moodCode=EVN, code=LOINC:54531-9].value (type=CD)"
}
]
},
{
"path": "DiagnosticReport.presentedForm",
"short": "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.",
"comments": "Application/pdf is recommended as the most reliable and interoperable in this context.",
"requirements": "Gives Laboratory the ability to provide its own fully formatted report for clinical fidelity.",
"min": 0,
"max": "*",
"base": {
"path": "DiagnosticReport.presentedForm",
"min": 0,
"max": "*"
},
"type": [
{
"code": "Attachment"
}
],
"mustSupport": true,
"mapping": [
{
"identity": "v2",
"map": "OBX"
},
{
"identity": "rim",
"map": "text (type=ED)"
}
]
}
]
},
"differential": {
"element": [
{
"path": "DiagnosticReport",
"name": "USLab-DR",
"short": "US Realm Laboratory Report",
"definition": "The scope is the sending of lab results from a laboratory to an ambulatory provider.",
"alias": [
"Lab Result",
"Lab Report"
],
"min": 0,
"max": "*",
"type": [
{
"code": "DiagnosticReport"
}
]
},
{
"path": "DiagnosticReport.identifier",
"min": 1,
"max": "*",
"mustSupport": true
},
{
"path": "DiagnosticReport.identifier.use",
"min": 1,
"max": "1",
"mustSupport": true
},
{
"path": "DiagnosticReport.identifier.system",
"short": "Lab URI",
"definition": "The URI for the laboratory Issuing the report. This establishes the namespace in which set of possible id values is unique.",
"min": 1,
"max": "1",
"mustSupport": true
},
{
"path": "DiagnosticReport.identifier.value",
"min": 1,
"max": "1",
"mustSupport": true
},
{
"path": "DiagnosticReport.status",
"min": 1,
"max": "1",
"mustSupport": true
},
{
"path": "DiagnosticReport.code",
"short": "US Realm Laboratory Report Order Code",
"definition": "The laboratory 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.",
"min": 1,
"max": "1",
"mustSupport": true
},
{
"path": "DiagnosticReport.code.coding",
"name": "USLabLOINCCoding",
"min": 1,
"max": "*",
"mustSupport": true,
"binding": {
"strength": "required",
"description": "LOINC codes",
"valueSetReference": {
"reference": "http://hl7.org/fhir/ValueSet/uslab-obs-codes"
}
}
},
{
"path": "DiagnosticReport.code.coding.system",
"min": 1,
"max": "1",
"mustSupport": true
},
{
"path": "DiagnosticReport.code.coding.code",
"comments": "Logical Observation Identifiers Names and Codes (LOINC) is a database and universal standard for identifying medical laboratory observations.",
"min": 1,
"max": "1",
"mustSupport": true
},
{
"path": "DiagnosticReport.code.coding.display",
"comments": "When using LOINC 'long common name' is preferred although the LOINC 'short name' or the LOINC 'fully-specified name can also be used. ( http://lionc.org.terms-of-use).",
"min": 0,
"max": "1",
"mustSupport": true
},
{
"path": "DiagnosticReport.code.text",
"short": "Display text",
"definition": "This is the laboratory defined display text for the report if different from the code display text(s).",
"comments": "If this exists, this is the text to be used for display.",
"requirements": "Used when the laboratory define how the dsplay text if different from the code display text.",
"min": 0,
"max": "1",
"mustSupport": true
},
{
"path": "DiagnosticReport.subject",
"min": 1,
"max": "1",
"type": [
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/uslab-patient"
]
},
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/uslab-phpatient"
]
}
],
"mustSupport": true
},
{
"path": "DiagnosticReport.effective[x]",
"short": "Specimen Collection Datetime or Period",
"definition": "This is the Specimen Collection Datetime or Period which is the physically relevent dateTime for laboratory tests.",
"min": 1,
"max": "1",
"type": [
{
"code": "dateTime"
},
{
"code": "Period"
}
],
"mustSupport": true
},
{
"path": "DiagnosticReport.issued",
"min": 1,
"max": "1",
"mustSupport": true
},
{
"path": "DiagnosticReport.performer",
"min": 0,
"max": "1",
"type": [
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/uslab-pract"
]
}
],
"mustSupport": true
},
{
"path": "DiagnosticReport.request",
"min": 1,
"max": "*",
"type": [
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/uslab-do"
]
}
],
"mustSupport": true
},
{
"path": "DiagnosticReport.specimen",
"min": 0,
"max": "*",
"type": [
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/uslab-spec"
]
}
],
"mustSupport": true
},
{
"path": "DiagnosticReport.result",
"min": 0,
"max": "*",
"type": [
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/uslab-obscode"
]
},
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/uslab-obsquantity"
]
},
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/uslab-obsother"
]
},
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/uslab-obsratio"
]
},
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/uslab-obspanel"
]
},
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/uslab-obsrange"
]
}
],
"mustSupport": true
},
{
"path": "DiagnosticReport.imagingStudy",
"min": 0,
"max": "0"
},
{
"path": "DiagnosticReport.conclusion",
"min": 0,
"max": "1",
"mustSupport": true
},
{
"path": "DiagnosticReport.codedDiagnosis",
"min": 0,
"max": "*",
"mustSupport": true,
"binding": {
"strength": "preferred",
"description": "SNOMED CT findings codes provided as adjunct diagnosis to the report",
"valueSetReference": {
"reference": "http://hl7.org/fhir/ValueSet/uslab-clinical-findings"
}
}
},
{
"path": "DiagnosticReport.presentedForm",
"min": 0,
"max": "*",
"mustSupport": true
}
]
}
}
© HL7.org 2011+. FHIR DSTU2 (v1.0.0-6850) generated on Tue, Sep 1, 2015 14:42+1000.
Links: What's a DSTU? |
Version History |
Table of Contents |
Compare to DSTU1 |
|
Propose a change