Clinical Data Forms are the primary channel for capturing information in the healthcare and clinical domain. Forms also play a key role in information exchange and are critical to supporting interoperability in healthcare.
A form differs from a document in that the structure of the form is designed to incorporate skip patterns, validation rules, and other aspects required to capture the clinical data while the document takes that data and structures it in a meaningful way that reflects the clinical activity and the associated syntactical representation necessary to maintain the flow that clinical activity.
A document in this context is specifically a clinical document which represents information about a clinical activity. The document contains the specific information obtained during that clinical activity and supports the broader definitions of a document. Documents can be transformed into human readable forms, and be transferred or transmitted for use across different systems.
The key forms capabilities include:
- Tools and services for defining form templates
- Ability to leverage models and reusable segments for defining these forms
- User friendly tools that hide the complexity of the underlying semantics The capabilities listed above are derived from the following use cases:
- caBIG® Clinical Information Suite
- ONC and Other external EHR adopters
- Clinical Trials
Functional Profile Group
- 5.2.3.1 - Administer Forms Sept. 6, 2010
- 5.2.3.1.1 - Manage Models and Reusable Segments Sept. 6, 2010 Manage models and reusable segments used to design Clinical Data Form Definitions.
- 5.2.3.2 - Create Forms Sept. 6, 2010 Tools and services for defining form templates.
- 5.2.3.2.1 - Form Definitions Sept. 6, 2010 Form Definitions
- 5.2.3.2.2 - Form Templates Sept. 6, 2010 Form Templates
