Subscriptions — client

The health IT developer demonstrates the Health IT Module supports the following capabilities as a client in accordance with an implementation specification at § 170.215(h):

1. SUN-1: Identification of a server’s supported subscription topics using the server’s “R4 Topic-Based Subscription Server Capability Statement.”
2. SUN-2: Creation, updating, and deletion of a subscription with a server. This subscription must use the “REST-hook” channel and be formatted according to the “R4/B Topic-Based Subscription” resource profile.
3. SUN-3: Query the status of a subscription with a server using the “$status” operation.
4. SUN-4: Read (i.e., retrieve) a subscription from a server using the “id” of a “Subscription” resource.
5. SUN-5: The Health IT Module’s “REST-hook” endpoint supports server subscription negotiation and processing including support for “handshake,” “heartbeat,” and “event-notification” transactions.

The tester verifies the Health IT Module supports the following capabilities as a client in accordance with an implementation specification at § 170.215(h):

1. SUN-1: Identification of a server’s supported subscription topics using the server’s “R4 Topic-Based Subscription Server Capability Statement.”
2. SUN-2: Creation, updating, and deletion of a subscription with a server. This subscription must use the “REST-hook” channel and be formatted according to the “R4/B Topic-Based Subscription” resource profile.
3. SUN-3: Query the status of a subscription with a server using the “$status” operation.
4. SUN-4: Read (i.e., retrieve) a subscription from a server using the “id” of a “Subscription” resource.
5. SUN-5: The Health IT Module’s “REST-hook” endpoint supports server subscription negotiation and processing including support for “handshake,” “heartbeat,” and “event-notification” transactions.