/
Technical Testing Requirements

Technical Testing Requirements

Apr 04, 2022

Capability Testing

To enable developers to verify implementations against a standards based requirement, data definitions, testing tools and infrastructure are needed

A common testing framework can be used by all developers to ensure compatibility and consistent behaviour across systems; and aids in the quality assessment of developed systems being fit for purpose in tested areas. This can also form the basis of technical education to allow verification of generated data instances when training.

To support FHIR testing in different areas the following implementation guides are initially relevant:

  • AU Base on R4 - recommended localised basis of all Australlian IG content

  • AEHRC Primary Care IG - working implementation guide from project

  • AU Provider Directory on R4 - support for secure messaging directory services

To support system capability testing the following general requirements are noted as key general needs:

  • SMART Application Launch

  • FHIR data content conformance (against IG)

  • FHIR interactions capability test (against IG)

At a high level the process involves:

  • Define specific scope of requirements; agreed areas of interest

  • Confirm FHIR implementation guide content is adequate for testing 

  • Use and develop testing modules for coverage of tests needed

It is recommended the infrastructure required to support this testing can be primarily supplied by the use of existing tools deployed and maintained as a conformance platform.  This includes:

  • Ontoserver: terminology/profile validation; needed to test FHIR instances for correctness including terminology content

  • Inferno Framework (https://inferno.healthit.gov/) : testing framework; modules need to be assessed and developed for local requirements


These need to be assembled into an operating framework including

  • Use of existing Inferno Framework modules e.g. SMART App Launch

  • Development of specialised Inferno Framework modules for relevant local specifications

  • Deployment and Hosting of the framework to make available

  • Maintain terminology content

  • Maintain FHIR implementation guide content

 

Validating IG Content Quality Assurance

Environment

  • Ontoserver instance

  • Referenced terminologies loaded

  • FHIR IG package(s) loaded

FHIR IG package validity:

  • Publishing: Check can be registered

  • Publishing: Check correct identification

  • Publishing: Check correct version

FHIR IG package content validation check:

  • For all profiles

    • Test compliant instances

    • Test all constrained element options 

    • Test invalid instances

    • Canonical URL resolution

    • Check correct maturity level

    • Check correct status

    • Test derivation from profile can build

    • Validation in derived profile

Performance test (desirable)

  • Need consistent test environment - VM

  • Record of test case performance metrics

  • Initially looking any large degradation