Sequoia Project Healthcare Directory Implementation Guide
1.0.3 - Release 1 United States of America flag

ValueSet: Hub Routing Status

Official URL: https://sequoiaproject.org/fhir/sphd/ValueSet/HubRoutingStatus Version: 1.0.3
Active as of 2023-12-13 Computable Name: HubRoutingStatus

Codes used by the HubRoutingStatus extension

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

Expansion based on codesystem Hub Routing Status v1.0.3 (CodeSystem)

This value set contains 5 concepts

CodeSystemDisplayDefinition
  ResponderOnlyhttps://sequoiaproject.org/fhir/sphd/CodeSystem/HubRoutingStatusResponderOnly

This organization can respond to requests routed through the eHx Hub. This organization cannot yet initiate requests through the Hub

  InitiatorOnlyhttps://sequoiaproject.org/fhir/sphd/CodeSystem/HubRoutingStatusInitatorOnly

This 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

  InitiatorAndResponderhttps://sequoiaproject.org/fhir/sphd/CodeSystem/HubRoutingStatusInitiatorAndResponder

This organization can respond to requests received from the Hub and also initiate requests to the Hub

  HubTestinghttps://sequoiaproject.org/fhir/sphd/CodeSystem/HubRoutingStatusHubTesting

This 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”

  LegacyRoutinghttps://sequoiaproject.org/fhir/sphd/CodeSystem/HubRoutingStatusLegacyRouting

this 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