This wiki has undergone a migration to Confluence found Here

Difference between revisions of "TestReport FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
(migrate to Confluence)
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
  
 
<div class="messagebox cleanup metadata">
 
<div class="messagebox cleanup metadata">
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
+
Current version: https://confluence.hl7.org/display/FHIR/TestReport+FHIR+Resource+Proposal<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:Pending FHIR Resource Proposal|Pending]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]]
Line 13: Line 13:
  
  
=PutProposedResourceNameHere=
+
=TestReport=
  
 
<!-- 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]]
+
[[FHIR Infrastructure]] (FHIR-I)
  
 
==Committee Approval Date:==
 
==Committee Approval Date:==
<i>Please enter the date that the committee approved this Resource proposal</i>
+
<i>2017-10-02</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) -->
* CGIT
+
[[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 - this resource is outside the scope of RIM.
+
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 and corresponds to a specific 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 seeing to verify system conformance.
+
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 88: Line 89:
  
 
==Example Scenarios==
 
==Example Scenarios==
* Test system against an implementation guide
+
 
* Test system for compliance with a set of RFP requirements
+
*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==
???
+
 
 +
*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?
  
Line 113: Line 116:
 
==When Resource Proposal Is Complete==
 
==When Resource Proposal Is Complete==
 
'''When you have completed your proposal, please send an email to [mailto:FMGcontact@HL7.org FMGcontact@HL7.org]'''
 
'''When you have completed your proposal, please send an email to [mailto:FMGcontact@HL7.org FMGcontact@HL7.org]'''
 +
===FMG Note===
 +
Waiting to hear from the community if this resource is needed

Latest revision as of 15:31, 31 October 2019



TestReport

Owning committee name

FHIR Infrastructure (FHIR-I)

Committee Approval Date:

2017-10-02

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 and corresponds to a specific 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

FMG Note

Waiting to hear from the community if this resource is needed