Difference between revisions of "TestReport FHIR Resource Proposal"
m |
|||
| 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]] | + | [[FHIR Infrastructure]] (FHIR-I) |
==Committee Approval Date:== | ==Committee Approval Date:== | ||
| − | <i> | + | <i>Pending</i> |
==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) --> | ||
| − | + | [[Conformance_and_Guidance_for_Implementation/Testing]] (CGIT) | |
==FHIR Resource Development Project Insight ID== | ==FHIR Resource Development Project Insight ID== | ||
| − | + | ||
| + | Pending | ||
<!-- 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 --> | ||
| Line 59: | Line 60: | ||
==RIM scope== | ==RIM scope== | ||
| − | N/A - | + | N/A - This resource operates outside of the space covered by the RIM as "meta" information about FHIR-conformant systems. |
<!-- 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 reports" is well understood. Formal testing has been used to drive IHE testing of HL7 interfaces as well as CDA systems. Test reports may be created in a package but each is distinct corresponds to a distinct test script execution and may be used in supporting certification testing of FHIR interfaces. | |
<!-- Does the resource meet the following characteristics? | <!-- Does the resource meet the following characteristics? | ||
| Line 78: | Line 79: | ||
==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 | + | 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 seeking to verify and report on 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 93: | Line 94: | ||
==Resource Relationships== | ==Resource Relationships== | ||
| − | + | * References TestScript to define the original testing context: resources, operations, and asserts | |
<!-- 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? | ||
Revision as of 21:01, 30 August 2017
This page documents a Pending FHIR Resource Proposal
Contents
- 1 PutProposedResourceNameHere
- 1.1 Owning committee name
- 1.2 Committee Approval Date:
- 1.3 Contributing or Reviewing Work Groups
- 1.4 FHIR Resource Development Project Insight ID
- 1.5 Scope of coverage
- 1.6 RIM scope
- 1.7 Resource appropriateness
- 1.8 Expected implementations
- 1.9 Content sources
- 1.10 Example Scenarios
- 1.11 Resource Relationships
- 1.12 Timelines
- 1.13 gForge Users
- 1.14 When Resource Proposal Is Complete
PutProposedResourceNameHere
Owning committee name
FHIR Infrastructure (FHIR-I)
Committee Approval Date:
Pending
Contributing or Reviewing Work Groups
Conformance_and_Guidance_for_Implementation/Testing (CGIT)
FHIR Resource Development Project Insight ID
Pending
Scope of coverage
The TestReport resource is an infrastructure resource used to define the results of software tests on one or more FHIR servers (and possibly clients). It includes a link to the TestScript resource that was executed and provides the state or outcome of each individual operation and assert. Additional details may be provided in markdown text for each operation and assert. The scope is limited to reporting on 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 operates outside of the space covered by the RIM as "meta" information about FHIR-conformant systems.
Resource appropriateness
The notion of "test reports" is well understood. Formal testing has been used to drive IHE testing of HL7 interfaces as well as CDA systems. Test reports may be created in a package but each is distinct corresponds to a distinct test script execution and may be used in supporting certification testing of FHIR interfaces.
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 seeking to verify and report on 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
- References TestScript to define the original testing context: resources, operations, and asserts
Timelines
Draft as part of STU 3
gForge Users
N/A
When Resource Proposal Is Complete
When you have completed your proposal, please send an email to FMGcontact@HL7.org
