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

Example Organization: Sub Y

Domains: Domains RCE: RCE

UseCases: Query Based Document Exchange

OrgManagingOrg: Organization QHIN A

Transaction: XCA ITI-38

Transaction: XCA ITI-39

identifier: Home Community ID/urn:oid:Q.A.P.1.2, TEFCA ID/urn:oid:5.5.5.5, urn:oid:2.16.840.1.113883.4.336/some-CCN-identifier-code

active: false

type: Subparticipant

name: Sub Y

address: 200 Main St., Austin TX 2472(work)

partOf: Participant 1

contact

purpose: Administrative

name: Family, Given(Official)

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

address: 100 Main St, Austin TX 78737(work)

endpoint:


Generated Narrative: Location #orgloc

Positions

-LongitudeLatitude
*-97.704738630.4159542

Generated Narrative: Endpoint #Endpoint-Sub-Y-1

Profile: RCE Endpoint

Transaction: XCA ITI-38

EndpointType: Endpoint Type responding-node: Responding Node

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

status: Active

connectionType: Endpoint Connection Type ihe-xca: IHE XCA

name: Endpoint-Sub-Y-1

managingOrganization: Organization Sub Y

payloadType: NoInformation

payloadMimeType: application/xml

address: Absent because : not-applicable


Generated Narrative: Endpoint #Endpoint-Sub-Y-2

Profile: RCE Endpoint

Transaction: XCA ITI-39

EndpointType: Endpoint Type responding-node: Responding Node

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

status: Active

connectionType: Endpoint Connection Type ihe-xca: IHE XCA

name: Endpoint-Sub-Y-2

managingOrganization: Organization Sub Y

payloadType: NoInformation

payloadMimeType: application/xml

address: Absent because : not-applicable