This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "TestScript FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
Line 3: Line 3:
 
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 
<div style="background:#F0F0F0">
 
<div style="background:#F0F0F0">
This page documents a [[:category:Pending FHIR Resource Proposal|Pending]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]]
+
This page documents a [[:category:Approved FHIR Resource Proposal|Approved]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]]
 
</div>
 
</div>
 
</div>
 
</div>
 
[[Category:FHIR Resource Proposal]]
 
[[Category:FHIR Resource Proposal]]
[[Category:Pending FHIR Resource Proposal]]
+
[[Category:Approved FHIR Resource Proposal]]
  
  

Revision as of 21:41, 22 July 2015



TestScript

Owning committee name

FHIR Infrastructure

Contributing or Reviewing Work Groups

  • CGIT

FHIR Resource Development Project Insight ID

???

Scope of coverage

The TestScript resource is an infrastructure resource used to define software tests that can be executed on one or more FHIR servers (and possibly clients). It includes definitions of data, setup, teardown, testing actions and expected results. The scope is limited to testing FHIR conformance-related behavior and does not apply to general user interface testing nor tests related to other standards


RIM scope

N/A - this resource is outside the scope of RIM. It is notionally similar to

Resource appropriateness

The notion of "test scripts" is well understood. Formal test scripts have been used to drive IHE testing of HL7 interfaces as well as CDA systems. Test scripts may be created in a package but each is distinctly maintainable. There is considerable interest in being able to define test scripts for inclusion as part of implementation guides and for use in supporting certification testing of FHIR interfaces. The current size of the resource is approximately 60 data elements, however this larger size is consistent with many of the "conformance" resources.

Expected implementations

This resource will be used in FHIR connectathons, as part of HL7 certification processes, within IHE certification tooling and by affiliates, implementers and other groups seeing to verify system conformance

Content sources

MIF, IHE test tooling, HL7 CDA certification tooling

Example Scenarios

  • Test system against an implementation guide
  • Test system for compliance with a set of RFP requirements

Resource Relationships

  • Part of FHIR ImplementationGuides
  • References StructureDefinitions to define the expected contents of inbound and outbound resources
  • Relies on example/test instances of all resources as part of the testing process
  • Verifies alignment of a system with its stated Conformance resource.

Timelines

Draft is part of DSTU 2

gForge Users

N/A