Integrations
Yes, Surface can work with Rayen, starting from an export the clinic controls
What is Rayen and where is it used?
Rayen Salud is a Chilean health technology company. Its site states more than twenty years of experience and a presence in over 76% of the country's primary care facilities, with services aimed at public and private establishments: medium and high complexity hospitals, clinics, primary care centres and government bodies.
Its primary care clinical record is described as a comprehensive information system for the clinical and administrative management of primary care centres, with a four-layer family record, a dental record and immunization integrated with the national registry. Rayen also states interoperability with other systems and founding membership of the Chilean HL7 chapter.
What changes when the ground is primary care?
The mix changes and the economics change. In primary care what stays pending is chronic check-ups, laboratory tests and referrals to specialists: high volume and low unit value, so chasing them by hand never pays. Under capitation the result is measured in the care gap that closes.
Who commands the system changes too. If the installation is administered by the municipal corporation or the health service, the centre that wants to chase its own orders does not control the change window. The report it can request locally is the lever it holds today.
What does Surface need out of Rayen?
Four fields per order. None of it forces a change to the clinical record's configuration.
- What was ordered. The text of the exam, the check-up or the specialist referral, exactly as it was written during the visit.
- For whom. A patient identifier, pseudonymized if the centre's policy requires it.
- When. The date of the visit, so each order's deadline can be computed.
- How to reach them. A current mobile number.
If the extract carries the sector or the programme the patient belongs to, prioritization improves and the waiting list sorts better. Without it, the work happens anyway.
A real integration, or an export from the centre?
The real integration reads continuously and writes back the status of each order. The export starts with a report the centre itself produces, with the fields reviewed before the first file leaves, and it depends on no approval from outside the establishment.
| Real integration | Export from the centre | |
|---|---|---|
| Time to first result | Bound to the change window of whoever administers the system | One week of setup and it is in production |
| Who has to approve | The system administrator, normally outside the centre | The establishment itself |
| Data control | Defined in the connection agreement | The centre picks fields, period and frequency |
| Coverage | Continuous across the connected network | The period the centre decides to export |
Starting with the export lets a centre prove the result before asking the network for anything. That is the order we recommend in you can do this without an API, with the detailed calendar in in three weeks.
What does the IT team have to do?
In a primary care centre the technical work usually lands on the statistics lead or a part-time IT contact. We ask them for three things.
Pull the period's list.
Unscheduled orders with the four fields, from the reporting tool the centre already uses.
Repeat it daily.
A daily delivery to a destination the establishment controls. No software installed, nothing opened outward.
Review the first week with us.
We check the file against what the team sees on screen and fix the list before raising the volume.
How do free-text orders inside the system get read?
In primary care the order is written in seconds and in shorthand. Programme acronyms show up, laboratory panel names arrive grouped on one line, and the check-up requested in 3 months carries no attached date.
Surface translates that into bookable services, computes the deadline when it is written in relative terms, and splits orders that arrive fused. Anything ambiguous is flagged for human review. The per-exam catalogue is in the exam library and the decision criteria in how the agent decides.
What does running on Rayen not change?
The establishment defines the scheduling protocols and Surface executes them as written. The patient gets the message under the identity of the centre treating them, and the data stays with the institution, per the detail in your brand, your data.