FHIR CI-Build

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions icon

FHIR Infrastructure icon Work GroupMaturity Level: 0 DraftSecurity Category: Business Compartments: No defined compartments

Detailed Descriptions for the elements in the TestPlan resource.

TestPlan
Element IdTestPlan
Definition

A plan for executing testing on an artifact or specifications.

Short DisplayDescription of intented testing
Cardinality0..*
TypeCanonicalResource
Summaryfalse
Invariants
Defined on this element
cnl-0Warning Name should be usable as an identifier for the module by machine processing applications such as code generationname.exists() implies name.matches('^[A-Z]([A-Za-z0-9_]){1,254}$')
TestPlan.url
Element IdTestPlan.url
Definition

An absolute URI that is used to identify this test plan when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which an authoritative instance of this test plan is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the test plan is stored on different servers.

Short DisplayCanonical identifier for this test plan, represented as a URI (globally unique)
Cardinality0..1
Typeuri
Requirements

Allows the test plan to be referenced by a single globally unique identifier.

Alternate Namesurl; authoritative-url; destination; identity
Summarytrue
Comments

Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version.

The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in Technical and Business Versions.

In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the meta.source element to indicate where the current master source of the resource can be found.

Invariants
Defined on this element
cnl-1Warning URL should not contain | or # - these characters make processing canonical references problematicexists() implies matches('^[^|# ]+$')
TestPlan.identifier
Element IdTestPlan.identifier
Definition

A formal identifier that is used to identify this test plan when it is represented in other formats, or referenced in a specification, model, design or an instance.

Short DisplayBusiness identifier identifier for the test plan
NoteThis is a business identifier, not a resource identifier (see discussion)
Cardinality0..*
TypeIdentifier
Requirements

Allows externally provided and/or usable business identifiers to be easily associated with the module.

Summarytrue
Comments

Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this test plan outside of FHIR, where it is not possible to use the logical URI.

TestPlan.version
Element IdTestPlan.version
Definition

The identifier that is used to identify this version of the test plan when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the test plan author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence.

Short DisplayBusiness version of the test plan
NoteThis is a business versionId, not a resource version id (see discussion)
Cardinality0..1
Typestring
Summarytrue
Comments

There may be different test plan instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the test plan with the format [url]|[version]. The version SHOULD NOT contain a '#' - see Business Version.

TestPlan.versionAlgorithm[x]
Element IdTestPlan.versionAlgorithm[x]
Definition

Indicates the mechanism used to compare versions to determine which is more current.

Short DisplayHow to compare versions
Cardinality0..1
Terminology BindingVersion Algorithm (Extensible)
Typestring|Coding
[x] NoteSee Choice of Datatypes for further information about how to use [x]
Summarytrue
Comments

If set as a string, this is a FHIRPath expression that has two additional context variables passed in - %version1 and %version2 and will return a negative number if version1 is newer, a positive number if version2 and a 0 if the version ordering can't be successfully be determined.

TestPlan.name
Element IdTestPlan.name
Definition

A natural language name identifying the test plan. This name should be usable as an identifier for the module by machine processing applications such as code generation.

Short DisplayName for this test plan (computer friendly)
Cardinality0..1
Typestring
Requirements

Support code generation.

Summarytrue
Comments

The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.

Invariants
Affect this element
cnl-0Warning Name should be usable as an identifier for the module by machine processing applications such as code generationname.exists() implies name.matches('^[A-Z]([A-Za-z0-9_]){1,254}$')
TestPlan.title
Element IdTestPlan.title
Definition

A short, descriptive, user-friendly title for the test plan.

Short DisplayName for this test plan (human friendly)
Cardinality0..1
Typestring
Summaryfalse
Comments

This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.

TestPlan.status
Element IdTestPlan.status
Definition

The status of this test plan. Enables tracking the life-cycle of the content.

