Recognized Coordinating Entity (RCE) Implementation Guide
1.14.0 - Release 1

Example Organization: General RCE Subparticipant Example

Domains: Domains: RCE (RCE)

Initiator Only: Initiator Only Codes: EMS (EMS Provider (Initiator Only))

OrgManagingOrg: Organization RCE Participant Example

Purposes Of Use: Treatment

StateOfOperation: NY USA

UseCases: Query Based Document Exchange

Delegation of Authority: Organization RCE QHIN Example

Transaction: XCA ITI-38

Delegation Role: Delegation Role Codes: delegate (Delegate)

Organization Node Type: Organization Node Type CodeSystem: passthrough-node (Passthrough Node)

identifier: Home Community ID/urn:oid:5.4.3.2.1, TEFCA ID/urn:oid:5.5.5.5, United States National Provider Identifier/1234567893 (use: official, ), CMS Certification Numbers/some-CCN-identifier-code

active: false

type: Subparticipant

name: RCE Subparticipant Example

address: Primary(work)

partOf: RCE Participant Example

contact

purpose: Administrative

name: Family, Given(Official)

telecom: ph: 555-555-5555(Work), test21@test.com

address: Primary(work)

endpoint: Endpoint Example RCE Endpoint


Generated Narrative: Location #orgloc

Positions

-LongitudeLatitude
*-97.704738630.4159542

Generated Narrative: Endpoint #RCE-orgEndpoint

Transaction: FHIR REST

Version: 4.0.1

identifier: Home Community ID/urn:oid:5.5.5.5 (use: official, )

status: Active

connectionType: Endpoint Connection Type: ihe-xcpd (IHE XCPD)

name: Example RCE Endpoint

managingOrganization: Organization RCE QHIN Example

payloadType: NoInformation

payloadMimeType: application/xml

address: https://example.org/xcpd/v1/xcpd