Reference no: EM132340763

Assignment - Brainstorming for Systems Solutions

Dr. Frost, Dr. Summer, and Dr. Mansfield work together in a group practice. They share scheduling, coding and billing staff.

However, the doctors sometimes have different ideas on how things should be done. When Dr. Mansfield sees a patient for a breast biopsy, she knows that she will spend 1.25 hours with that patient and will bill $750 for the procedure. Then she will need a 20-minute break between patients to prepare specimen right away for pathology. She does not want any deviation from this.

Dr. Summer is a dermatologist who sees patients with varying degrees of skin lesions needing removal. Until it's over, he wants to keep options open about the coding and billing, even the length of time the patient might take.

Dr. Frost, our third doctor, is open to seeing patients who need lengthy consultations, except on Thursday afternoons. On Thursdays, he has to pick up his daughter at 2:00 pm. When staff schedule a complicated case they need to make sure it is not for Thursday afternoon. Office staff members are tired of using post-it notes on the desk to remind themselves of these different needs.

Your task: Write a 1-2 page paper that answers the following:

1. Do you think these varying needs would be challenging for a scheduling system? Why or why not?

2. What sort of alerts or reminders would you put into their system(s)?

3. Brainstorm 4-5 solutions and issues for dealing with these various needs.

Module - Lesson Content

Feasibility Studies

This module provides an overview of planning for information systems needs, from the top levels. First, we consider what the organization can or should do in terms of information systems purchase. What problems or issues need to be solved? Have specific goals been set to reduce medical errors and to contain costs of care?

When considering and developing new systems, management considers overall organizational goals.

For example, an electronic prescribing system is supposed to reduce the level of prescription errors in transcribing and administration.

A hospital or clinic transforming from paper-based to electronic prescribing needs to consider the following issues:

• Does the technology exist for sending remote prescriptions to the pharmacy, efficiently and securely?
• Does this institution have the electronic infrastructure needed to support such a system? What changes would be needed?
• Do the major managers in the institution support such a move? Will the chief medical officer, chief operating officer, and pharmacy department director support this change? If not, why not?
• What other questions or issues should be considered, to evaluate making the move to electronic prescribing?

Needs Analysis

In the Needs Analysis phase, the institution considers what the system needs to accomplish.

Interviews with key departments and managers should be conducted to clarify expectations and requirements.

On a general level, requirements for the system include items such as:

• The system will provide timely computerized transfer of all prescription information to the pharmacies involved. Timely transfer is defined as within xx minutes of order entry.
• The system will adhere to all applicable state and federal regulations.
• The system must include privacy and security features.
• The system requires a backup plan in case of network outages.

All staff will be trained to use the system and be up-to-speed on functions within three weeks of implementation.

These provide examples of general, systems-level goals and needs. Once the general needs have been signed off and agreed upon, the process of writing systems specifications ensues.

As a practical matter, the general needs and detailed specifications might be defined simultaneously, instead.

A Requirements Analysis and Systems Specifications Go Hand-in-Hand

A software requirements specification (SRS) is a comprehensive description of the intended purpose and environment for software under development. The SRS fully describes what the software will do and how it will be expected to perform.

Bitpipe.com, (n.d.) In Bitpipe.com. Retrieved on January 2, 2011.

Systems Cost and Assessing Vendor Capabilities

Some reports make the transition to electronic health records look straightforward, even enjoyable. However, some physicians have difficulty justifying costs and making changes needed for adapting to the EHR. How can system capability and costs be determined?

Specifying the system needs and features first, will help in developing a checklist against which to compare systems capabilities. By interviewing the system's key users on how their work is accomplished, a list begins for system needs and unique capabilities.

Is it necessary to have remote access to an EHR after hours? If so, that need should be made known. The systems selectors and vendors will need such information.

Vendors will want to give product demonstrations. Vendors often present features in the order they specify.

However, starting from the user's need list, and asking the vendor to show the part of the system that meets that need and specifications, will put the burden back on the vendor to demonstrate capability.

Costs

Costs for the system need to include all costs including its design or customization, installation, training of users, and ongoing maintenance and backups.

Some systems are purchased via a license granted for a given time period. Others may be leased on a month-to-month (or longer term) basis.

Where will the data be stored? Some systems require the hospital or practice to purchase and maintain servers. The staff needed to administer and maintain server capacity and security are another cost. Other systems for a physician office level may have server space available remotely, and associated maintenance tasks will happen out-of-sight.

A back-up scheduled every 24 hours will ensure that no more than a day's work would need to be re-entered.

Staff who have not used computers extensively in the past may fear that they will wipe out needed data on the system. It is likely that more errors will occur during system startup than at any other time.