Services specifications developed by NCI and the community have to be testable to ensure that the implementation conforms to the specification.
Conformance testing leverages the artifact and service metadata to validate that an implementation adequately addresses the requirements stated in the service specification. An example of service requirement is the ability to specify a response time in the specification (design time) and validate that this response time is valid for an implementation of the service. Additional test points include but are not limited to binding to specific terminologies and domain models.
Conformance testing allows both CBIIT and other HL7 SAIF adopters to validate specifications.
The requirements listed above are derived from the following use cases:
- CBIIT's adoption of ECCF: ECCF requires all specification developers to make conformance statements, the conformance testing framework leverages these conformance statements to generate validation tests.
- Other National Initiatives: Other national organizations like NIST are adopting a similar approach to conformance testing.
Functional Profile Group
- 5.2.4.1 - Create Conformance Statements Sept. 6, 2010
- 5.2.4.2 - Search and Access Conformance Statements Sept. 6, 2010 Conformance testing leverages the artifact and service metadata to validate that an implementation adequately addresses the requirements stated in the service specification. An example of service requirement is the ability to specify a response time in the specification (design time) and validate that this response time is valid for an implementation of the service. Aadditional test points include but are not limited to binding to specific terminologies and domain models.
- 5.2.4.3 - Test for Conformance Sept. 6, 2010 Conformance testing allows both CBIIT and other HL7 SAIF adopters to validate specifications.
