CapabilityStatement for Data Source Actor in the IHE IT Infrastructure Technical Framework Supplement IHE mCSD.

CapabilityStatement for Directory Actor in the IHE IT Infrastructure Technical Framework Supplement IHE mCSD.

CapabilityStatement for Directory Actor with the Feed Option in the IHE IT Infrastructure Technical Framework Supplement IHE mCSD.

CapabilityStatement for Directory Actor with the Location Distance option in the IHE IT Infrastructure Technical Framework Supplement IHE mCSD.

CapabilityStatement for Directory Actor with the Update Option in the IHE IT Infrastructure Technical Framework Supplement IHE mCSD.

CapabilityStatement for Query Client Actor in the IHE IT Infrastructure Technical Framework Supplement IHE mCSD.

CapabilityStatement for Query Client Actor with the Location Distance Option in the IHE IT Infrastructure Technical Framework Supplement IHE mCSD.

CapabilityStatement for Update Client Actor in the IHE IT Infrastructure Technical Framework Supplement IHE mCSD.

This SearchParameter enables finding Endpoints by the specificType code. This resource is created as informative content.

This SearchParameter enables finding Endpoints or Organizatoins by the purpose of use code. This resource is created as informative content.

Defines constraints on the AuditEvent Resource to record when a Care Services Feed Transaction happens to do batch/transaction updates to Care Services resources, as recorded by the Directory or Data Source.

Defines constraints on the AuditEvent Resource to record when a Care Services Feed Transaction happens to create a Care Services resource, as recorded by the Directory or Data Source.

Defines constraints on the AuditEvent Resource to record when a Care Services Feed Transaction happens to delete a Care Services resource, as recorded by the Directory or Data Source.

Defines constraints on the AuditEvent Resource to record when a Care Services Feed Transaction happens to update a Care Services resource, as recorded by the Directory or Data Source.

Defines constraints on the AuditEvent Resource to record when a Find Matching Care Services Transaction happens to query a Care Services Resource, as recorded by the Directory or Query Client.

Defines constraints on the AuditEvent Resource to record when a Find Matching Care Services Transaction happens to read a Care Services resource, as recorded by the Query Client or Directory.

Defines constraints on the AuditEvent Resource to record when a Request Care Services Updates Transaction happens for a Care Services Resource updates, as recorded by the Directory or Update Client.

A profile on the mCSD Endpoint.

An Organization may be reachable through electronic Endpoint(s). An Endpoint may be a FHIR server, an IHE web services actor, or some other mechanism. If an Organization does not have an Endpoint, it may still be reachable via an Endpoint at its parent Organization or an affiliated Organization.

Given that in FHIR R4 the .connnectionType is 1..1, each type of endpoint will be indicated with an independent Endpoint resource.

A profile on the mCSD Endpoint for Document Sharing environments.

Given that in FHIR R4 the .connnectionType is 1..1, each type of endpoint will be indicated with an independent Endpoint resource. Thus a XCA Responding Gateway will need two Endpoint instances to express Query vs Retrieve.

Open-Issues:

1. That payloadType and payloadMimeType are either empty to indicate that the endpoint is not constrained; or fully populated.
2. That payloadType and PayloadMimeType for XCA/XDS/MHD Query and XCA/XDS/MHD Retrieve would be the same thus replicating the capability at both endpoints.
3. It did not seem right that Query be indicated with a mimeType of ebRegistry as that is not helpful to the use-case.
4. should the homeCommunityId be mandated here, should those behind it be here, should this be empty?
5. would a Proxy service that is supporting OrgAff be a good example of NOT putting a homeCommunityId in the endpoint.identifier?

A profile on the HealthcareService resource for mCSD.

Each healthcare service has a unique identifier. Examples include surgical services, antenatal care services, or primary care services. The combination of a Healthcare Service offered at a Location may have specific attributes including contact person, hours of operation, etc.

A profile on the Location resource for mCSD.

