| Project: | TAPAS |
|---|---|
| Internal Release Number: | 0.0.1 |
| Attached worksheets: |
SRS > Use case suite
SRS > Feature set
|
| Related Documents: |
The first release of TAPAS will be a virtual practice server that supports several core functions to support the delivery of primary care. These include:
TAPAS it will support the e-MS standard, in terms of clinical data and in the creation, exporting, and importing of the e-MS CDA document. It will not, in this version, support the transport protocol of e-MS.
The practice server will connect to a number of clients through a Java based rich user interface on the desktop (which will require an online connection to the server to access patient data) and a PDA wireless sync interface for PalmOS PDAs.
For more information, see the project proposal.
The use case suite for this
project collects the core functions,
both clinical and administrative for the practice. The following
diagram shows all use cases and their interaction with actors:
The system should support practices in a way that (a) improves practice and (b) speeds up practice where ever possible.
Workflows for TAPAS-supported tasks have to support real world office work. While workflows will look at current practice, the system will diverge from current paper practices where suitable in order to reduce duplication of effort, streamline communication, and provide more information.
The user interface should be as familiar as possible to clinicians and office assistants who have a basic understanding of computers. Standardized UI elements will be used where ever possible and consistent workflows and paradigms will be developed to support learning.
Care is delivered by family physicians 24/7. While no system can be maintained live 24/7, we want our system to provide 99.9% uptime.
The data housed in the system is important medical data. Thousands of patient summaries will be held. The reliability and integrity of that data will be critical. Design must consider integretity of data over performance where ever necessary.
The system, if there is a failure, must degenerate gracefully, ensuring data integrety.
The development group will have a defined process for upgrading the system and adding new modules. It is foreseeable that new modules would be requested by different groups exploring and learning about quality improvement through technology assistance and, therefore, a clear path to how new clinical modules may be created and integrated will be key. For example, a group may want to develop a module to support improved care of addictions patients. An integration pathway would need to be provided to allow groups to collaborate and contribute their modules to the TAPAS system.
User groups should have the ability to select and incorporate new modules and updates into their existing system with no loss to the integrity of the existing clinical data. Data should contain sufficient meta data to ensure integrity. Updates to the PDA and the server should be available remotely, to reduce the cost of providing updates.
Our envisioned goal for support is to provide a suite of tools and documentation that will allow other groups to provide runtime support. Deployment of TAPAS tools may occur through the embedding of those tools inside an existing service provider's infrastructure: eg through an existing billing program or by integrating some components (such as the PDA summary tools) into an existing EMR platform. Through this model, we will support the current infrastructure, provide a functional sustainability plan, while allow our team to focus resources on development of future modules.
The product features and choice of robust, tested open source technologies should help us achieve our goal of 99.9% uptime (at most 43 minutes downtime each month). Key features supporting that are the ability to do hot data backups, and application monitoring.
The TAPAS medical summary server must allow import and export of medical summaries of all patients in the form of standardized e-MS CDA documents that can be imported into an EMR system. Data import / export must occur by individual patient and in batches. Exporting of patient data needs to be by physicians and by the entire clinic.