Integrations
Yes, Surface can work with MasterKey, and the first result does not wait for an integration
What is MasterKey?
MasterKey is a Chilean HIS. Its own site presents it as a modular platform bringing together the electronic medical record, scheduling, emergency, operating room, pharmacy, laboratory, imaging and billing, with every module on the same database, and it states interoperability with HL7 v2, HL7 FHIR and DICOM plus a documented REST API.
We write little more than that on purpose. MasterKey publishes less open technical documentation than an international vendor, and describing what its site claims is more honest than assuming how your installation ended up configured. What we do know is that the shape of the extract we need does not depend on the vendor.
What does Surface need out of MasterKey?
Four fields per order, none of which requires a new module or a migration.
- What was ordered. The text of the exam order, the referral or the check-up, exactly as it was written in the record.
- For whom. A patient identifier, pseudonymized if your policy requires it.
- When. The date of the visit where the order was written.
- How to reach them. A current mobile number.
The price list, the full medical record and billing all stay inside MasterKey. Surface works on the subset that leaves in the extract.
A direct connection, or an export the clinic controls?
The direct connection reads from MasterKey continuously and writes back the status of each order. The export starts with a report your team saves and schedules, with the fields it reviewed before the first file ever leaves.
The export reaches a first result sooner because it does not depend on booking time with the system vendor. A mid-sized private clinic rarely has an integration window free this month; it can have a daily report tomorrow.
| Direct connection | Export the clinic controls | |
|---|---|---|
| Time to first result | Depends on coordinating with the system vendor | One week of setup and it is in production |
| What the clinic is asked for | Read credentials and a testing window | One saved, scheduled report |
| Who decides what leaves | Agreed when the scope is defined | The clinic, field by field |
| Coverage | Continuous over the connected modules | Whatever the report carries, on the slice the clinic picks |
The export is the data contract the direct connection reuses later, which is why the first week's work survives the migration. We argue it in full in you can do this without an API.
What does the clinic's IT team have to do?
In a mid-sized Chilean clinic the IT team is two or three people already putting out fires. Their share of this fits in half a morning.
Build the report once.
The period's orders with the four fields. Whoever administers the system in the clinic already knows where they live.
Schedule it.
A daily run into a folder you control. Nothing installed, nothing opened outward.
Validate it with us.
For the first week we check the file against what the team sees on screen and adjust the report together.
How do free-text orders inside the system get read?
Doctors write fast and write short. The same field holds abd + thyroid US, an exam's commercial name, the abbreviation only that specialty uses, and the paper order somebody typed in by hand.
Surface translates that text into your own clinic's service catalogue: it resolves the alias, splits orders that arrive fused on one line, and keeps the condition that changes the preparation. Anything ambiguous is flagged for human review before a patient hears from us. The per-exam detail is in the exam library.
How is this different from the reminders scheduling already sends?
A reminder needs a booked appointment to exist at all. Surface works one step earlier, on the order that never became an appointment, which is why it sits alongside the scheduling module. The distinction and its effect on missed appointments are in the no-show essay.
What does running on MasterKey not change?
The clinic keeps writing the scheduling protocols, the message carries the clinic's brand, and the data stays the clinic's. We spell it out in your brand, your data.