Locations are physical places where care can be delivered such as facilities, buildings, wards, rooms, or vehicles. Locations also include jurisdictions such as a village districts or regions. A Location has a unique identifier and may have geographic attributes (address, geocode), attributes regarding its hours of operation, etc. Each Location may be related to one Organization. A location may have a hierarchical relationship with other locations.

A profile on mCSD Location for mCSD Facilities.

Facilities are physical care delivery sites such as hospitals, clinics, health outposts, physician offices, labs, pharmacies, etc. A Facility has a unique identifier, geographic attributes (address, geocode), contact attributes, attributes regarding its hours of operation, etc. Each Facility is defined by a pairing of Location and Organization.

In addition to the base requirements of mCSD Location, one type must be set to https://profiles.ihe.net/ITI/mCSD/CodeSystem/IHE.mCSD.Organization.Location.Types#facility.

A profile on the mCSD Location for mCSD Jurisdictions.

Jurisdictions are political administrative units or other territories over which authority is exercised. A Jurisdiction has a unique identifier, geographic attributes, etc. Jurisdictions include political administrative units such as village districts or regions. Each Jurisdiction is defined by a pairing of Location and Organization.

In addition to the base requirements of mCSD Location, one type must be set to https://profiles.ihe.net/ITI/mCSD/CodeSystem/IHE.mCSD.Organization.Location.Types#jurisdiction.

A profile on the mCSD Location resource for distance searches.

This profile is for when you want to allow distance based searches for an mCSD Location resource.

A profile on the Organization resource for mCSD.

Organizations are “umbrella” entities; these may be consideredthe administrative bodies under whose auspices care services are provided such as Healthcare Information Exchanges (HIEs), Integrated Delivery Networks (IDNs), Non-Government Organizations (NGOs), Faith-Based Organizations (FBOs) or even a one-physician family practice. An organization has a unique identifier and may have additional administrative attributes such as contact person, mailing address, etc. Departments of an institution, or other administrative units, may be represented as child Organizations of a parent Organization.

A profile on the OrganizationAffiliation resource for mCSD.

An Organization may have relationships with other organizations that are not hierarchical. These relationships may indicate an electronic routing path to other organizations that cannot be reached directly. OrganizationAffiliation can be used to specify relationships such as supply chains or administrative reporting structures.

A profile on the OrganizationAffiliation resource for mCSD in Document Sharing. Karen’s Cross, when expanded to either/or a service that translates protocols, or a proxy that mediates network communication.

Not used for direct connected mesh networks of depth 2 as that is handled fine with Organization->Endpoint.

Affiliation is used to show Document Sharing network linkage to a set of communities that are not directly addressible.
The participating organization would not have Organization->Endpoint advertised in the network directory. There will be many OrganizationAffiliations, one for each pathway provided on the network by the serving organization (.organization) to another organization (.participatingOrganization).

A profile on mCSD Organization for mCSD Facilities.

Facilities are physical care delivery sites such as hospitals, clinics, health outposts, physician offices, labs, pharmacies, etc. A Facility has a unique identifier, geographic attributes (address, geocode), contact attributes, attributes regarding its hours of operation, etc. Each Facility is defined by a pairing of Location and Organization.

In addition to the base requirements of mCSD Organization, one type must be set to https://profiles.ihe.net/ITI/mCSD/CodeSystem/IHE.mCSD.Organization.Location.Types#facility.

A profile on the mCSD Organization for mCSD Jurisdictions.

Jurisdictions are political administrative units or other territories over which authority is exercised. A Jurisdiction has a unique identifier, geographic attributes, etc. Jurisdictions include political administrative units such as village districts or regions. Each Jurisdiction is defined by a pairing of Location and Organization.

In addition to the base requirements of mCSD Organization, one type must be set to https://profiles.ihe.net/ITI/mCSD/CodeSystem/IHE.mCSD.Organization.Location.Types#jurisdiction.

A profile on the Practitioner resource for mCSD.

A Practitioner is a health worker such as defined by WHO; a Practitioner might be a physician, nurse, pharmacist, community health worker, district health manager, etc. Practitioners have contact and demographic attributes. Each Practitioner may be related to one or more Organizations, one or more Locations and one or more Healthcare Services through a Practitioner Role. Specific attributes may be associated with the Practitioner relationship with these other entities.