Short Displaydraft | active | retired | unknown
Cardinality1..1
Terminology BindingPublicationStatus (Required)
Typecode
Is Modifiertrue (Reason: This is labeled as "Is Modifier" because applications should not use a retired {{title}} without due consideration)
Summarytrue
Comments

Allows filtering of test plans that are appropriate for use versus not.

See guidance around (not) making local changes to elements here.

TestPlan.experimental
Element IdTestPlan.experimental
Definition

A Boolean value to indicate that this test plan is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage.

Short DisplayFor testing purposes, not real usage
Cardinality0..1
Typeboolean
Meaning if MissingIf absent, this resource is treated as though it is not experimental.
Requirements

Enables experimental content to be developed following the same lifecycle that would be used for a production-level test plan.

Summarytrue
Comments

Allows filtering of test plans that are appropriate for use versus not.

TestPlan.date
Element IdTestPlan.date
Definition

The date (and optionally time) when the test plan was last significantly changed. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the test plan changes.

Short DisplayDate last changed
Cardinality0..1
TypedateTime
Alternate NamesRevision Date
Summarytrue
Comments

The date is often not tracked until the resource is published, but may be present on draft content. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the test plan. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.

See guidance around (not) making local changes to elements here.

TestPlan.publisher
Element IdTestPlan.publisher
Definition

The name of the organization or individual responsible for the release and ongoing maintenance of the test plan.

Short DisplayName of the publisher/steward (organization or individual)
Cardinality0..1
Typestring
Requirements

Helps establish the "authority/credibility" of the test plan. May also allow for contact.

Summarytrue
Comments

Usually an organization but may be an individual. The publisher (or steward) of the test plan is the organization or individual primarily responsible for the maintenance and upkeep of the test plan. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the test plan. This item SHOULD be populated unless the information is available from context.

TestPlan.contact
Element IdTestPlan.contact
Definition

Contact details to assist a user in finding and communicating with the publisher.

Short DisplayContact details for the publisher
Cardinality0..*
TypeContactDetail
Summarytrue
Comments

May be a web site, an email address, a telephone number, etc.

See guidance around (not) making local changes to elements here.

TestPlan.description
Element IdTestPlan.description
Definition

A free text natural language description of the test plan from a consumer's perspective.

Short DisplayNatural language description of the test plan
Cardinality0..1
Typemarkdown
Summaryfalse
Comments

This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the test plan as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the test plan is presumed to be the predominant language in the place the test plan was created).

TestPlan.useContext
Element IdTestPlan.useContext
Definition

The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate test plan instances.

Short DisplayThe context that the content is intended to support
Cardinality0..*
TypeUsageContext
Requirements

Assist in searching for appropriate content.

Summarytrue
Comments

When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.

TestPlan.jurisdiction
Standards StatusThis element has a standards status of "Deprecated" which is different from the status of the whole resource
Element IdTestPlan.jurisdiction
Definition

A legal or geographic region in which the test plan is intended to be used.

Short DisplayIntended jurisdiction where the test plan applies (if applicable)
Cardinality0..*
Terminology BindingJurisdiction ValueSet (Extensible)
TypeCodeableConcept
Summarytrue
Comments

It may be possible for the test plan to be used in jurisdictions other than those for which it was originally designed or intended.

DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.)

TestPlan.purpose
Element IdTestPlan.purpose
Definition

Explanation of why this test plan is needed and why it has been designed as it has.

Short DisplayWhy this test plan is defined
Cardinality0..1
Typemarkdown
Summaryfalse
Comments

This element does not describe the usage of the test plan Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this test plan.

TestPlan.copyright
Element IdTestPlan.copyright
Definition

