Connects reception, verification, signed records and hospital fees to the existing hospital system. The proposed starting journey is returning-patient reception and fee reconciliation; the HIS remains authoritative for clinical visit creation.
Patients, appointments, visits and treatment episodes have distinct identities and lifecycles. A signed record or received payment does not itself constitute a clinical intake decision.
Prefill and verify within permissions; users review information before confirmation.
PalmID at service points is conditional and includes an alternative assisted route.
Deposits, charges, refunds and documents have separate authoritative outcomes.
Infrastructure components, applicable documentation and integration support within the agreed scope.
Business systems, permitted data, decision authority and end-to-end acceptance.
CAs, banks, device suppliers or data sources as applicable; confirm connection rights and conditions separately.
The source is a proposal. Product scope, release, SDK/API, connections and usage rights require confirmation for the deployment combination; diagrams and mockups do not establish production readiness.
Test appointment recognition through HIS-confirmed visit creation, reconcile collections and handle desk exceptions. Measure intake time, supplementary requests and reconciliation hours within the same scope.
Discuss pilot scopeLightweight offline WebP presentation. The original PDF opens only when you choose it.
Vietnamese presentation · the PDF has not been translated.
The editorial summary is based on the sections linked above. The original PDF is unchanged. An observed version is not confirmation of current commercial status.
Open source document · online
Knowledge HubMobileID_Healthcare_Digital_Ecosystem_Proposal_V3_8K.pdfOrganise documents, approvals and signing around a business workflow.
Explore productIdentity & verificationExplore electronic document reading and identity verification workflows.
Explore productPayments & billingPlan billing workflows and business-data integration.
Explore productLinks orders, collections, receivables and invoices through cross-system references. Trusted Billing coordinates using source data and matching rules, allowing operators to focus on exceptions while accounting systems and banks retain their own authoritative outcomes.
An introductory financial-sector proposal covering identity information through accepted signed records. The reference architecture places integration on the institution server and signing on Mobile-ID SaaS, with explicit authoritative outcomes.
Proposes a server API for consent checking or information matching under a legitimate purpose. The partner submits information for checking; Mobile-ID coordinates and returns outcomes with references rather than source personal data for correction.
Share your current systems and intended outcomes to plan the next integration step.
