Therapeias believes that simplicity of design inherently provides the flexibility and power of TheraScan in clinical implementations.
Table-driven logic dynamically builds the data entry elements that accompany document uploads. This metadata is stored in an XML format that allows for easy queries of the data using standard SQL commands.
Thus the content of the metadata drives the sorting, viewing and accession of documents throughout the system.
As documents are loaded into the system, the user certifies that the stored document is an accurate representation of the original.
TheraScan users can build documents from a wide variety of sources. As an example: PDFs can be created from a combination of scanned images, photos, image files and screen captures. This allows for the clinic staff to aggregate source documents from scanned paper CRFs, EHR screen captures, photos and image files to support data entered into a visit record in the CTMS.
All file types can be loaded and certified in TheraScan.
Every time a file is viewed, the system verifies that it has not changed since being uploaded. All viewing is logged by the system with the username and timestamp.
Those file types that have a native web viewer, like PDF, image, audio or video are the most elegantly handled as they appear within a TheraScan viewing window. However any type of document; which can include DICOM images, word processing documents or spreadsheets; can still be downloaded and accessed in a local application.
TheraScan also supports the uploading and accessing of documents from third-party application via an API. This is accomplished via an HTML-compliant RESTful interface.
Physically, source documents are kept in a repository server. While logically separate, this server typically operates on shared hardware in the TheraScan data center. Clients can opt to have this repository on their own equipment or virtual server. Documents are only accessible via the repository web server. There is no direct database access.
Records pertaining the creation and viewing of documents are kept on the TheraScan certification server. This server also contains keys that when coupled with both user-entered values and keys in the repository server allow for the decryption of the source documents. No Protected Health Information (PHI) is stored on the certification server.
· · ·