|
|
- How does the system work?
The NTTC utilizes an Application Service Provider (ASP) model, which means the NTTC hosts, manages, and delivers applications to multiple entities (users) from a remote data center across a wide area network (Internet).
- What is the benefit of the ASP model?
- ASPs require no client-side software beyond a current Web browser.
- Clients can access their information from virtually anywhere in the world.
- Client system-administration costs and additional staffing requirements are eliminated.
- ASPs leverage the cost benefits of the Internet without compromising security.
- What does the clinic provide?
The participating clinic provides patient and appointment data and access to the billing system (such as Medical Manager).
- What reports are generated for chart audits, and is that compared to a national average for benchmarking?
A Coder report functionality is available, which is an aggregation/consolidation of all notes, in a list form, for centralized chart review. Access to this report is role-based, limiting access to only those who legitimately need it.
- Who will enter all the information? Does it occur at points of care or by different departments?
Can be done either way. Depends on the clinic's preference.
- How long will it take this information to become part of the record?
Information is entered in real-time and will be available immediately.
- How would we prepare for the days schedule? Would we download the records or would we access as needed?
The system requires an interface with the patient administration system to get patient data, appointment data, clinic data and provider data. The download parameters and preparation time depends upon the data source and type of interface.
- Is there much Internet time involved? Can more than one user access the system?
All screens are dependent on the Internet for display. System performance is directly related to the internal network and Internet performance (speed and capacity). Multiple providers can access the system at the same time.
- How is patient data accessed -- by numbers or names of patients? How does this happen when the physician is accessing from the hospital?
The system receives patient information, including names and ID numbers, from the clinic’s core patient registration system. Access to these records is Web- and role-based. In theory, a physician who is authorized to use the system can access the Internet and generate a note on the patient from anywhere. It is, therefore, possible to generate a note for a patient who is hospitalized, provided that patient is in the clinic’s registration system.
- How do we access patient history?
If the history data is entered (either manually into the record or as a scanned document), it will be viewable in the system.
- What are the security issues if physicians can access data from outside locations?
The Web site is secure and no data is locally cached by the system. The only way to store data on a local machine is through a user's deliberate screen capture or other activity outside of the scope of the system's core functionality (this is a potential security issue). The Web site can be accessed from outside the clinic network if configured to do so. Data can be accessed from home if local policy supports such.
|