This wiki has undergone a migration to Confluence found Here
Difference between revisions of "TestScript FHIR Resource Proposal"
Jump to navigation
Jump to search
(Replaced content with "{{subst::Template:FHIR Resource Proposal}}") |
|||
| Line 13: | Line 13: | ||
| − | = | + | =TestScript= |
<!-- Resource names should meet the following characteristics: | <!-- Resource names should meet the following characteristics: | ||
| Line 30: | Line 30: | ||
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. --> | <!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. --> | ||
| − | [[ | + | [[FHIR Infrastructure]] |
==Contributing or Reviewing Work Groups== | ==Contributing or Reviewing Work Groups== | ||
<!-- Additional work groups that may have an interest in contributing to, or reviewing the content of the resource (optional) --> | <!-- Additional work groups that may have an interest in contributing to, or reviewing the content of the resource (optional) --> | ||
| − | * | + | * CGIT |
| − | |||
| − | |||
==FHIR Resource Development Project Insight ID== | ==FHIR Resource Development Project Insight ID== | ||
| − | + | ??? | |
<!-- Please specify the id of your work group’s PSS for doing FHIR work. (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc --> | <!-- Please specify the id of your work group’s PSS for doing FHIR work. (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc --> | ||
==Scope of coverage== | ==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 | ||
<!-- Define the full scope of coverage for the resource. The scope must be clearly delineated such that it does not overlap with any other existing or expected resource. The scope will be used to govern "what is the set of potential applications to consider when evaluating what elements are 'core' – i.e. in the 80%" | <!-- Define the full scope of coverage for the resource. The scope must be clearly delineated such that it does not overlap with any other existing or expected resource. The scope will be used to govern "what is the set of potential applications to consider when evaluating what elements are 'core' – i.e. in the 80%" | ||
| Line 57: | Line 56: | ||
==RIM scope== | ==RIM scope== | ||
| − | + | N/A - this resource is outside the scope of RIM. It is notionally similar to | |
<!-- Identify the formal RIM mapping for the root concept of the resource. The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. --> | <!-- Identify the formal RIM mapping for the root concept of the resource. The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. --> | ||
==Resource appropriateness== | ==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. | |
<!-- Does the resource meet the following characteristics? | <!-- Does the resource meet the following characteristics? | ||
| Line 76: | Line 75: | ||
==Expected implementations== | ==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 | |
<!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. --> | <!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. --> | ||
==Content sources== | ==Content sources== | ||
| − | + | MIF, IHE test tooling, HL7 CDA certification tooling | |
<!-- List all of the specifications (beyond those in the "standard" (FHIR_Design_Requirements_Sources) list of source specifications) that you’re planning to consult | <!-- List all of the specifications (beyond those in the "standard" (FHIR_Design_Requirements_Sources) list of source specifications) that you’re planning to consult | ||
| Line 86: | Line 85: | ||
==Example Scenarios== | ==Example Scenarios== | ||
| − | + | * Test system against an implementation guide | |
| + | * Test system for compliance with a set of RFP requirements | ||
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource. They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) --> | <!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource. They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) --> | ||
==Resource Relationships== | ==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. | ||
<!-- What are the resources do you expect will reference this resource and in what context? | <!-- What are the resources do you expect will reference this resource and in what context? | ||
| Line 101: | Line 104: | ||
==Timelines== | ==Timelines== | ||
| − | + | Draft is part of DSTU 2 | |
<!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting --> | <!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting --> | ||
==gForge Users== | ==gForge Users== | ||
| − | + | N/A | |
<!-- Identify the userids who will require commit access to gForge to maintain the resource. (Ensure all users have registered for gForge.) --> | <!-- Identify the userids who will require commit access to gForge to maintain the resource. (Ensure all users have registered for gForge.) --> | ||
Revision as of 18:28, 18 July 2015
This page documents a Pending FHIR Resource Proposal
Contents
- 1 TestScript
- 1.1 Owning committee name
- 1.2 Contributing or Reviewing Work Groups
- 1.3 FHIR Resource Development Project Insight ID
- 1.4 Scope of coverage
- 1.5 RIM scope
- 1.6 Resource appropriateness
- 1.7 Expected implementations
- 1.8 Content sources
- 1.9 Example Scenarios
- 1.10 Resource Relationships
- 1.11 Timelines
- 1.12 gForge Users
TestScript
Owning committee name
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
