Overview
The Clinical Documentation Solution Accelerator (CDSA) for the Microsoft Office system is a Connected Health Platform resource that enables you or your customer to define and create clinically encoded documents. Documents can be created based upon ready-made templates (for example, for a Discharge Summary or a Referral) retrieved using the Microsoft Office System.
Key Benefits for Your Organization
Users employ the already familiar Microsoft Office Word interface to complete documents that are yet readable by both people and systems
CDSA supports rapid development of a range of clinical documents that readily match those currently in use by clinicians and end-users
Look up, verify and encode your data (such as clinical terms or medications) by background reference to online services
Use existing e-mail and middleware systems to send documents, sharing data between primary care and hospital and acute care clinicians and communicating with the patient
Uses MSCUI Controls to Encode Clinical Information
CDSA promotes the safety and consistency of clinical documentation by utilizing Microsoft Health Common User Interface software toolkit components. Those components support the embedding of structured, machine-readable clinical information in a human-readable Microsoft Office document shareable across care boundaries. The encoding of clinical information is to industry standard formats (such as the Health Level 7 (HL7) Clinical Document Architecture (CDA)).
Built for External Data Sources
This resource demonstrates the direct utilization of external clinical data (perhaps from a cloud platform or Windows Azure source) in a document. Example external data sources include Systematized Nomenclature of Medicine Clinical Terms (SNOMED CT®) encoding services or drug reference data. This enables a powerful editing experience, specific to the healthcare domain but easy to use because it offers familiar, industry-leading authoring tools, such as Microsoft Office Word 2007 or Microsoft Office Word 2010.
Integrate with Your Existing IT Systems
You can use CDSA as the foundation for clinical document workflows (for example, in combination with Microsoft Office SharePoint Server 2010). Tailor those to the specific Electronic Medical Record (EMR) or Electronic Health Record (EHR) systems in your own or your customer's healthcare environment. In addition, CDSA will enable you to create clinical documents suitable for upload to a Personal Health Record (PHR) system (such as Microsoft HealthVault) or to other external storage.
Easily Create Clinical Templates
Template designers can create Office Word templates, allowing the data entered in the document to be mapped to a machine-readable representation using clinical encoding taxonomies (such as SNOMED CT®). This is in addition to providing a human-readable version of the document.
Easily Create Clinical Documents
Clinicians can complete clinical forms created from a CDSA-enabled Office Word template. The Office Word (.docx) file contains both human-readable and machine-readable clinical information (such as a HL7 CDA representation).
Share Clinical Documents Across Care Boundaries
Even without the need for the CDSA add-in, a recipient can read the clinical document. The document .docx file still contains the machine-readable clinical information and this can be extracted and uploaded to an external clinical system. It is easy to share clinical documents created using the CDSA, passing them across care boundaries whilst retaining the clinically encoded data.
Clinical Documentation Solution Accelerator Source Package (Zip file) including
One of the following operating systems:
The following applications:
Download Developer Videos
|
Developer Overview
This video provides an introduction to the template development features provided
by the CDSA add-in.
Constructing a template using existing controls
Building a new clinical document template using the controls provided with the CDSA
add-in.
Creating a simple control
How to create a new CDSA control using Microsoft Word content controls which can
then be re-used across your clinical templates.
|
Customizing the layout of an existing control
How to customize the appearance and layout of a control provided with the CDSA add-in,
to meet your own template requirements.
Creating Rich-editing experiences using WPF based controls
How to use controls implemented in WPF to extend and enhance the editing experience
for users completing documents.
Creating a WPF based list control
How to use your WPF based control to create a CDSA control for populating lists
of information.
|
Mapping your document data to a Custom XML format
How to take the data which has been entered and mapping that information into a
custom storage format (such as HL7 CDA) for interchange with other IT systems.
Prepopulating your document with data from another system
How to programmatically prepopulate sections of your clinical document with information you already hold.
|
|
Microsoft would like to thank the following companies for their support in the production of the Clinical Documentation Solution Accelerator. |
|||
|
|
|
|