Others titles
- FHIR Test Report Resource
- Electronic Health Records Exchange Through FHIR
Keywords
- FHIR
- HL7
- Medical Terminology
- Processes Data
- Processes Information
- Processes Documentation
- Health Information Exchange
- Electronic Health Records
- FHIR Smart
- Smart on FHIR
Test Report
The Test Report structure mirrors the Test Script concepts of having sections for setup, tests, and teardown. The Test Script resource is used to define tests that can be executed on one or more Fast Healthcare Interoperability Resources (FHIR) servers.
Get The Data
- ResearchNon-Commercial, Share-Alike, Attribution Free Forever
- CommercialCommercial Use, Remix & Adapt, White Label Log in to download
Description
The Test Report resource defines how systems should encode the summarized results of executing a Test Script. If present, these ordered lists should mirror the actions (either operations or assertions) of the referenced Test Script with a result code: pass, skip, fail, warning, or error.
Implementers should be familiar with the testing concepts and descriptions found in Testing Fast Healthcare Interoperability Resources (FHIR) before working with this resource.
About this Dataset
Data Info
Date Created | 2018-09-20 |
---|---|
Last Modified | 2023-03-26 |
Version | 5.0.0 |
Update Frequency |
Annual |
Temporal Coverage |
N/A |
Spatial Coverage |
United States |
Source | John Snow Labs; Health Level Seven International; |
Source License URL | |
Source License Requirements |
N/A |
Source Citation |
N/A |
Keywords | FHIR, HL7, Medical Terminology, Processes Data, Processes Information, Processes Documentation, Health Information Exchange, Electronic Health Records, FHIR Smart, Smart on FHIR |
Other Titles | FHIR Test Report Resource, Electronic Health Records Exchange Through FHIR |
Data Fields
Name | Description | Type | Constraints |
---|---|---|---|
Concept_Name | Name of the concept in the FHIR structure | string | required : 1 |
Computer_Ready_Name | A Computer-ready name (e.g. a token) that identifies the structure - suitable for code generation. Note that this name (and other names relevant for code generation, including element & slice names, codes etc) may collide with reserved words in the relevant target language, and code generators will need to handle this. | string | - |
Type | The type the structure describes. | string | - |
Dollar_Ref | The "$ref" string value contains a Uniform Resource Identifier (URI) which identifies the location of the JSON value being referenced. | string | - |
Description | A free text natural language description of the structure and its use | string | - |
Items | The value of the keyword should be an object or an array of objects. If the keyword value is an object, then for the data array to be valid each item of the array should be valid according to the schema in this value. | string | - |
Enum | The value of the keyword should be an array of unique strings. The data object to be valid should contain all properties with names equal to the elements in the keyword value. | string | - |
Required | The value of the keyword should be an array of unique strings. The data object to be valid should contain all properties with names equal to the elements in the keyword value. | string | - |
Const | The value of this keyword can be anything. The data is valid if it is deeply equal to the value of the keyword. | string | - |
Data Preview
Concept Name | Computer Ready Name | Type | Dollar Ref | Description | Items | Enum | Required | Const |
TestReport;resourceType;;;This is a TestReport resource;;;;TestReport | ||||||||
TestReport;id;;#/definitions/id;The logical id of the resource | as used in the URL for the resource. Once assigned | this value never changes.;;;; | ||||||
TestReport;meta;;#/definitions/Meta;The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.;;;; | ||||||||
TestReport;implicitRules;;#/definitions/uri;A reference to a set of rules that were followed when the resource was constructed | and which must be understood when processing the content. Often | this is a reference to an implementation guide that defines the special rules along with other profiles etc.;;;; | ||||||
TestReport;_implicitRules;;#/definitions/Element;Extensions for implicitRules;;;; | ||||||||
TestReport;language;;#/definitions/code;The base language in which the resource is written.;;;; | ||||||||
TestReport;_language;;#/definitions/Element;Extensions for language;;;; | ||||||||
TestReport;text;;#/definitions/Narrative;"A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data | but is required to contain sufficient detail to make it ""clinically safe"" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.";;;; | |||||||
TestReport;contained;array;;These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently | nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.;{'$ref': '#/definitions/ResourceList'};;; | |||||||
TestReport;extension;array;;May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and managable | there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension | there is a set of requirements that SHALL be met as part of the definition of the extension.;{'$ref': '#/definitions/Extension'};;; |