net.ihe.gazelle.assets.SearchCriteria : 64 assertions found for this search Review filtered assertions

Assertion

Applies to

Applied to
Not applied to

Coverage

Covered by
Not covered by
Id scheme
Assertion id
Status
Testable?
#Coverage
#Applies to
Comment
Predicate
Page
Tags
Last changed
Actions
RFDRFD-001to be reviewedTestable 0 0 As a minimal requirement, the Form Filler shall be able to display, complete and submit the form.168Section 17.1.3.21/29/19 2:23:58 PM by jlabbe
RFDRFD-002to be reviewedTestable 0 0 The profile makes suggestions about storing partially completed forms but provides no guidance on how to do this.168Section 17.1.4.11/29/19 2:23:47 PM by jlabbe
RFDRFD-003to be reviewedTestable 0 0 Form Filler may initiate requests for data clarification. When the Form Filler initiates a request, the Form Filler responds with one or more items.171Section 17.1.61/29/19 2:23:47 PM by jlabbe
RFDRFD-004to be reviewedTestable 0 0 A Form Manager may return a form instance id along with a form in response to retrieve a form.173Section 17.2.1.11/29/19 2:23:58 PM by jlabbe
RFDRFD-005to be reviewedTestable 0 0 The Form Manager shall be able to construct a form such that the data is sent to an external Form Receiver. That is, a Form Manager cannot merely construct a form to send data to itself.173Section 17.2.1.11/29/19 2:23:58 PM by jlabbe
RFDRFD-006to be reviewedTestable 0 0 The Form Filler Actor retrieves forms from a Form Manager as and when required.173Section 17.2.1.21/29/19 2:23:47 PM by jlabbe
RFDRFD-007to be reviewedTestable 0 0 When requesting a form, the Form Filler Actor can optionally provide EHR context information by providing pre-population xml data in the request for use by the Form Manager, as well as workflow data that may be used to facilitate form selection.173Section 17.2.1.21/29/19 2:23:47 PM by jlabbe
RFDRFD-008to be reviewedTestable 0 0 A form instance id may be provided to identify use of previously submitted data.173Section 17.2.1.21/29/19 2:23:58 PM by jlabbe
RFDRFD-009to be reviewedTestable 0 0 The Form Filler may also specify a Form Archiver Actor. The Form Archiver Actor specified by the Form Filler is in addition to any Form Archiver actors specified by the Form Manager.173Section 17.2.1.21/29/19 2:23:47 PM by jlabbe
RFDRFD-010to be reviewedTestable 0 0 The Form Receiver Actor receives and processes completed or partially completed forms instance data from a Form Filler. Form Receiver processing is out of the scope of the profile.173Section 17.2.1.31/29/19 2:23:47 PM by jlabbe
RFDRFD-011to be reviewedTestable 0 0 The Form Archiver Actor receives completed or partially completed forms instance data and stores these for archival purposes.173Section 17.2.1.41/29/19 2:23:58 PM by jlabbe
RFDRFD-012to be reviewedTestable 0 0 The Form Processor is an integrated Form Manager and Form Receiver, supporting all of the transactions and options of those actors.173Section 17.2.1.51/29/19 2:23:47 PM by jlabbe
RFDRFD-013to be reviewedTestable 0 0 The Form Processor constructs forms such that form data is submitted back to itself.173Section 17.2.1.51/29/19 2:23:58 PM by jlabbe
RFDRFD-014to be reviewedTestable 0 0 Assignment of form identifiers is not profiled and is assumed to take place as a part of the setup configuration process necessary between Form Fillers and Form Managers, or Form Processors.174Section 17.2.2.11/29/19 2:23:47 PM by jlabbe
RFDRFD-015to be reviewedTestable 0 0 The Retrieve Clarifications transaction allows a Form Filler to request the set of clarifications for a given organization from a Form Manager, or Form Processor. The value of the assigned organization identifier determines the named option format of the clarifications form. Assignment of organization identifiers is not profiled and is assumed to take place as a part of the setup configuration process between Form Fillers and Form Managers.174Section 17.2.2.41/29/19 2:23:58 PM by jlabbe
RFDRFD-016to be reviewedTestable 0 0 The Form Filler makes a Retrieve Form request to a Form Manager. The Form Manager either returns the requested form or an error indicating no form is available.175Section 17.41/29/19 2:23:58 PM by jlabbe
RFDRFD-017to be reviewedTestable 0 0 The action upon submit is controlled by the form, hence the Form Manager is responsible for defining the post-submit action by selection of, or generation of, the desired action during the Retrieve Form transaction processing.175Section 17.41/29/19 2:23:58 PM by jlabbe
RFDRFD-018to be reviewedTestable 0 0 The Form Manager constructs the form to perform an archive transaction to the Form Archiver specified in the Form Filler’s Retrieve Form request. When the form is returned and subsequently submitted, form instance data is submitted to the Form Receiver and also to the Form Archiver.175Section 17.41/29/19 2:23:47 PM by jlabbe
RFDRFD-019to be reviewedTestable 0 0 This case illustrates one way to use Form design to solve the issue where a formID is not known in advance. The identifier of a form, the formID, is not known to the Form Filler, but a set of context value (name, value) pairs is known. A context form where these values could be entered would have a formID. Information collected by the instance of a context form would be used by the Form Manager to determine the appropriate data capture form to return to the Form Filler. The Form Filler has enough information to request a context form that collects information that can help the Form Manager determine the actual data capture form. The Form Filler completes the context form, submits this to the Form Receiver which returns either new instance data, or a new form.175Section 17.41/29/19 2:23:47 PM by jlabbe
RFDRFD-020to be reviewedTestable 0 0 These Retrieve Clarifications requests must be periodically executed by the Form Filler. The frequency of request is likely based upon some duration as defined or agreed upon by the Form Manager / Form Receiver.175Section 17.41/29/19 2:23:58 PM by jlabbe