This wiki has undergone a migration to Confluence found Here
Difference between revisions of "TestReport FHIR Resource Proposal"
Jump to navigation
Jump to search
| Line 38: | Line 38: | ||
<!-- 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 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 | ||
<!-- 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 60: | Line 59: | ||
==RIM scope== | ==RIM scope== | ||
| − | + | N/A - this resource is outside the scope of RIM. | |
<!-- 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. --> | ||
| Line 79: | Line 78: | ||
==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. --> | ||
| Line 89: | Line 88: | ||
==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== | ||
| − | + | ??? | |
<!-- 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 104: | Line 104: | ||
==Timelines== | ==Timelines== | ||
| − | + | Draft as part of STU 3 | |
<!-- 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.) --> | ||
==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]''' | ||
Revision as of 20:36, 7 October 2016
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
Committee Approval Date:
Please enter the date that the committee approved this Resource proposal
Contributing or Reviewing Work Groups
- CGIT
FHIR Resource Development Project Insight ID
???
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 is outside the scope of RIM.
Resource appropriateness
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
Example Scenarios
- Test system against an implementation guide
- Test system for compliance with a set of RFP requirements
Resource Relationships
???
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
