Summary
Description of the profile
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.
Validation capabilities include;
- Validation of harmonization
- Ensure mappings between terminologies are "semantically valid". In other words, to detect mappings that can cause semantic and logical inconsistencies in the terminologies involved in those mappings
- Support validation for use; for example a protocol designer will need to be able to build and validate the SEC based on programmatic retrieval of metadata.
- Validate consistency of model representations across multiple repositories
Capabilities
Requirements traceability
Requirement |
Source |
Capability |
|---|---|---|
Validation of harmonization |
Gap Analysis::Validate::103 - Validation of harmonization |
|
Ensure mappings between terminologies are "semantically valid"? In other words, to detect mappings that can cause semantic and logical inconsistencies in the terminologies involved in those mappings |
Gap Analysis::Validate::137 - Mapping Validation |
|
Identify data elements that should be harmonized with existing data elements that are semantically close |
Gap Analysis::Validate::152 - Validation of data element usage |
|
Validate consistency of model representations across multiple repositories |
Gap Analysis::Validate::160.1 - Validate consistency of model representations across multiple repositories |
|
Conformance testing allows both CBIIT and other HL7 SAIF adopters to validate specifications. |
Semantic Infrastructure Requirements::Conformance Testing::Test for Conformance |
validateHarmonization, validateTerminologies, validateUsage, validateModelRepresentationConsistency, |
validateHarmonization
Description
Validation of harmonization
Requirements addressed
Overview of possible operations
To be provided.
validateModelRepresentationConsistency
Description
Validate consistency of model representations across multiple repositories
Requirements addressed
- 160.1 - Validate consistency of model representations across multiple repositories
- Test for Conformance
Overview of possible operations
To be provided.
validateTerminologies
Description
Ensure mappings between terminologies are "semantically valid"? In other words, to detect mappings that can cause semantic and logical inconsistencies in the terminologies involved in those mappings
Requirements addressed
Overview of possible operations
To be provided.
validateUsage
Description
Support validation for use, for example a protocol designer will need to be able to build and validate the SEC based on programmatic retrieval of data element metadata.
Requirements addressed
Overview of possible operations
To be provided.
