MEDHIS Odoo Revenue Interface Workflow

แหล่งอ้างอิง: phase-4-uat-documents/1. MEDHIS/3. MEDHIS - รายงานผลการทดสอบเชื่อมโยงระบบ MEDHIS กับระบบงาน ODOO ERP.pdf

Overview

ส่งข้อมูลรายได้จาก Billing / MEDHIS ไปยัง Odoo ERP เพื่อบันทึกบัญชี Receipt, Invoice, Deposit, และ Onward revenue.

Stream	Direction	Timing	Accounting Target
HIS Receipt	MEDHIS → Odoo	Daily 00:01	Receipt/payment posting
HIS Invoice	MEDHIS → Odoo	Daily 00:01	Invoice/debtor posting
Deposit	MEDHIS → Odoo	Daily interface group	Customer payment/deposit posting
HIS Onward	MEDHIS → Odoo	Monthly, first day of next month	IPD accrued revenue journal entry

Billing generates Receipt, Invoice, Deposit, or unbilled IPD Ward revenue.
Interface job selects eligible records:
- includes valid records for the period
- excludes same-day cancelled items
- includes cross-day cancellation correction where applicable
MEDHIS creates interface payload or log file using the source-defined naming/running sequence.
MEDHIS sends one transaction or visit-level payload to Odoo ERP API.
Odoo records request and validates required fields.
Odoo creates invoice/payment/journal entry and maps account, cost center, profit center, customer/payor, patient, VN/AN, and doctor fields.
Odoo returns success or failure response.
Interface result is logged for audit and rerun.

See HIS ERP Interface Data Dictionary for full payload-level field mapping.

Field Group	Examples
Patient and encounter	HN, patient_name, episode_type, VN/AN
Billing document	receipt/invoice number, invoice_date, journal_code, move_type
Accounting	account_code, cost_code, profit_code, price_unit, balance
Payment	payment method, bank, reference, amount
Payor	customer / TPA code, insurance_code

HIS should not edit original sales documents after interface; use cancellation/correction.
Missing ERP mapping should result in ERP error visibility, then user fixes mapping and reruns.
Logs should be retained for finance and interface support.