Recognized Coordinating Entity (RCE) Implementation Guide
1.0.3 - Release 1
Recognized Coordinating Entity (RCE) Implementation Guide
1.0.3 - Release 1
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
These are profiles on resources or data types that describe patterns used by other profiles, but cannot be instantiated directly. I.e. instances can conform to profiles based on these abstract profiles, but do not declare conformance to the abstract profiles themselves.
| RCE Organization |
This profile on the FHIR Organization resource is an abstract base profile that defines shared constraints for all other profiles on the Organization resource in this implementation guide. It is not intended to be used directly, rather end users should create instances conforming to the QHIN, Participant, Subparticipant, or Child profiles. |
These define constraints on FHIR resources for systems conforming to this implementation guide.
| Child |
The Child profile represents the individual components (such as member organizations, facilities, locations, etc.) that make up a QHIN, Participant, or Subparticipant. A Child can be the parent of other Child organizations. |
| Participant |
The Participant profile represents a Participant as defined in the Common Agreement. A Participant can be the parent of Subparticipant and Child organizations. |
| QHIN |
The QHIN profile represents a Qualified Health Information Network as defined in the Common Agreement. A QHIN can be the parent of Participant, Subparticipant, and Child organizations. There will be exactly one QHIN Organization resource per Designated QHIN. |
| RCE Endpoint |
This profile on the FHIR Endpoint resource represents information about the endpoints provided by Organizations participating in TEFCA exchange. The endpoints described can use any QTF-supported protocol, such as IHE XCA, and need not be FHIR endpoints. |
| Subparticipant |
The Subparticipant profile represents a Subparticipant as defined in the Common Agreement. A Subparticipant can be the parent of Subparticipant and Child organizations. |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
| Example RCE Endpoint |
Example RCE Endpoint instance. Note that the RCE Directory currently expects Endpoint instances to be contained resources within an Organization resource. |
| RCE Child Example |
Example RCE Child Organization instance. This example shows a 3rd-level organization below the RCE Subparticipant example. |
| RCE Participant Example |
Example RCE Participant Organization instance. This example shows a top level organization participating in a QHIN, which is the direct parent of the RCE Subparticipant example. In includes a contained FHIR Endpoint. |
| RCE QHIN Example |
Example RCE QHIN Organization instance. This example shows a TEFCA Qualified Health Information Network (QHIN) organization in the RCE directory. It is the top-level parent of the other examples in this IG, and the direct parent of the RCE Participant example. |
| RCE Subparticipant Example |
Example RCE Participant Organization instance. This example shows a 2nd level organization below an RCE Participant organization. This example is the direct parent of the RCE Child example. It includes a contained XCDR Endpoint. |