Eloquence applications

Overview
• The EncaptureMD Core
• Modality Applications
• Support Applications
• Sharing Data

Modality Applications
• Echocardiography
• Nuclear cardiology
• Electrophysiology
• Cardiac catheterization
• Vascular

Use any one of our reporting applications, modify them to better fit your needs or
create a new report from scratch.

EncaptureMD comes standard with many reporting modalities. We call each one an application. They are much like the applications that run on your computer, except that they all work together to gather information, create reports, maintain inventory, keep track of ordering physicians, handle billing and much more.

The EncaptureMD Core

Core Functions are common to all applications that deal directly with patient data. Patient information can be entered directly through the core, or, more commonly, through interaction with modality specific applications, such as echocardiography or interventional radiology.

Core functions are shared so that one patient can have many procedures performed and Eloquence will know the results of all of them, know who ordered them and who received reports, and even know their billing status. Your application's results are made immediately available to registered web users as well.

your application

Modality Applications

Modality Applications manage information and create reports specific to one procedure or one area of medicine. They provide a common interface to allow the user to quickly enter data and generate concise reports. See the list to the left for more details.

Support Applications

Support Applications do not directly interface with patient data. Instead, they provide inventory, tracking and support to modality specific applications. Pharmacy, catheter inventory, equipment maintenance records are all support applications.

Sharing Data

One of the most powerful features of EncaptureMD is the ability to share data between applications. Different types of sharing are possible and the ability to share data between applications is controlled.

1) "I have an application, but I need to comment on the same thing multiple times". An example would be a procedure where multiple drugs are given at different doses and different intervals. In this case, data is created in your application and stored in the pharm application.

pharm

The new Pharm application allows you to keep track of all drug doses given during a procedure and include a drug schedule in your procedure's final report. You can even share the Pharm application with other Modality applications.

2) "My procedure uses catheters, which I take out of inventory". In this case, you am consuming a resource that must be accounted for in inventory. Your procedure may use one catheter or a dozen. In this case, catheter inventory is managed by the catheter application. When a catheter is used by your application, it cannot be used again.

cath app

Your modality application knows which catheters were used during any procedure and your catheter application knows which catheters were used in all procedures, even if you share your catheter application among different procedure/modality applications.

3) "I need to know the names of all the doctors who see the patient undergoing the procedure AND I want to know how many patients each of my referring physicians is sending me". A patient has many doctors AND a doctor has many patients.

ref app

Relationships like these are not limited to two applications. The catheter table could be shared between, for example, interventional Radiology, Interventional Cardiology, and Electrophysiology. The patient and referring relationship is tied to all patient-based modality applications and can be used throughout your group or hospital system.