Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

Capability Testing

To enable developers to check and verify implementations against a standards based requirement, data definitions, testing tools and infrastructure are required. FHIR conformance testing requires suitable implementation guides to define the interfacing requirement. FHIR offers standardised validation of data based on implementation guide profiles so fully defined and quality tested implementation guides offer the basis of data testing using standard tools.needed

A common testing framework can be used by all developers to ensure compatibility and consistent behaviour across systems; and aids in the quality assessemnt 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 difference different areas the following implementation guides are currently 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


  • SMART Application Launch
  • FHIR data content conformance (against IG)
  • FHIR interactions capability test (against IG)

To support At a basic high level of capability by systems the following is recommendedthe 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 generally 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 ( : testing framework; modules need to be assessed and developed for local requirements

Alongside the tools ongoing activities needed include



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