Peking University International Hospital Patient Service

Problem

Booking, schedule, and appointment lookups at Peking University International Hospital are fragmented across a mobile mini-program and manual channels. Automation is brittle because captcha, SMS login, short-lived tokens, and re-verification for sensitive actions turn a simple query into a multi-step state problem. Throwaway scripts also tend to leak PKUIH_API_KEY, SMS codes, or login state into logs and shell profiles. pkuih-patient-service packages these steps into a Skill, so an agent or terminal workflow can call a stable API surface for departments, doctors, slots, and appointments.

How It Works

The skill organizes authentication, appointment, report, and payment interfaces. Core available capabilities include:
- Authentication: getCaptcha(), sendSms(...), login(...), and logout(), with a token valid for about 30 minutes.
- Appointments: appointment.getDoctorSchedule(...) for doctor schedules, appointment.getScheduleDetail(...) for slot details, appointment.book(...) for booking, and appointment.getAppointments(...) for records.
- Reserved extensions: report and payment modules are present at the interface level, but the materials mark them as coming soon, so they should not be treated as reliable.

The main flow is to apply for an API Key, configure the environment variable in ~/.profile, then call captcha, SMS, login, schedule lookup, slot selection, and booking. Payment and cancellation require re-verification, and state in /tmp/pkuih_state.json is automatically cleaned up.

Boundaries

It is suitable as a thin integration layer for the hospital's open APIs and workflow orchestration, not for storing long-lived PHI, executing production payments without additional controls, or supporting clinical decisions. The API Key is mandatory and must not be committed; SMS codes expire in five minutes; cross-session use depends on short-lived tokens and local state. For stable production use, add rate limiting, retries, key rotation, and audit logging.