This page is part of the electronic Case Reporting (eCR) (v0.1.0: STU 1 Ballot 1) based on FHIR R3. The current version which supercedes this version is 1.0.0. For a full list of available versions, see the Directory of published versions 
CapabilityStatements defined for this Guide
source file: source/pages/_include/capstatements.md file
The following CapabilityStatements define the conformance requirements for this implementation guide.
Trigger Code Transaction
This section describes the expected capabilities of a server that stores Reportable Conditions Trigger Codes (RCTC).
Conformance requirements for the RCTC Server
The RCTC Server SHALL:
- Store all RCTC value sets as individual ValueSet resources, and as a single Bundle resource containing all RCTC ValueSet resources.
- Implement the RESTful behavior according to the FHIR specification.
- Return the following response classes:
- (Status 200): successful operation
- (Status 400): invalid parameter
- (Status 401/4xx): unauthorized request
- (Status 403): insufficient scope
- (Status 404): unknown resource
- (Status 410): deleted resource.
- Support json and xml resource formats for all RCTC interactions.
- Declare a CapabilityStatement identifying the list of profiles, operations, search parameter supported.
The RCTC Server SHOULD:
- Support clients creating and updating Subscription resource for all RCTC ValueSet and Bundle resources.
- Implement Subscription services per the FHIR specification.
Conformance requirements for an RCTC Client
The RCTC Client SHALL:
- Support fetching RCTC ValueSet and Bundle resources using the supported RESTful interactions and search parameters declared in the RCTC Server CapabilityStatement.
The RCTC Client SHOULD:
- Support creating and updating Subscription resources on the RCTC server.
- Support receiving updates to subscriptions using one or more of the methods described in the FHIR specification.
