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 225<br />

16.3.2.2 Costs to Customize Products<br />

Small practice decision makers must decide if “commercial off-the-shelf (COTS)”<br />

technology will meet practice needs or if customization is required. Customization<br />

may range from “built-<strong>in</strong>” specification of forms (low cost) to changes <strong>in</strong> the<br />

underly<strong>in</strong>g data structures that require technologist <strong>in</strong>tervention (high cost). In<br />

addition, practices need to determ<strong>in</strong>e the frequency of customization updates and<br />

how these will <strong>in</strong>cur further costs.<br />

16.3.2.3 Costs to Interface/Integrate Systems<br />

In the same manner, practices must decide if “standalone” products will meet needs<br />

of if they must connect to other systems (and on what basis). Interface/<strong>in</strong>tegration<br />

considerations <strong>in</strong>clude the costs of <strong>in</strong>terfaces (and functionalities) of an EHR to:<br />

Practice cost centers or management system<br />

Different office locations (and home/mobile)<br />

Commercial laboratory and imag<strong>in</strong>g services<br />

New entities (How much will it cost to modify current <strong>in</strong>terfaces)<br />

The most useful <strong>in</strong>terface is between cl<strong>in</strong>ical <strong>in</strong>formation tools (such as EHRs and<br />

eRx) to practice management systems to <strong>in</strong>tegrate cl<strong>in</strong>ical <strong>in</strong>formation with bill<strong>in</strong>g<br />

and schedul<strong>in</strong>g functions. Interfaces that connect products from different vendors<br />

to form value-added <strong>in</strong>tegrated suites are available. Challenges to practices <strong>in</strong>clude<br />

decisions on how to transition from current management systems while m<strong>in</strong>imiz<strong>in</strong>g<br />

costs of productivity loss and retra<strong>in</strong><strong>in</strong>g of staff. Transitions may require operation<br />

of more than one system.<br />

16.3.2.4 Upgrade Costs<br />

Proprietary and customized systems are vulnerable to discont<strong>in</strong>uation by their<br />

vendors. Contractual negotiations with vendors should <strong>in</strong>clude cont<strong>in</strong>gency plans<br />

for cont<strong>in</strong>ued service, <strong>in</strong>clud<strong>in</strong>g if needed, availability of code or <strong>in</strong>terfaces for<br />

modification. All hardware and software have a life span and upgrades may <strong>in</strong>clude<br />

major changes, with accompany<strong>in</strong>g costs. Tools are available that can help a provider<br />

look at <strong>in</strong>dividual pieces or the cost breakdown. 11<br />

16.4 Plann<strong>in</strong>g IT Adoption<br />

16.4.1 The Steps<br />

The steps <strong>in</strong> plann<strong>in</strong>g adoption for small practices may be less formal than for<br />

larger ones. These <strong>in</strong>clude:

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

Saved successfully!

Ooh no, something went wrong!