TCAMT, Test Case Authoring and Management Tool
Compiled by KHAO Editorial — aggregated from 2 sources. See llms.txt for citation guidance.
★ Tier-1 Source
It is important to provide users with numerous examples of the scenarios covered by the implementation guide.
Key facts
- The NIST Test Case Authoring and Management Tool (TCAMT, ) is a productivity tool that can be used to create use case scenarios and example messages
- TCAMT has been used to create test cases for ONC EHR certification, test cases for HIMSS IIP EHR certification, and template messages for the American Immunization Registry Association (AIRA)
- A key design component in TCAMT is its use of the XML profiles created in IGAMT as a foundation
- For example, elements with “required, but may be empty (RE)” usage, elements with “conditional usage (C)”, or elements with cardinality greater than “1” cannot be assessed without targeted tests
Summary
The NIST Test Case Authoring and Management Tool (TCAMT, ) is a productivity tool that can be used to create use case scenarios and example messages. The foundation of TCAMT is the computable specification model created in IGAMT. TCAMT is a tool used to create HL7 v2.x test plans that contain one or more (typically many) test cases. Key features in TCAMT include test plan creation (narrative and computable), IGAMT XML profile import, HL7 v2 message creation and import, constraint editing, constraint and messaging templates, and multiple export formats. Targeted test cases are critical for assessing the capabilities of a system. TCAMT allows domain experts to create test cases (that include example messages) for certain scenarios and capabilities.
A key design component in TCAMT is its use of the XML profiles created in IGAMT as a foundation. TCAMT also allows the user to enter additional assertion indicators based on what they want to test. For elements with “RE” usage, the element must be supported by the system-under test (SUT), but in a given message instance the element may not be populated. In a context-free environment, the absence of data in a message is not a conformance violation for elements with “RE” usage.