Foreign Exam Management use cases cover three main areas requiring standardization:
- Document and Image Sharing
- Imaging Report Format
- Anatomic Region Code
Listed below are the available standards considered for each standardization category, the chosen alternative being highlighted.
Document and Image Sharing
Foreign Exam Management will be implemented by an organization participating a jurisdictions’ shared Diagnostic Imaging Repository (DI-R) system. The DI-R will provide for registration and long term storage of sets of images and reports and standards based services that will be leveraged and, possibly, upgraded to support the FEM use case(s).
Standard | Fit for Pupose | Stewardship | Quality | |||||
Fits | Implementation | Vendor Support | Canadian | SDO | Complexity | Standard | Training, Support and Tooling | |
IHE Cross-Enterprise Document Sharing - Imaging (XDS/XDS-I) | Yes | Production | Medium | Yes | Yes | High | High | Yes |
DICOM / HL7 | Yes | Production | High | No | Yes | Medium | High | Unknown |
Architectural Constraints and Considerations | Secondary Benefits | |||||||
None of these standards impose significant architectural constraints |
| |||||||
Recommendation | Supporting Rationale | |||||||
IHE Cross-Enterprise Document Sharing - Imaging (XDS/XDS-I) | The IHE XDS-I.b profile specifies the use of existing standards including HL7 and DICOM to enable registration and sharing of images and reports. A Canadian XDS Affinity domain guide is available to support implementation of the profile. |
Report Format
XDS/XDS-I supports a range of report formats through the use of different transaction and reporting
Standard | Maturity | Sustainability | Implementation | ||||
Standards Process | Implementation | Canadian Implementation | Superseded? | Vendor Support? | Complexity | Training, Support and Tooling Availability | |
Clinical Document Architecture (CDA) R2 | Final | Production | Production | No | High | High | Good |
Portable Document Format (PDF) | Final | Production | Production | No | High | Medium | Good |
DICOM SR / SC | Final | Production | Unknown | No | High | ? | Good |
Raw Text | Final | Production | Unknown | No | High | Low | Good |
Architectural Constraints and Considerations | Secondary Benefits | ||||||
None of these standards impose significant architectural constraints | PDF may preclude secondary use, while the structured data of a CDA document supports machine readability and may enable secondary use of clinical data, clinical decision support or application of administrative/demographic data to analytics/business intelligence | ||||||
Recommendation | Supporting Rationale | ||||||
Clinical Document Architecture (CDA) R2 | It is the goal of the Canadian XDS Affinity domain that reports will be stored in HL7 CDA format (using the pan-Canadian header format) as these reports (a) support required metadata, and (b) can be transformed to all other formats. |
Anatomic Region Code
Metadata plays an important role in the identification of relevant priors during the fetch and pre-fetch use cases. The significant coded metadata elements for the FEM use case are the acquisition modality of image and the anatomical region being studied. Acquisition modality was adopted as prescribed. This section identifies options considered to identify the Anatomic Region.
Standard | Maturity | Sustainability | Implementation | ||||
Standards Process | Implementation | Canadian Implementation | Superseded? | Vendor Support? | Complexity | Training, Support and Tooling Availability | |
Coarse Body Parts (SNOMED CT subset) | Final | Production | Production | No | High | High | Good |
Anatomic Region (DICOM CID 4) | Final | Production | Production | No | High | Medium | Good |
Architectural Constraints and Considerations | Secondary Benefits | ||||||
None of these standards impose significant architectural constraints | Use of SNOMED CT to encode the Canadian code set may help enable mapping from the DI Procedure Codes to the Coarse Body parts and/or definition of automated validation. | ||||||
Recommendation | Supporting Rationale | ||||||
Clinical Document Architecture (CDA) R2 | The DICOM CID 4 value set is very detailed and generally inconsistent with the general approach of “casting a wide net” employed when fetching content within the FEM use cases. |