Why Predefined Action IDs Matter
Under Chrome Manifest V3 and strict healthcare compliance guidelines (Rule #8 of LamaniSync Architecture):
Page-world code may execute only predefined adapter action IDs — never arbitrary remote URL, method, body, or executable string instructions.
This architectural guarantee protects your clinic: even if a malicious actor were to intercept cloud traffic, they cannot force the extension to execute unauthorized JavaScript or exfiltrate private patient records.
Declarative Adapter Structure
To support regional or custom clinic web portals (such as custom Laravel, React, or legacy ASP.NET portals), LamaniSync uses Declarative Manifests:
{
"adapter_id": "custom-clinic-portal-v1",
"match_origin": "https://portal.myclinic.com.my/*",
"version": "1.0.0",
"actions": {
"READ_AVAILABLE_SLOTS": {
"target_selector": "#calendar-grid-container",
"slot_row_selector": ".slot-available",
"time_attr": "data-slot-time",
"doctor_attr": "data-doctor-id"
},
"INSERT_APPOINTMENT": {
"open_modal_btn": "#btn-new-appointment",
"patient_name_input": "input[name='patient_name']",
"phone_input": "input[name='contact_phone']",
"time_select": "select[name='appointment_slot']",
"submit_btn": "#btn-confirm-save"
},
"VERIFY_WRITEBACK": {
"calendar_entry_selector": ".appointment-card[data-booking-id='{ID}']",
"success_banner_selector": ".toast-success"
}
}
}
Step-by-Step Onboarding for Custom Portals
- Schedule Technical Assessment: Contact our engineering team at support@lamanify.com with details of your clinic's web portal.
- Schema Definition: Our team creates a sandboxed declarative manifest matching your portal's DOM hierarchy.
- Safety Validation: The manifest is statically verified against our Zod schema validator and signed with LamaniHub's deployment key.
- Zero-Update Rollout: The manifest loads into your workstation's extension securely as data — requiring zero reinstallation or browser restarts.