Does your IT plan include the management of legacy data?
When implementing a new system, legacy data should be kept accessible to
meet regulatory requirements (7-10 years)
respond to patient or legal inquiries
support claims collection and audit activities
Why secure your historical patient information?
Typically, only demographic and some financial information is converted to a new system. That leaves plenty of vital patient detail left behind in the legacy practice management application. State and federal regulations mandate that patient information is securely retained for the next 7-10 years. Check with your attorney on your state’s medical record retention requirements, or, check your state medical society web page or the AHIMA website for more information.
How are you securing your legacy patient data?
While one option for meeting the requirements is to keep your aging practice management server up and running, keep staff educated over the next decade on how to login, and continue to pay for application support – that gets both costly and risky. Don’t simply push that practice management server under a desk and expect it, the Unix operating system and the application to work perfectly when you need it most!
How do we secure your legacy patient data?
Data from the practice management software is converted from its architecture into a relational Microsoft® SQL database. That new database, which maintains full data integrity, can then yield a variety of outputs. One output option is account-level profile sheets in searchable portable data format, or PDF.
The universally-accepted PDF output is indexed to a web browser and searchable by account number, name, social security number, date of birth, or dataset. Each patient profile sheet is then categorically bookmarked for quick and easy access by any staff member – even those not trained on how to use the practice management system.
Health Data Archiver Product Features
Access, print and redact patient profile sheets from anywhere
Respond to audit and legal inquiries with full data integrity
Retire hardware infrastructure to support legacy system
Eliminate support of an aging operating system and application
Eliminate need for application expertise by an administrator
Access information without application training or competency
Integrate legacy data into normal day-to-day IT administration
Meet HIPAA requirements for patient information storage
System Requirements
Hosted on a local server with
Windows 2003/2008
IIS V or IIS VI
.NET Frame 2.0
SQL 2005/2008
Required Disk Drive Space varies based on data volume
