09.11.2012 Views

Pediatric Informatics: Computer Applications in Child Health (Health ...

Pediatric Informatics: Computer Applications in Child Health (Health ...

Pediatric Informatics: Computer Applications in Child Health (Health ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

16 Prioritiz<strong>in</strong>g <strong>Pediatric</strong> Investment for IT <strong>in</strong> Smaller Practices 229<br />

Other cont<strong>in</strong>gencies that must be planned <strong>in</strong>clude prolonged downtime (How does<br />

the practice operate when the system is nonoperational?) and recovery (How is<br />

data from downtime restored to the system? How is data loss or theft handled?).<br />

Practices must have a clear idea about how support will respond either to rout<strong>in</strong>e or<br />

urgent requests. Are they fast and dependable? Communication with previous users<br />

is essential because vendor promises might not be reliable.<br />

16.4.5.3 Ma<strong>in</strong>tenance<br />

In a paperless pediatric office the electronic data repository will be the life blood of<br />

the practice and it must be ma<strong>in</strong>ta<strong>in</strong>ed. Information must be backed up on a regular<br />

basis. Technologies to automate this process <strong>in</strong>clude tapes, redundant hard drives,<br />

optical disks, etc. have been <strong>in</strong> use for practice management systems and can be<br />

applied to EHRs. This task can also be entrusted to an Application Service Provider<br />

to store data securely off site.<br />

Most systems <strong>in</strong>corporate regular backup process<strong>in</strong>g to multiple locations to<br />

provide redundancy. Assurance of the restoration (and retrieval) process, while the<br />

responsibility of the practice, requires guidance from vendors and purchasers should<br />

look for guarantees of rapid response <strong>in</strong> case of an emergencies. No office should be<br />

placed <strong>in</strong>to the position of hav<strong>in</strong>g to manage a restoration without help available.<br />

Downtime policies for staff should be <strong>in</strong> place <strong>in</strong> case of a failure (system failure,<br />

power outage, misplaced record). This <strong>in</strong>cludes a mechanism to create a temporary<br />

record until updat<strong>in</strong>g the electronic systems can be restored and re<strong>in</strong>corporat<strong>in</strong>g<br />

<strong>in</strong>terim records <strong>in</strong>to the ma<strong>in</strong> system. These policies and procedures should be<br />

reviewed periodically by the practice.<br />

System updates and repairs should be considered as part of service contracts for<br />

workstations, servers and other hardware. Upgrades should be considered <strong>in</strong> terms<br />

of compatibilities with other components of the system (operat<strong>in</strong>g system, network<br />

connection, control devices, and any system that cannot be updated easily should<br />

be questioned (as it may <strong>in</strong>cur additional costs and upgrades).<br />

16.4.6 Expenses – Nonmonetary<br />

Important questions to ask about cont<strong>in</strong>gency procedures <strong>in</strong>volve how data (or lack<br />

of data) is handled when the system does not function optimally.<br />

16.4.6.1 Confidentiality and Security<br />

What happens if <strong>in</strong>formation security is compromised (stolen or lost) due to any<br />

cause (malicious or otherwise)? What are ways of mitigat<strong>in</strong>g this compromise<br />

and its effects on care? What are the disclosure requirements and procedures as

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!