Three portals over one API. The same treatment-assistance journey seen from three sides: the Secretariat and the Medical Advisory Committee who administer the Fund, the member who applies to it, and the facility that treats them and bills for it. Every control names the endpoint behind it.
Membership, the provider panel, the tariff catalogue, contributions and compliance, the application pipeline, Committee review, claims assessment and payment, complaints against their SLA clock, and the administration of the console itself.
144 endpoints · sign in with a staff account GMA memberApply for treatment assistance, follow the case through to its Guarantee of Payment, read your contribution statement, and raise a complaint if something goes wrong.
23 endpoints · sign in with a membership number and PIN Health-service providerTake in the applications members have directed to your facility, cost a treatment proposal, answer the Committee’s queries, hold the Guarantees and claim against them. Sign in with a GMA-MHF facility PIN or with your centralized health-insurance account.
32 endpoints · facility code + PIN, or a health-insurance account
These portals are served by the API itself, so one dotnet run boots the whole demo.
The API reference lives at /scalar/v1.
Every button carries a tooltip explaining its purpose and the endpoint it calls; the
Show / hide endpoints toggle in each portal switches the on-screen endpoint chips off for a
clean, business-facing view.