A profile on the PractitionerRole resource for mCSD.

A PractitionerRole links a Practitioner with a particular health care role to perform Healthcare Services at a particular Location for an Organization

The specific endpoint type. Given that the FHIR R4 Endpoint.connectionType is limited to a one value from a valueSet given by FHIR core and that valueSet includes XCA thus by Extensible rules one is forced to pick that value, we choose to add an additional codeableConcept for a more detailed code(s).

Set a purpose of use for an mCSD Endpoint or mCSD Organization.

ValueSet of the Core Document Sharing Endpoint types allowed

ValueSet of the Endpoint types allowed

ValueSet of Organization Affiliation types allowed

mCSD Type codes for specific business identifiers for Endpoint resources.

mCSD Type codes for specific business identifiers for Organization resources.

mCSD Types for specialized Organization and Location resources.

mCSD Endpoint types beyond those in the FHIR core.

The codes defined here are endpoint types defined in IHE profiles at the time of publication. Other codes might be defined in new IHE profiles written later, where they could define their own code and own codeSystem.

Code pattern: {Profile}-{Actor}-{Transaction}[-{option}]

• Where Profile is the acronym
• Where Actor name compressed to be short yet clear (camel case)
• Where Transaction name is compressed to be short yet clear (camel case)
• Where the code definition spells out these using the formal names and transaction number
• Where an option is important it can be prepended

Note that this codeSystem contains only endpoints needed for Some IHE profiles, and only for the synchronous communication pattern. When Async is supported additional entries will be needed on these actors, and the peer actor will also need to be described. Async is not in scope at this time.

An example vocabulary of hierarchies.

mCSD OrganizationAffiliation types beyond those in the FHIR core.

mCSD Type codes for specific business identifiers for Endpoint resources.

mCSD Type codes for specific business identifiers for Organization resources.

mCSD Type codes for specialized Organization and Location resources.

Audit example for a Data Source submitting a batch/transaction on Care Services resources for ITI-130.

Audit example for a Data Source submitting a create on a Care Services resource for ITI-130.

Audit example for a Data Source submitting a delete on a Care Services resource for ITI-130.

Audit example for a Data Source submitting an update on a Care Services resource for ITI-130.

Audit example for a Query Client requesting a query on a Care Services Resource for ITI-90.

Audit example for a Query Client requesting a read on a Care Services resource for ITI-90.

Audit example for a Update Client requesting updates on a Care Services Resource for ITI-91.

Device Example for mCSD.

Example Bundle of Core mCSD Resources.

Example Organization A that wants to communicate with Organization B

• Note this Organization has no endpoint, but it is a client in this scenario

Example Organization B that is not on the network directly

• Note that this organization has no endpoint as it is not directly participating in the network

Example Organization C supports communication with Organization B

• Note that this organization hosts an XDS Query endpoint on the network.
• More endponts would be here, but the use-case is simplified to just XDS Query

Example OrganizationAffiliation C that indicates that C will provide communication to B.

• Note that the endpoint is listed here in addition to in ex-OrgC to be more efficient

Example Organization for a Partner Organization

Organization Affiliation resource for an example administrative relationship for a facility.

Location resource for an example mCSD Facility

Organization resource for an example mCSD Facility

HealthcareService resource example for mCSD.

Location resource for an example mCSD Jurisdiction

Organization resource for an example mCSD Jurisdiction

Location resource for an example of an mCSD Location (Ward)

Location resource for an example of an mCSD Location with Distance Option

Practitioner resource example for mCSD.

PractitionerRole resource example for mCSD.

This is an example of a DICOM WADO-RS endpoint.

This is a simple OrganizationAffiliation for an HIE. This is NOT representative of a Document Sharing affiliation.

This is an example of an XCA Retrieve endpoint for OrgA

• supports XPHR and IPS
• supports mime-type for FHIR, CDA, and PDF

This is an example of an XCA Retrieve endpoint

• supports XPHR and IPS
• supports mime-type for FHIR, CDA, and PDF