Triage
Hospital registration independent of mobile use, administrative queue management, and optional QR linking.
Hospital and patient coordination
Make waiting clearer without moving clinical decisions.
LUJEQ gives emergency departments an optional link to the patient app, dedicated staff tools, and a relay infrastructure designed to minimize exposed data.
- Local hospital continuity
- Staff-initiated actions
- Optional patient app
One platform, four roles
Each team gets the tool suited to its responsibility.
Physician
Assigned worklist, neutral calls, and controlled hand-off to the organization's HIS/EHR.
Administration
Staff identities, roles, approvals, access reviews, and central connectivity.
Relay network
Enrollment, certificates, revocation, and transport supervision without visible clinical content.
Controlled journey
An optional connection from triage to care.
- 1
Triage registration
The patient enters the hospital queue whether or not they use the application.
- 2
Voluntary linking
A limited-use QR or code links the application to the visit without exposing the clinical record to the relay.
- 3
Authorized message
Hospital staff initiate a neutral notification. Patient calls are never automated.
- 4
Link closure
The temporary link ends with the visit lifecycle and can be revoked by the authorized service.
Actual product
Interfaces designed for a hospital environment.
Institutional pricing
An offering adapted to each organization's size and context.
Organization
Monthly pricing by quote
Deployment for one hospital, role-specific terminals, and initial onboarding.
Hospital network
Annual pricing by quote
Multiple organizations, centralized governance, and regional deployment planning.
Pilot project
Controlled evaluation
Limited technical and operational validation before a deployment commitment.
Public amounts will be displayed after commercial approval. No provisional price is presented as a contractual offer.
Trust architecture
The hospital server remains protected behind outbound connectivity.
Minimized data. The relay carries opaque routes and encrypted content.
Human control. Notifications are authorized by hospital staff.
Separated access. The public site and protected central console do not share the same access level.
Institutional questions
What an organization should know before an evaluation.
Is the application mandatory?
No. Registration, waiting, and hospital care remain available without a phone or application.
What happens without Internet access?
Essential hospital functions remain local. The mobile link displays a neutral outage notice until service returns.
Who can send a notification?
Only authenticated and authorized hospital staff. The central system never decides automatically to call a patient.
Can the relay see the patient record?
The intended architecture limits the relay to opaque routes and end-to-end encrypted content; production validation remains mandatory before real data is used.
How does a pilot begin?
After legal, security, and privacy review, a limited scope is agreed with the organization and tested without clinical data before activation.
Which systems are involved?
The deployment includes the local hospital server, authorized terminals, the secure relay, and the optional patient application.
LUJEQ project
Prepare an evaluation with your hospital.
The commercial form and official contact details will be enabled after the final domain and legal identity are established.
Central console — restricted access