Sequoia Project Healthcare Directory Implementation Guide
1.0.10 - Release 1
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.
Sequoia Project Healthcare Directory |
Sequoia Project FHIR Provider Directory |
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.
Sequoia Endpoint |
This profile on the FHIR Endpoint resource represents information about the endpoints provided by organizations participating in Sequoia project sponsored exchanges. The endpoints described can use any Sequoia supported protocol, such as IHE XCA, and need not be FHIR endpoints. |
Sequoia 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 the implementation guides that are based on it. It is not intended to be used directly, rather end users should create instances conforming to the non-abstract profiles defined in other IGs such as Carequality, eHealthExchange, and RCE. |
These define constraints on FHIR resources for systems conforming to this implementation guide.
Sequoia Location |
This profile on the FHIR Location resource is used to store geolocation data about an address, as well as the OrgRole extension. If not set by the QHIN when publishing an Organization address to the Directory, SequoiaLocation is created by the Directory with geolocation Position details determined from the provided physical address. |
These define constraints on FHIR data types for systems conforming to this implementation guide.
Administrative Status |
This extension is currently only used by eHealthExchange. This should be ignored in other directories. |
Company |
The company or organization affiliated with the contact. The contact’s company/organization may differ from the Organization.name as the company may be working as a technology partner or consultant in support of the entity defined by the Organization.name. This extension is only necessary when the contact person is employed by an organization different from the one specified in the Organization resource itself. |
Delegation of Authority |
This extension allows references to other Organization resources in the directory from which this Organization receives its Delegation of Authority |
Domains |
This extension is used on the Organization resource and indicates which Sequoia directory (or directories) the Organization participantes in. The current legal values are CQ, eHx, and RCE. Most Organizations would only have a single value in this extension. |
Downtime |
This extension is used on the Endpoint resource and indicates expected future down-time of the endpoint for maintenance, etc. |
FHIR IG Conformance |
When the Transaction extension is set to FHIR REST, this extension specifies which implementation guides and CapabilityStatement resources this Endpoint conforms to. If an Endpoint conforms to multiple versions of a single IG (i.e. multiple versions of US Core) then multiple instances of this extension should be specified. |
Hub Routing Status |
This extension is currently only used by eHealthExchange. This should be ignored in other directories. |
Hub Service Subscription |
This extension is currently only used by eHealthExchange. This should be ignored in other directories. |
Initiator Only |
When an Organization participates in a Use Case that includes a requirement to respond to requests from others, this extension may be used on that Organization resource to indicate that they meet an Initiator Only exception and do not have Endpoints for that Use Case, if allowed by the Use Case's Initiator Only policies. |
Org Location |
This extension is used on the Organization resource to indicate the geolocation and organization role at a given address. |
Org Role |
This extension is used on the Location resource to indicate the organization role at a given address. |
OrgManagingOrg |
This extension is directly tied to the Directory server access API key allowing Organizations to be created, updated, and deleted only by their managing Organization. This is typically the top-level Organization in the hierarchical chain defined by Organization.partOf. |
Purposes Of Use |
This extension is used on both the Endpoint and Organization resources. For an Endpoint, this extension defines the Purpose(s) of Use for which the Endpoint will receive and respond to requests from others. An Organization may have multiple Endpoints for the same Transaction type that receive and process different Purposes of Use. For an Organization, this extension defines the Purpose(s) of Use for which the Organization will initiate requests to others. |
Roles |
This extension is used on the Endpoint resource and provides SNOMED CT codes to indicate the clinical role(s) of document authors for documents available from that Endpoint. |
StateOfOperation |
This extension is used on the Organization resource. It is repeatable, and each instances contains a state or province in which the organization operates. |
Transaction |
This extension is used on the Endpoint resource and indicates the profile/standard supported for transactions sent to the Endpoint address (e.g., XCA ITI-38) |
UseCases |
When an implementation of the Sequoia Directory IG has unique requirements tied to specific Use Case participation, this extension is used on the Organization resource to indicate which Use Case(s) the Organization participates in. |
Version |
When an implementation of the Sequoia Directory IG allows multiple published versions of a single transaction profile/standard, this extension indicates the specific Version supported for transactions sent to the Endpoint address. If the transaction is "FHIR REST" then this should represent the FHIR version supported by the Endpoint. |
These define sets of codes used by systems conforming to this implementation guide.
Administrative Status |
Codes used by the AdministrativeStatus extension. |
Domains |
Codes used by the Domains extension. |
Endpoint Connection Type |
Codes used in Endpoint.connectionType |
Endpoint Identifier Codes |
Codes used in Identifier.type |
Endpoint Payload Type Codes |
Codes used in Endpoint.payloadType |
Endpoint Use Case Codes |
Codes used by the UseCases extension |
Hub Routing Status |
Codes used by the HubRoutingStatus extension |
Hub Service Subscriptions |
Codes used by the HubServiceSubscriptions extension |
Initiator Only |
Codes used by the InitiatorOnly extension |
NHIN User Role |
The value set is defined by the NHIN Specifications Factory to the restricted set of SNOMED CT codes listed in Table 2-155 Author Role Value Set Definition |
Organization Type |
Codes used in Organization.type |
Purpose Of Use |
Codes used by the PurposesOfUse extension |
RCE Purpose ValueSet |
Codes used for the RCE implementation of the PurposesOfUse extension. Each code is used as defined in the Common Agreement, QHIN Technical Framework, Exchange Purposes SOP, and any other applicable Exchange Purpose Implementation SOP. |
Sequoia Service Delivery Location Role Type Value Set |
Adds additional codes required by Sequoia directories that are not present in the HL7 Service Delivery Location Role Type value set. |
Transactions |
Codes used by the Transactions extension |
These define new code systems used by systems conforming to this implementation guide.
Administrative Status |
Codes used by the AdministrativeStatus extension |
Domains |
Codes used by the Domains extension |
Endpoint Connection Type |
Codes used in Endpoint.connectionType |
Endpoint Role Codes |
Codes used by the Roles extension |
Endpoint Use Case Codes |
Codes used by the UseCases extension |
Hub Routing Status |
Codes used by the HubRoutingStatus extension |
HubServiceSubscriptionCodes |
Codes used by the HubServiceSubscriptions extension |
Initator Only Codes |
Codes used by the InitiatorOnly extension |
Organization Type |
Codes used in Organization.type |
Purpose Of Use |
Codes used by the PurposesOfUse extension |
RCE Purpose |
Codes used for the RCE implementation of the PurposesOfUse extension. Each code is used as defined in the Common Agreement, QHIN Technical Framework, Exchange Purposes SOP, and any other applicable Exchange Purpose Implementation SOP. |
Sequoia Service Delivery Location Role Type Coding System |
Adds additional codes required by Sequoia directories that are not present in the HL7 Service Delivery Location Role Type code system. |
SequoiaIdentifierCodes |
Codes used in Identifier.type |
Transaction Codes |
Codes used by the Transaction extension |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
Create Error Example |
Create Error Example |
Create Success Example |
Create Success Example |
Create Success Example 2 |
Create Success Example 2 |
Delete Error Example |
Delete Error Example |
Delete Success Example |
Delete Success Example |
Delete Success Example 2 |
Delete Success Example 2 |
Delete Success Example 3 |
Delete Success Example 3 |
Delete Success Example 4 |
Delete Success Example 4 |
Eric Hospital |
Example SequoiaOrganization |
FHIR Endpoint Example |
FHIR Endpoint Example |
Kyras Clinic |
Kyras Clinic Example |
Payer Organization Example |
Payer Organization Example |
Read Error Example |
Read Error Example |
Read Success Example |
Read Success Example |
Read Success Example |
Read Success Example |
Read Success Example |
Read Success Example |
Read Success Example 4 |
Read Success Example 4 |
Update Success Example |
Update Success Example |
Update Success Example 3 |
Update Success Example 3 |
Update Success Example 5 |
Update Success Example 5 |
Validate Error Example |
Validate Error Example |
Validate Success Example |
Validate Success Example |