Pan-Canadian Patient Summary (PS-CA) IGuide v1.1.0 DFT

Releases of the PS-CA Implementation Guide may be found on a table on the Home Page of this Project.

DiagnosticReport (PS-CA)

Additional information on this profile (including the JSON & XML structure and detailed element descriptions) can be found at package/structuredefinition-profile-diagnosticreport-ca-ps.json

Profile

DiagnosticReport	I		DiagnosticReport	There are no (further) constraints on this element Element id DiagnosticReport Short description A Diagnostic report - a combination of request information, atomic results, images, interpretation, as well as formatted reports Alternate names Report, Test, Result, Results, Labs, Laboratory Definition The findings and interpretation of diagnostic tests performed on patients, groups of patients, devices, and locations, and/or specimens derived from these. The report includes clinical context such as requesting and provider information, and some mix of atomic results, images, textual and coded interpretations, and formatted representation of diagnostic reports. Comments This is intended to capture a single report and is not suitable for use in displaying summary information that covers multiple reports. For example, this resource has not been designed for laboratory cumulative reporting formats nor detailed structured reports for sequencing. Data type DiagnosticReport Constraints dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources `contained.contained.empty()` dom-4: If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated `contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()` dom-3: If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource `contained.where((('#'+id in (%resource.descendants().reference \| %resource.descendants().as(canonical) \| %resource.descendants().as(uri) \| %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()` dom-6: A resource should have narrative for robust management text.`div`.exists() dom-5: If a resource is contained in another resource, it SHALL NOT have a security label `contained.meta.security.empty()` Mappings rim: Entity. Role, or Act workflow: Event v2: ORU -> OBR rim: Observation[classCode=OBS, moodCode=EVN]
id	Σ	0..1	string	There are no (further) constraints on this element Element id DiagnosticReport.id Short description Logical id of this artifact Definition The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. Comments The only time that a resource does not have an id is when it is being submitted to the server using a create operation. Data type string
meta	Σ	0..1	Meta	There are no (further) constraints on this element Element id DiagnosticReport.meta Short description Metadata about the resource Definition The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource. Data type Meta Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
implicitRules	Σ ?!	0..1	uri	There are no (further) constraints on this element Element id DiagnosticReport.implicitRules Short description A set of rules under which this content was created Definition A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
language		0..1	codeBinding	There are no (further) constraints on this element Element id DiagnosticReport.language Short description Language of the resource content Definition The base language in which the resource is written. Comments Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). Data type code Binding A human language. CommonLanguages (preferred) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
text		0..1	Narrative	There are no (further) constraints on this element Element id DiagnosticReport.text Short description Text summary of the resource, for human interpretation Alternate names narrative, html, xhtml, display Definition A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Comments Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later. Data type Narrative Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A rim: Act.text?
contained		0..*	Resource	There are no (further) constraints on this element Element id DiagnosticReport.contained Short description Contained, inline Resources Alternate names inline resources, anonymous resources, contained resources Definition These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. Comments This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels. Data type Resource Mappings rim: Entity. Role, or Act rim: N/A
extension	I	0..*	Extension	There are no (further) constraints on this element Element id DiagnosticReport.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
modifierExtension	?! I	0..*	Extension	There are no (further) constraints on this element Element id DiagnosticReport.modifierExtension Short description Extensions that cannot be ignored Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Requirements Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
identifier	Σ	0..*	Identifier	There are no (further) constraints on this element Element id DiagnosticReport.identifier Short description Business identifier for report Alternate names ReportID, Filler ID, Placer ID Definition Identifiers assigned to this report by the performer or other systems. Requirements Need to know what identifier to use when making queries about this report from the source laboratory, and for linking to the report outside FHIR context. Comments Usually assigned by the Information System of the diagnostic service provider (filler id). Data type Identifier Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CX / EI (occasionally, more often EI maps to a resource id or a URL) rim: II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT] servd: Identifier workflow: Event.identifier w5: FiveWs.identifier v2: OBR-51/ for globally unique filler ID - OBR-3 , For non-globally unique filler-id the flller/placer number must be combined with the universal service Id - OBR-2(if present)+OBR-3+OBR-4 rim: id
basedOn	I	0..*	Reference(CarePlan \| ImmunizationRecommendation \| MedicationRequest \| NutritionOrder \| ServiceRequest)	There are no (further) constraints on this element Element id DiagnosticReport.basedOn Short description What was requested Alternate names Request Definition Details concerning a service requested. Requirements This allows tracing of authorization for the report and tracking whether proposals/recommendations were acted upon. Comments Note: Usually there is one test request for each result, however in some circumstances multiple test requests may be represented using a single test result resource. Note that there are also cases where one request leads to multiple reports. Data type Reference(CarePlan \| ImmunizationRecommendation \| MedicationRequest \| NutritionOrder \| ServiceRequest) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) workflow: Event.basedOn v2: ORC? OBR-2/3? rim: outboundRelationship[typeCode=FLFS].target
status	Σ ?!	1..1	codeBindingFixed Value	Element id DiagnosticReport.status Short description registered \| partial \| preliminary \| final + Definition The status of the diagnostic report. Requirements Diagnostic services routinely issue provisional/incomplete reports, and sometimes withdraw previously released reports. Comments Only diagnostic results with a status of "final" may be included in a patient summary. Feedback is requested on whether this is too restrictive, and, e.g. "registered", "partial" or "preliminary" should also be allowed. Data type code Binding The status of the diagnostic report. DiagnosticReportStatus (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Fixed value final Mappings rim: n/a workflow: Event.status w5: FiveWs.status v2: OBR-25 (not 1:1 mapping) rim: statusCode Note: final and amended are distinguished by whether observation is the subject of a ControlAct event of type "revise"
category	S Σ	1..1	package/structuredefinition-profile-codeableconcept-ca-ps.json	Element id DiagnosticReport.category Short description Concept - reference to a terminology or just text Alternate names Department, Sub-department, Service, Discipline Definition A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text. Comments The IPS-UV specification considers this a Must Support element with minimum cardinality of 1. Further feedback is required on whether these systems are still expected to be able to demonstrate they can construct this element when developing the patient summary instance Data type package/structuredefinition-profile-codeableconcept-ca-ps.json Binding Codes for diagnostic service sections. DiagnosticServiceSectionCodes (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD w5: FiveWs.class v2: OBR-24 rim: inboundRelationship[typeCode=COMP].source[classCode=LIST, moodCode=EVN, code < LabService].code
code	S Σ	1..1	package/structuredefinition-profile-codeableconcept-ca-ps.json	Element id DiagnosticReport.code Short description Concept - reference to a terminology or just text Alternate names Type Definition A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text. Comments For all CodeableConcepts, at least one of coding or text must be present. If coding contains only a display value (no code) then CodeableConcept must include text. Data type package/structuredefinition-profile-codeableconcept-ca-ps.json Binding Work is underway to define the pan-Canadian terminology that will be preferred and/or socialized for this element. A stub value set pointing to pCLOCD code system is put forth in the meantime to encourage implementers to utilize the Canadian localization of LOINC package/valueset-pclocd.json (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD workflow: Event.code w5: FiveWs.what[x] v2: OBR-4 (HL7 v2 doesn't provide an easy way to indicate both the ordered test and the performed panel) rim: code
subject	S Σ I	1..1	Reference(package/structuredefinition-profile-patient-ca-ps.json \| Group)	Element id DiagnosticReport.subject Short description The subject of the report - usually, but not always, the patient Alternate names Patient Definition The subject of the report. Usually, but not always, this is a patient. However, diagnostic services also perform analyses on specimens collected from a variety of other sources. Requirements SHALL know the subject context. Comments References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Data type Reference(package/structuredefinition-profile-patient-ca-ps.json \| Group) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) workflow: Event.subject w5: FiveWs.subject[x] v2: PID-3 (no HL7 v2 mapping for Group or Device) rim: participation[typeCode=SBJ] w5: FiveWs.subject
id		0..1	string	There are no (further) constraints on this element Element id DiagnosticReport.subject.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id DiagnosticReport.subject.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
reference	S Σ I	1..1	string	There are no (further) constraints on this element Element id DiagnosticReport.subject.reference Short description Literal reference, Relative, internal or absolute URL Definition A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Comments Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
type	Σ	0..1	uriBinding	There are no (further) constraints on this element Element id DiagnosticReport.subject.type Short description Type the reference refers to (e.g. "Patient") Definition The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). Comments This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Data type uri Binding Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
identifier	Σ	0..1	Identifier	There are no (further) constraints on this element Element id DiagnosticReport.subject.identifier Short description Logical reference, when literal reference is not known Definition An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. Comments When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation\|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). Data type Identifier Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CX / EI (occasionally, more often EI maps to a resource id or a URL) rim: II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT] servd: Identifier rim: .identifier
display	Σ	0..1	string	There are no (further) constraints on this element Element id DiagnosticReport.subject.display Short description Text alternative for the resource Definition Plain text narrative that identifies the resource in addition to the resource reference. Comments This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
encounter	Σ I	0..1	Reference(Encounter)	There are no (further) constraints on this element Element id DiagnosticReport.encounter Short description Health care event when test ordered Alternate names Context Definition The healthcare event (e.g. a patient and healthcare provider interaction) which this DiagnosticReport is about. Requirements Links the request to the Encounter context. Comments This will typically be the encounter the event occurred within, but some events may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission laboratory tests). Data type Reference(Encounter) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) workflow: Event.encounter w5: FiveWs.context v2: PV1-19 rim: inboundRelationship[typeCode=COMP].source[classCode=ENC, moodCode=EVN]
effective[x]	S Σ	1..1		There are no (further) constraints on this element Element id DiagnosticReport.effective[x] Short description Clinically relevant time/time-period for report Alternate names Observation time, Effective Time, Occurrence Definition 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. Requirements Need to know where in the patient history to file/present this report. Comments If the diagnostic procedure was performed on the patient, this is the time it was performed. If there are specimens, the diagnostically relevant time can be derived from the specimen collection times, but the specimen information is not always available, and the exact relationship between the specimens and the diagnostically relevant time is not always automatic. Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a workflow: Event.occurrence[x] w5: FiveWs.done[x] v2: OBR-7 rim: effectiveTime
id		0..1	string	There are no (further) constraints on this element Element id DiagnosticReport.effective[x].id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	Element id DiagnosticReport.effective[x].extension Short description Additional content defined by implementations Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
data-absent-reason	S I	0..1	Extension(code)	Element id DiagnosticReport.effective[x].extension:data-absent-reason Short description effective[x] absence reason Alternate names extensions, user content Definition Provides a reason why the effectiveTime is missing. Comments Systems that have requirements to always populate .effective[X] do not need to demonstrate this element. Receiving systems are expected not to error if they receive a patient summary with a data absent reason on this element. Data type Extension(code) Extension URL http://hl7.org/fhir/StructureDefinition/data-absent-reason Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A rim: ANY.nullFlavor
effectiveDateTime			dateTime	There are no (further) constraints on this element Data type dateTime
effectivePeriod			Period	There are no (further) constraints on this element Data type Period
issued	Σ	0..1	instant	There are no (further) constraints on this element Element id DiagnosticReport.issued Short description DateTime this version was made Alternate names Date published, Date Issued, Date Verified Definition The date and time that this version of the report was made available to providers, typically after the report was reviewed and verified. Requirements Clinicians need to be able to check the date that the report was released. Comments May be different from the update time of the resource itself, because that is the status of the record (potentially a secondary copy), not the actual release time of the report. Data type instant Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a w5: FiveWs.recorded v2: OBR-22 rim: participation[typeCode=VRF or AUT].time
performer	S Σ I	0..*	Reference(package/structuredefinition-profile-practitioner-lab-ca-ps.json \| package/structuredefinition-profile-practitionerrole-lab-ca-ps.json \| package/structuredefinition-profile-organization-lab-ca-ps.json \| CareTeam)	Element id DiagnosticReport.performer Short description Responsible Diagnostic Service Alternate names Laboratory, Service, Practitioner, Department, Company, Authorized by, Director Definition The diagnostic service that is responsible for issuing the report. Requirements Need to know whom to contact if there are queries about the results. Also may need to track the source of reports for secondary data analysis. Comments The IPS-UV specification considers this a Must Support element. Further feedback is required on whether these systems are still expected to be able to demonstrate they can construct this element when developing the patient summary instance Data type Reference(package/structuredefinition-profile-practitioner-lab-ca-ps.json \| package/structuredefinition-profile-practitionerrole-lab-ca-ps.json \| package/structuredefinition-profile-organization-lab-ca-ps.json \| CareTeam) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) workflow: Event.performer.actor w5: FiveWs.actor v2: PRT-8 (where this PRT-4-Participation = "PO") rim: .participation[typeCode=PRF]
resultsInterpreter	Σ I	0..*	Reference(Practitioner \| PractitionerRole \| Organization \| CareTeam)	There are no (further) constraints on this element Element id DiagnosticReport.resultsInterpreter Short description Primary result interpreter Alternate names Analyzed by, Reported by Definition The practitioner or organization that is responsible for the report's conclusions and interpretations. Requirements Need to know whom to contact if there are queries about the results. Also may need to track the source of reports for secondary data analysis. Comments Might not be the same entity that takes responsibility for the clinical report. Data type Reference(Practitioner \| PractitionerRole \| Organization \| CareTeam) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) workflow: Event.performer.actor w5: FiveWs.actor v2: OBR-32, PRT-8 (where this PRT-4-Participation = "PI") rim: .participation[typeCode=PRF]
specimen	I	0..*	Reference(Specimen)	There are no (further) constraints on this element Element id DiagnosticReport.specimen Short description Specimens this report is based on Definition Details about the specimens on which this diagnostic report is based. Requirements Need to be able to report information about the collected specimens on which the report is based. Comments If the specimen is sufficiently specified with a code in the test result name, then this additional data may be redundant. If there are multiple specimens, these may be represented per observation or group. Data type Reference(Specimen) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) v2: SPM rim: participation[typeCode=SBJ]
result	S I	0..*	Reference(Observation)	Element id DiagnosticReport.result Short description Observation results included in the diagnostic report. Alternate names Data, Atomic Value, Result, Atomic result, Data, Test, Analyte, Battery, Organizer Definition Observation results included in the diagnostic report. Requirements Need to support individual results, or groups of results, where the result grouping is arbitrary, but meaningful. Comments The IPS-UV specification considers this a Must Support element. Further feedback is required on whether these systems are still expected to be able to demonstrate they can construct this element when developing the patient summary instance Data type Reference(Observation) Sliced: Unordered, Open, by $this.resolve()(Profile) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) v2: OBXs rim: outboundRelationship[typeCode=COMP].target
observation-results	S I	0..*	Reference(package/structuredefinition-profile-observation-results-laboratory-ca-ps.json \| package/structuredefinition-profile-observation-results-pathology-ca-ps.json \| package/structuredefinition-profile-observation-results-radiology-ca-ps.json \| package/structuredefinition-profile-observation-results-ca-ps.json)	Element id DiagnosticReport.result:observation-results Short description Observations Alternate names Data, Atomic Value, Result, Atomic result, Data, Test, Analyte, Battery, Organizer Definition Observations that are part of this diagnostic report. Requirements Need to support individual results, or groups of results, where the result grouping is arbitrary, but meaningful. Comments Observations can contain observations. Data type Reference(package/structuredefinition-profile-observation-results-laboratory-ca-ps.json \| package/structuredefinition-profile-observation-results-pathology-ca-ps.json \| package/structuredefinition-profile-observation-results-radiology-ca-ps.json \| package/structuredefinition-profile-observation-results-ca-ps.json) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) v2: OBXs rim: outboundRelationship[typeCode=COMP].target
imagingStudy	I	0..*	Reference(ImagingStudy)	There are no (further) constraints on this element Element id DiagnosticReport.imagingStudy Short description Reference to full details of imaging associated with the diagnostic report Definition One or more links to full details of any imaging performed during the diagnostic investigation. Typically, this is imaging performed by DICOM enabled modalities, but this is not required. A fully enabled PACS viewer can use this information to provide views of the source images. Comments ImagingStudy and the image element are somewhat overlapping - typically, the list of image references in the image element will also be found in one of the imaging study resources. However, each caters to different types of displays for different types of purposes. Neither, either, or both may be provided. Data type Reference(ImagingStudy) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) rim: outboundRelationship[typeCode=COMP].target[classsCode=DGIMG, moodCode=EVN]
media	Σ	0..*	BackboneElement	There are no (further) constraints on this element Element id DiagnosticReport.media Short description Key images associated with this report Alternate names DICOM, Slides, Scans Definition A list of key images associated with this report. The images are generally created during the diagnostic process, and may be directly of the patient, or of treated specimens (i.e. slides of interest). Requirements Many diagnostic services include images in the report as part of their service. Data type BackboneElement Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: OBX? rim: outboundRelationship[typeCode=COMP].target
id		0..1	string	There are no (further) constraints on this element Element id DiagnosticReport.media.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id DiagnosticReport.media.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
modifierExtension	Σ ?! I	0..*	Extension	There are no (further) constraints on this element Element id DiagnosticReport.media.modifierExtension Short description Extensions that cannot be ignored even if unrecognized Alternate names extensions, user content, modifiers Definition May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Requirements Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
comment		0..1	string	There are no (further) constraints on this element Element id DiagnosticReport.media.comment Short description Comment about the image (e.g. explanation) Definition A comment about the image. Typically, this is used to provide an explanation for why the image is included, or to draw the viewer's attention to important features. Requirements The provider of the report should make a comment about each image included in the report. Comments The comment should be displayed with the image. It would be common for the report to include additional discussion of the image contents in other sections such as the conclusion. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: .inboundRelationship[typeCode=COMP].source[classCode=OBS, moodCode=EVN, code="annotation"].value
link	Σ I	1..1	Reference(Media)	There are no (further) constraints on this element Element id DiagnosticReport.media.link Short description Reference to the image source Definition Reference to the image source. Comments References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Data type Reference(Media) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) rim: .value.reference
conclusion		0..1	string	There are no (further) constraints on this element Element id DiagnosticReport.conclusion Short description Clinical conclusion (interpretation) of test results Alternate names Report Definition Concise and clinically contextualized summary conclusion (interpretation/impression) of the diagnostic report. Requirements Need to be able to provide a conclusion that is not lost among the basic result data. Comments Note that FHIR strings SHALL NOT exceed 1MB in size Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: OBX rim: inboundRelationship[typeCode="SPRT"].source[classCode=OBS, moodCode=EVN, code=LOINC:48767-8].value (type=ST)
conclusionCode		0..*	CodeableConcept	There are no (further) constraints on this element Element id DiagnosticReport.conclusionCode Short description Codes for the clinical conclusion of test results Definition One or more codes that represent the summary conclusion (interpretation/impression) of the diagnostic report. Comments Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Data type CodeableConcept Binding Diagnosis codes provided as adjuncts to the report. SNOMEDCTClinicalFindings (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD v2: OBX rim: inboundRelationship[typeCode=SPRT].source[classCode=OBS, moodCode=EVN, code=LOINC:54531-9].value (type=CD)
presentedForm	I	0..*	Attachment	There are no (further) constraints on this element Element id DiagnosticReport.presentedForm Short description Entire report as issued Definition Rich text representation of the entire result as issued by the diagnostic service. Multiple formats are allowed but they SHALL be semantically equivalent. Requirements Gives laboratory the ability to provide its own fully formatted report for clinical fidelity. Comments "application/pdf" is recommended as the most reliable and interoperable in this context. Data type Attachment Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` att-1: If the Attachment has data, it SHALL have a contentType `data.empty() or contentType.exists()` Mappings rim: n/a v2: ED/RP rim: ED v2: OBX rim: text (type=ED)

Extensions

There are no additional extensions added to this profile

Key Differences between the IPS-UV and PS-CA

Must Support Differences:

There are no Must support differences between this profile and IPS-UV

Cardinality Differences:

There are no cardinality differences between this profile and IPS-UV

Vocabulary Differences:

There are no vocabulary differences between this profile and IPS-UV

Other differences between the IPS and PS-CA Include:

Data type profiles (e.g., CodeableConcept) and reference targets (e.g., Patient) replaced with PS-CA equivalents when appropriate