Your EHR holds gold. But you can't access it.
Most EHR systems are closed. Treatment data is manually retyped, combining with other sources is impossible. House of Data has solved this for multiple healthcare organizations.
EHR systems are closed
Your EHR has no standard export. No APIs, no connections to BigQuery or Power BI. The data is locked inside the system.
Manual retyping
Quality data and treatment notes are manually retyped into Excel. Time-consuming, error-prone, no guarantee of completeness.
No treatment data for analysis
Researchers want to analyze patient characteristics, clinicians want to track treatment outcomes. The data is not available in structured form.
Compliance and privacy are complex
NEN 7510, GDPR, regulatory frameworks: EHR data is medical data with strict legal requirements. Insecure exports weaken your compliance posture.
EHR Data Scan
30 minutes with Herman or Ewald about your EHR system, what data needs to come out and what your goals are. Immediate clarity on what is possible.
Connector design
Technical design for the EHR integration. Which data elements, which transformations, how we implement NEN 7510 and privacy. Architecture review with your IT where needed.
Delivery & operations
Custom connector that safely extracts data from your EHR and loads it into Google Cloud or Azure. Monitoring, maintenance and further development.
From EHR to insight
How a rehabilitation clinic opened its closed EHR system and started analyzing treatment outcomes in real time.
Read moreML platform in rehabilitation care
An ML platform that predicts treatment outcomes based on EHR data. From clinical data to clinical value.
Read moreGCP as foundation for healthcare analytics
Architecture decisions for securely loading and analyzing medical data on Google Cloud.
Read moreData quality: why validation takes longer than you think
Why small deviations in EHR data have major consequences for analyses and ML models.
Read moreFrom technical solution to strategic partnership
How an EHR integration grows into a partnership around data governance and roadmapping.
Read moreThe large consulting firms provide advice and depart. Boutique firms build, but often lack architectural depth. We do both. And we stay.
"Advice without execution is an opinion. Execution without architecture is a time bomb."
What you get
- Consultation with Herman or Ewald about your EHR integrations
- NEN 7510 compliant approach from day 1
- Custom architecture proposal for your institution
- No vendor lock-in, you own the result
Direct Access
EHR Data Integration for healthcare organizations
- What is EHR Data Integration?
- EHR Data Integration is the secure and structured release of treatment data from your electronic health record system for analysis, reporting and research. Most EHR systems are closed by origin: there is no standard export, no API to BigQuery, no connection to Power BI. House of Data builds custom connectors that extract data from the EHR, transform it into a research-ready format and load it into a secure environment on Google Cloud or Azure. From there researchers, controllers and clinicians can work with the data without any manual retyping.
- Which EHR systems do you work with?
- We have experience with several EHR systems common in the Netherlands across specialist medical care, rehabilitation, mental health and elderly care. With every institution we start with an EHR Data Scan to determine which routes to the data are available: direct database access, vendor exports, web services, or a combination. The approach depends on the system, but the starting point is always the same: no changes to the EHR itself, but a reliable integration that works around the EHR.
- How do you handle compliance and NEN 7510?
- NEN 7510 and GDPR are part of the design from day 1, not something added later. We follow a fixed approach: data impact assessment up front, encryption in transport and at rest, pseudonymization where possible, and an access model that aligns with your existing authorization management. For research data we work with a Data Use Agreement and a review committee where needed. We document every choice so your data protection officer can verify what is happening.
- What is an EHR Data Scan?
- The EHR Data Scan is an exploratory conversation of about 30 minutes with Ewald or Herman, followed by a brief technical analysis of your EHR environment. It delivers a clear answer to the question: can we extract the data you need from your EHR in a safe way, and if so: how? You receive a short written summary with the possible routes, the complexity per route and a realistic estimate of what the first working version requires. Free and without follow-up obligation.
- How much impact does this have on the EHR system itself?
- Minimal impact. We deliberately work around the EHR, not inside it. No changes to the EHR database, no modifications to the application, no extra modules. The connector reads data via routes the EHR vendor already supports or which run outside business hours with low priority. We measure the load on the source system and ensure the extraction does not disturb care delivery. To your EHR vendor we are invisible; for you it suddenly makes the data that already exists usable.
- Who owns the connector after delivery?
- You. The code, the documentation and the runtime environment belong to your institution. We do not build a black box that needs us forever. At delivery you receive the source code in your own repository, the connector runs in your own Google Cloud or Azure tenant, and your IT department is trained to operate it. Many clients still choose to leave operations and further development with us because it is more efficient, but that is a choice, not an obligation.
- Can researchers and clinicians use the data directly?
- Yes. The goal is for the data coming out of the EHR to be directly usable for analysis without another intermediate step. Researchers work from BigQuery, Looker, Power BI or R and Python notebooks. Clinicians and controllers receive dashboards with patient characteristics, treatment outcomes and quality indicators. The difference with manual Excel exports is that the data refreshes automatically, is structured according to a fixed model and is traceable back to its source in the EHR. No retyping work, no version conflicts, just a reliable basis for decision making.
Last updated: 11 April 2026