Skip to content

TestScript / Inferno / Touchstone Alignment

Intent

Write portable conformance tests using TestScript/TestPlan conventions and execute on common platforms.

Structure

Portable test alignment is a structure of assets that can execute on multiple platforms (TestScript/TestPlan + data bundles + reporting). Structurally it separates specification (what to test) from execution (where/how it’s run).

  • TestPlan: scenario and environment documentation + links to conformance statements
  • TestScript: portable test definitions with fixtures, setup, and assertions
  • Synthetic data: curated bundles free of PHI that validate against profiles
  • Execution adapters: platform-specific runners (Inferno, Touchstone, etc.) that map to the same logical tests
  • Reporting: consistent pass/fail summaries that can be compared across platforms and releases

Key Components

TestPlan

  • Define test scope, actors, and scenarios
  • Describe required environment setup
  • Link tests to conformance statements
  • Keep the plan versioned
  • Use the plan to coordinate cross-org testing

TestScript

  • Write portable, standards-based test definitions
  • Keep tests readable and modular
  • Use fixtures and variable extraction consistently
  • Ensure tests work across platforms where possible
  • Version tests with the IG package

Synthetic data

  • Provide consistent test data bundles
  • Include required terminology and identifiers
  • Avoid PHI or real patient data
  • Ensure data matches profile constraints
  • Maintain data alongside tests

Execution report

  • Capture pass/fail outcomes per scenario
  • Include logs and failure context
  • Track results across products
  • Publish summaries for implementers
  • Use reports as release gates

Behavior

Write once, run many

Start with a portable smoke test set, then grow coverage while keeping tests readable and maintainable.

Author portable tests

  • Define scenarios and actors in TestPlan.
  • Implement the core flows in TestScript using consistent fixture and variable conventions.
  • Keep assertions aligned to conformance statements and examples.

Execute and compare

  • Run tests on at least two platforms/targets to catch platform assumptions.
  • Normalize reporting so failures are comparable.
  • When a platform needs a feature, document the divergence and keep a portable baseline.

Benefits

  • Reusable across vendors
  • Supports certification

Trade-offs

  • Verbose; start with smoke suite

References