Data timeliness and completeness

Can VennU access EHR data in real time?
Yes. VennU enables you to access electronic health record (EHR) data in real time. Only the speed of your network can slow you down.

Can VennU be used to access data on demand?
Yes. VennU gives you access to any authorized data in the EHR whenever you need it. You no longer need to pull and store data. VennU retrieves the data when you want it, with no lags.

Can VennU access historical EHR data?
Yes, VennU provides access to historical data on demand. VennU also has an asynchronous mode you can use to access data for large populations. VennU processes the data offline and notifies you when your results are ready.

Can I access any EHR data with VennU? Are there limits to the data model, like there are with FHIR and HL7?
Unlike FHIR, HL7, or other API vendors, VennU enables access to any and all EHR data. The only limits to data access are healthcare system authorizations, and you can write as many queries of any type as you want. With VennU, there are no boundaries to your creativity.

Data security and performance

How does VennU protect data privacy and security?
VennU enables data privacy with zero data persistence, end-to-end encryption, and configurable audit settings. It also ensures data security by giving the healthcare system exclusive, field-level control over data access. No user of VennU can access data without approval by the healthcare system.

Does VennU affect the performance of the EHR?
No. VennU eliminates any adverse effect on performance by enabling healthcare systems to manage resources through configurable throttling, asynchronous processing, and process monitoring and management.

What happens if the data change in the EHR? Will my VennU APIs break?
VennU stays in sync with the EHR through proactive schema change detection and data quality rules. VennU also uses algorithms to detect data content changes1 and notifies application owners about changes relevant to them.

Data sources

Which EHR vendors does VennU work with?
Currently, VennU can access data from Epic and Cerner EHRs.

Will Medcurio develop versions of VennU for other EHR vendors?
We are not currently developing a version of VennU for other EHR vendors, but we will prioritize other vendors depending on market need.

Can VennU access data from sources other than EHRs?
Yes. Through our professional services, we can provide custom integration to other data sources, such as PDFs, images, audio, and other types of files.

Data scalability

How does VennU create APIs?
VennU enables analysts to create APIs using a graphical user interface. As you select fields, VennU automatically creates APIs that can be called by approved applications.

Can the APIs be reused at other sites?
The APIs can be exported and used with other instances of the same EHR. You can easily modify them to account for variation in availability and use of data elements within each EHR instance.

Data formatting and processes

Is VennU FHIR-compliant?
FHIR compliance refers to the package that is sending transactional EHR data, meta data and other data. For example, a given FHIR resource could be 90% “package” and 10% transactional EHR data. VennU can meet FHIR’s1  clinical data model and emulate transactional EHR data through a FHIR Façade approach, but it is not a certified FHIR server.

How does VennU output the data currently?
VennU APIs are accessed through an endpoint in JSON format and can be consumed using an http protocol. VennU APIs also can be put onto an SFTP server.

Can I use VennU to add business logic to trigger, transform, or process data?
VennU currently can perform simple transformations, such as renaming fields.  It will soon1 have the ability to provide additional transformations, including triggers, business logic, scheduling/polling, API chaining, data quality checks, notifications and alerting.

VennU implementation and resourcing

How is VennU deployed?
VennU is installed on customer infrastructure. Medcurio is proceeding through security and privacy certification processes. We will soon support multiple deployment options to suit customer preferences, including cloud hosting1 and hybrid models.

How much time is required to set up VennU, and what resources does installation take?
The VennU on-prem install requires less than four hours of effort once connectivity is established. Three components are installed:

System resources needed include:

Can VennU reduce the need for scarce coding resources to access EHR data?
Yes. Traditional methods of data access require considerable time from technical staff to access data on demand. VennU enables an analyst to create APIs, eliminates the need for coders, and reduces overall time and effort by 85%.

VennU use cases

How is VennU being used today? What are some current use cases?
Customers are using VennU to access data for real-time needs and to access data not available through FHIR, HL7, or EHR vendor APIs. Some uses include:

Real-time AI icon

Using real-time AI to recommend coding upon patient discharge.

Real-Time Operational Analytics icon

Offering real-time operational analytics for managing emergency department capacity and staffing.

Real-Time Dashboard Analytics icon

Delivering real-time dashboard analytics to track financial, clinical, quality and performance information.

Master Data Management icon

Synchronizing electronic health records with master data management platforms.

Customer Relationship Management icon

Integrating patients' preferred contact method and other EHR data with customer relationship management software to make patient representatives more efficient and enable data access for a nurse call center.

1 Roadmap item

Download the FAQ


Simplify the use of EHR data when, where, and how it’s needed to improve care.

Contact Us