A copyright statement relating to the test plan and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the test plan. The short copyright declaration (e.g. (c) '2015+ xyz organization' should be sent in the copyrightLabel element.

Short DisplayUse and/or publishing restrictions
Cardinality0..1
Typemarkdown
Requirements

Consumers must be able to determine any legal restrictions on the use of the test plan and/or its content.

Alternate NamesLicense; Restrictions
Summaryfalse
TestPlan.copyrightLabel
Element IdTestPlan.copyrightLabel
Definition

A short string (<50 characters), suitable for inclusion in a page footer that identifies the copyright holder, effective period, and optionally whether rights are resctricted. (e.g. 'All rights reserved', 'Some rights reserved').

Short DisplayCopyright holder and year(s)
Cardinality0..1
Typestring
Requirements

Defines the content expected to be rendered in all representations of the artifact.

Summaryfalse
Comments

The (c) symbol should NOT be included in this string. It will be added by software when rendering the notation. Full details about licensing, restrictions, warrantees, etc. goes in the more general 'copyright' element.

TestPlan.category
Element IdTestPlan.category
Definition

The category of the Test Plan - can be acceptance, unit, performance, etc.

Short DisplayThe category of the Test Plan - can be acceptance, unit, performance
Cardinality0..*
Terminology BindingTest Script Scope Phase Type (Example)
TypeCodeableConcept
Summaryfalse
TestPlan.scope
Element IdTestPlan.scope
Definition

What is being tested with this Test Plan - a conformance resource, or narrative criteria, or an external reference...

Short DisplayWhat is being tested with this Test Plan - a conformance resource, or narrative criteria, or an external reference
Cardinality0..*
TypeReference
Summaryfalse
TestPlan.testTools
Element IdTestPlan.testTools
Definition

A description of test tools to be used in the test plan.

Short DisplayA description of test tools to be used in the test plan - narrative for now
Cardinality0..1
Typemarkdown
Summaryfalse
TestPlan.dependency
Element IdTestPlan.dependency
Definition

The required criteria to execute the test plan - e.g. preconditions, previous tests...

Short DisplayThe required criteria to execute the test plan - e.g. preconditions, previous tests
Cardinality0..*
Summaryfalse
TestPlan.dependency.description
Element IdTestPlan.dependency.description
Definition

A textual description of the criterium - what is needed for the dependency to be considered met.

Short DisplayDescription of the dependency criterium
Cardinality0..1
Typemarkdown
Summaryfalse
TestPlan.dependency.predecessor
Element IdTestPlan.dependency.predecessor
Definition

Predecessor test plans - those that are expected to be successfully performed as a dependency for the execution of this test plan.

Short DisplayLink to predecessor test plans
Cardinality0..1
TypeReference
Summaryfalse
TestPlan.exitCriteria
Element IdTestPlan.exitCriteria
Definition

The threshold or criteria for the test plan to be considered successfully executed - narrative.

Short DisplayThe threshold or criteria for the test plan to be considered successfully executed - narrative
Cardinality0..1
Typemarkdown
Summaryfalse
TestPlan.testCase
Element IdTestPlan.testCase
Definition

The individual test cases that are part of this plan, when they they are made explicit.

Short DisplayThe test cases that constitute this plan
Cardinality0..*
Summaryfalse
TestPlan.testCase.sequence
Element IdTestPlan.testCase.sequence
Definition

Sequence of test case - an ordinal number that indicates the order for the present test case in the test plan.

Short DisplaySequence of test case in the test plan
Cardinality0..1
Typeinteger
Summaryfalse
TestPlan.testCase.scope
Element IdTestPlan.testCase.scope
Definition

The scope or artifact covered by the case, when the individual test case is associated with a testable artifact.

Short DisplayThe scope or artifact covered by the case
Cardinality0..*
TypeReference
Summaryfalse
TestPlan.testCase.dependency
Element IdTestPlan.testCase.dependency
Definition

The required criteria to execute the test case - e.g. preconditions, previous tests.

Short DisplayRequired criteria to execute the test case
Cardinality0..*
Summaryfalse
TestPlan.testCase.dependency.description
Element IdTestPlan.testCase.dependency.description
Definition

Description of the criteria.

Short DisplayDescription of the criteria
Cardinality0..1
Typemarkdown
Summaryfalse
TestPlan.testCase.dependency.predecessor
Element IdTestPlan.testCase.dependency.predecessor
Definition

Link to predecessor test plans.

Short DisplayLink to predecessor test plans
Cardinality0..1
TypeReference
Summaryfalse
TestPlan.testCase.testRun
Element IdTestPlan.testCase.testRun
Definition

The actual test to be executed.

Short DisplayThe actual test to be executed
Cardinality0..*
Summaryfalse
TestPlan.testCase.testRun.narrative
Element IdTestPlan.testCase.testRun.narrative
Definition

The narrative description of the tests.

Short DisplayThe narrative description of the tests
Cardinality0..1
Typemarkdown
Summaryfalse
TestPlan.testCase.testRun.script
Element IdTestPlan.testCase.testRun.script
Definition

The test cases in a structured language e.g. gherkin, Postman, or FHIR TestScript.

Short DisplayThe test cases in a structured language e.g. gherkin, Postman, or FHIR TestScript
Cardinality0..1
Summaryfalse
TestPlan.testCase.testRun.script.language
Element IdTestPlan.testCase.testRun.script.language
Definition

The language for the test cases e.g. 'gherkin', 'testscript'.

Short DisplayThe language for the test cases e.g. 'gherkin', 'testscript'
Cardinality0..1
TypeCodeableConcept
Summaryfalse
TestPlan.testCase.testRun.script.source[x]
Element IdTestPlan.testCase.testRun.script.source[x]
Definition

The actual content of the cases - references to TestScripts or externally defined content.

Short DisplayThe actual content of the cases - references to TestScripts or externally defined content
Cardinality0..1
Typestring|Reference
[x] NoteSee Choice of Datatypes for further information about how to use [x]
Summaryfalse
TestPlan.testCase.testData
Element IdTestPlan.testCase.testData
Definition

The test data used in the test case.

Short DisplayThe test data used in the test case
Cardinality0..*
Summaryfalse
TestPlan.testCase.testData.type
Element IdTestPlan.testCase.testData.type
Definition

The type of test data description, e.g. 'synthea'.

Short DisplayThe type of test data description, e.g. 'synthea'
Cardinality1..1
TypeCoding
Summaryfalse
TestPlan.testCase.testData.content
Element IdTestPlan.testCase.testData.content
Definition

The actual test resources when they exist.

Short DisplayThe actual test resources when they exist
Cardinality0..1
TypeReference
Summaryfalse
TestPlan.testCase.testData.source[x]
Element IdTestPlan.testCase.testData.source[x]
Definition

Pointer to a definition of test resources - narrative or structured e.g. synthetic data generation, etc.

Short DisplayPointer to a definition of test resources - narrative or structured e.g. synthetic data generation, etc
Cardinality0..1
Typestring|Reference
[x] NoteSee Choice of Datatypes for further information about how to use [x]
Summaryfalse
TestPlan.testCase.assertion
Element IdTestPlan.testCase.assertion
Definition

The test assertions - the expectations of test results from the execution of the test case.

Short DisplayTest assertions or expectations
Cardinality0..*
Summaryfalse
TestPlan.testCase.assertion.type
Element IdTestPlan.testCase.assertion.type
Definition

The test assertion type - this can be used to group assertions as 'required' or 'optional', or can be used for other classification of the assertion.

Short DisplayAssertion type - for example 'informative' or 'required'
Cardinality0..*
TypeCodeableConcept
Summaryfalse
TestPlan.testCase.assertion.object
Element IdTestPlan.testCase.assertion.object
Definition

The focus or object of the assertion i.e. a resource.

Short DisplayThe focus or object of the assertion
Cardinality0..*
TypeCodeableReference
Summaryfalse
TestPlan.testCase.assertion.result
Element IdTestPlan.testCase.assertion.result
Definition

The test assertion - the expected outcome from the test case execution.

Short DisplayThe actual result assertion
Cardinality0..*
TypeCodeableReference
Summaryfalse