Items to clarify in a MedAgents implementation proposal

An implementation proposal needs to state which capabilities the facility receives, who configures them, who verifies them, and which costs depend on external services. The items below are points to be agreed on, not a price list or contract terms already in effect.

Three groups of work to keep separate

• Initial setup: discovery session, account and permission configuration, data migration, training, and testing.
• Routine operations: the runtime environment, updates, backups, monitoring, and support scope.
• Changes after rollout: new features, additional integrations, newly generated data, and further training.

External integrations and costs

For Zalo OA, Messenger, a call center, or an AI vendor, you need to determine which party holds the account, the usage rights, the quotas, and any additional costs. Having integration code is not enough to ensure the connection will work in the facility's environment.

Data and end of service

The agreement should state the purpose of processing, who is granted access, where data is stored, and which parties receive data. It should define the handover format, the accompanying document types, the reconciliation method, and the data handling process at the end of use. Do not infer unlimited data export rights or an AI vendor's policies from the software architecture alone.

Confirm scope using real-world scenarios

MedAgents covers patient intake, consultation, prescribing, billing, and post-visit follow-up. Digital signatures, social insurance, electronic invoices, and LIS/PACS require separate assessment. See platform capabilities and book a consultation to prepare the list of items to check.