Sequoia Project Healthcare Directory Implementation Guide
0.0.3 - CI Build US

Sequoia Project Healthcare Directory Implementation Guide - Local Development build (v0.0.3). See the Directory of published versions

ValueSet: Hub Routing Status

Official URL: https://sequoiaproject.org/fhir/sphd/ValueSet/HubRoutingStatus Version: 0.0.3
Active as of 2022-08-18 Computable Name: HubRoutingStatus

Copyright/Legal: This document is copyright 2017-18 by The Sequoia Project. All rights reserved world wide.

References

Logical Definition (CLD)

  • Include these codes as defined in https://sequoiaproject.org/fhir/sphd/CodeSystem/HubRoutingStatus
    CodeDisplayDefinition
    ResponderOnlyResponderOnlyThis organization can respond to requests routed through the eHx Hub. This organization cannot yet initiate requests through the Hub
    InitiatorOnlyInitatorOnlyThis organization can route requests through the eHx Hub, but cannot respond to requests from the eHx Hub. PULSE would be an example, as they are an initiator only and do not maintain a CDR that can be queried externally
    InitiatorAndResponderInitiatorAndResponderThis organization can respond to requests received from the Hub and also initiate requests to the Hub
    HubTestingHubTestingThis organization can respond to requests received from the Hub and also initiate requests to the Hub. This state is supported to allow Participants to perform Hub-specific testing, and should be considered a temporary state. This is independent of the AdministrativeStatus of “Testing”
    LegacyRoutingLegacyRoutingthis organization should exchange directly with Participants and not route thru the Hub

 

Expansion

This value set contains 5 concepts

Expansion based on Hub Routing Status v0.0.3 (CodeSystem)

All codes in this table are from the system https://sequoiaproject.org/fhir/sphd/CodeSystem/HubRoutingStatus

CodeDisplayDefinition
  ResponderOnlyResponderOnlyThis organization can respond to requests routed through the eHx Hub. This organization cannot yet initiate requests through the Hub
  InitiatorOnlyInitatorOnlyThis organization can route requests through the eHx Hub, but cannot respond to requests from the eHx Hub. PULSE would be an example, as they are an initiator only and do not maintain a CDR that can be queried externally
  InitiatorAndResponderInitiatorAndResponderThis organization can respond to requests received from the Hub and also initiate requests to the Hub
  HubTestingHubTestingThis organization can respond to requests received from the Hub and also initiate requests to the Hub. This state is supported to allow Participants to perform Hub-specific testing, and should be considered a temporary state. This is independent of the AdministrativeStatus of “Testing”
  LegacyRoutingLegacyRoutingthis organization should exchange directly with Participants and not route thru the Hub

Explanation of the columns that may appear on this page:

Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance)
Display The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code