IHE PaLM - Radiology Pathology Concordance (RPC)
0.1.0 - ci-build

IHE PaLM - Radiology Pathology Concordance (RPC), published by IHE IT Infrastructure Technical Committee. This is not an authorized publication; it is the continuous build for version 0.1.0). This version is based on the current content of https://github.com/IHE/PaLM.RPC/ and changes regularly. See the Directory of published versions

## 1:XX. RPC Home

Official URL: http://profiles.ihe.net/PaLM/RPC/ImplementationGuide/ihe.palm.rpc | Version: 0.1.0
Active as of 2023-06-06 | Computable Name: IHE_PaLM_RPC
Copyright/Legal: IHE http://www.ihe.net/Governance/#Intellectual_Property

The Radiology Pathology Concordance (RPC) Profile describes how discrete data elements are collected from structured reports to create an integrated report, where concordance of results is assessed, and reports are shared to an EMR or system in use by a health facility.

The integrated report would extract data from structured radiology and pathology reports, compare the extracted results and assign a score based on the concordance of the results which will be included in a new integrated report.

Use cases include the correlation of structured reporting data for Breast, Prostate and Thyroid175 cancers, as well as the use of integrated diagnostic reports for radiologist training, as well as a tool in MCC’s and Tumor Board discussions to support decision making for patient care.

Open and Closed Issues

### Organization of This Guide

This guide is organized into four main sections:

1. Volume I: Overview
   1. Actors and Transactions
   2. Actor Options
   3. Actor Required Groupings
   4. Overview
   5. Security Considerations
   6. ​Cross Profile Considerations
2. Volume II: Transaction Detail
   1. Send Concordance Report [LAB-90]
   2. Retrieve Concordance Report Definition [LAB-91]
3. Volume III: Metadata
   1. TODO: point to your content profiles if you have them
4. National Extensions
   1. TODO: point at your national extensions if you have them
5. Appendix
   1. Test Plan
   2. TODO: point to your appendix if you have them

Click on any of the links above, head on over the table of contents, or if you are looking for a specific artifact, check out the index.

You can also download:

- this entire guide,
- ​the definition resources in json, xml, ttl, or csv format, or
- the example resources in json, xml or ttl format.

The source code for this Implementation Guide can be found on TODO: Put your github repo here