This section will address prototypes and demos and includes the following:
Scope, Objectives and Approach
The caBIG® Clinical Information Suite Clinical Forms prototype has two primary goals. The first goal involves a form designer and the construction of a clinical data entry form for use in the graphical user interface of the caBIG® Clinical Information Suite application that is semantically consistent and based on HL7 RIM objects, HL7 structural vocabulary, and ONC required code systems for meaningful use. The second goal involves the data entry person (a physician, nurse or other health care provider) who defines the value set requirements for the form elements, identifies the rules for skip patterns and form element arrangement, and eventually enters and persists clinical data.
Capability Description
The prototype will support the following core capabilities:
- Create Form Definitions
- Retrieve form Objects
- Persist CDA Document
Requirements
The following is a description of the use case that will be realized by the prototype:
Element |
Description |
---|---|
Use Case Name |
caBIG® Clinical Information Suite Form Development |
Use Case Unique ID |
--- |
caBIG® Clinical Information Suite Enterprise Use Case Ref. ID |
--- |
Brief Description |
A qualified form builder designs a form for use in caBIG® Clinical Information Suite |
Actors |
Data Entry Form builder, Data Entry Form end user |
Trigger |
Data Entry Form end user requests a new form |
Preconditions |
|
Main Flow |
|
Alternate Flow |
--- |
Postconditions |
A Semantically Aware Form is available for use in the caBIG® Clinical Information Suite |
Notes |
The use case assumes that the caBIG® Clinical Information Suite applications have the responsibility for binding of the form to system middleware components |
Community Feedback and Comments
TBD
Lessons Learned
TBD