Welcome Guest, Login
Image
RSS RSS

Navigation


Quick Search
»



Page History: Importing data into CAREWare

Compare Page Revisions



« Older Revision - Back to Page History - Newer Revision »


Page Revision: Thu, 04 Dec 2014 12:27


There are a number of ways to import data into CAREWare available to users. These import processes can be quite complicated for novice users and we have gathered together all of the available documentation here for each import process. These documents will allow users to create the data file and complete the import successfully. Each of the available import methods is described below in brief.

Provider Data Import (PDI)

The Provider Data Import (PDI) allows users to import their clinical data from other electronic health record applications into CAREWare using a pre-defined Access template. The Access template for ease of use when converting the third party data into CAREWare. Once the data is ready to be imported a user will map all incoming fields with the associated CAREWare fields, then allow the PDI to complete the import.

The PDI template can download from here.

All PDI data fields are outlined in the Provider Data Import - Specifications document.

The PDI data entry rules can be reviewed in the Provider Data Import - Data Entry Rules document.

A user can follow the steps to complete the import using the PDI with the PDI User Manual.

Many users want to import data via the PDI into CAREWare for reporting purposes. We have created the following documents for this purpose. These documents identify the PDI fields that hold the report and question specific fields for the necessary incoming data.

The PDI-Peformance Measure Field Map details all PDI fields with the corresponding CAREWare elements for use by the HAB Performance Measures within CAREWare.

The PDI-Performance Measure Element Map details all the CAREWare field selections used to create the HAB Performance Measures by individual performance measure. Each measure is broken apart to its base field selections and PDI and user data used for individual field selection.

The PDI-RSR Field Map details all fields in use on the RSR and the necessary field to use within the PDI template.

HL7

HL7 is a standardized framework for exchanging, integrating, retrieving, and sharing electronic health information. This framework provides the ability to exchange several different types of clinical data. The CAREWare HL7 import allows for importing such clinical data as hospital admissions, diagnoses, tests, and appointments.

The use of the HL7 Socket to import clinical data allows users to automatically import data as the HL7 file is placed within the per-defined location on the central server. Prior to the first successful import of the HL7 data a user must map all incoming fields to existing fields within CAREWare.

More information regarding the overall architecture of the HL7 Socket interface please review the HL7 Socket Tech document.

More information regarding the HL7 Socket installation can be found in the HL7 Socket Installation document.

To see all RSR fields available for import using the HL7 Socket Interface please review the HL7 Options for RSR Fields document.

The CAREWare Feature Explorer also provides a brief overview of the HL7 Socket Interface.

Data Translation Module

The Data Translation Module is a utility designed to parse flat text files in a CSV format, or Excel files, and create an Access database template file that can be easily imported into CAREWare through the Provider Data Import (PDI). After required configuration and mapping processes are complete, this utility can be automated and will look for incoming files in a specified folder.

You can learn more about the Data Translator Module and download the utility at the Data Translation Module page.



Store & Forward

Store & Forward (S&F) allows CAREWare users to securely transfer all clinical data between separate instances of CAREWare. Store & Forward can be used to centralize the warehousing of remote sites to one centralized database for easier client tracking and reporting. It also allows for continuous, incremental updating so exports can be done over time without the need for re-exporting the same data each time.

Store & Forward requires setup on both the central server and the remote site in order for it work properly. The Store & Forward Instructions provide the clearest picture of how to properly set it up for first time use.

Back to Administration

Back to Frequently Asked Questions

jProg is a registered trademark of Jeff Murray's Programming Shop, Inc. All other products mentioned are registered trademarks or trademarks of their respective companies. Questions or problems regarding this web site should be directed to JeffMurray@jprog.com.

© 1998- Jeff Murray's Programming Shop, Inc. (jProg) , all rights reserved.