SuperAPI AI Directory

hospital-skill

General & other

View repository

Updated 10-16 08:42

About this skill

Hospital registration

A set of capabilities for completing hospital search, department and time slot selection, appointment registration, and registration record queries based on a hospital list.

Trigger scenarios

Examples of user utterances (routing hits this skill):

  • "Help me make an appointment"
  • "What hospitals are nearby"
  • "I want to make an appointment for the respiratory medicine department"
  • "What departments does Peking University First Hospital have"
  • "Help me book an appointment"
  • "View my registration records"
  • "My previous registration records"

Out of scope

  • Online consultations, text/image consultations, medication delivery, etc. → not within the scope of this skill; handled by consultation/pharmacy skills
  • Medical expense reimbursement, medical insurance inquiries, etc. → not within the scope of this skill
  • Emergency treatment, 120 calls, and other urgent medical requests → not within the scope of this skill; please guide the user to call 120

API flow

  • searchHospitals: hospital search and display of candidate hospital list, supporting keyword search.
  • getAvailableSlots: view the list of available registration time slots for a specified department.
  • bookAppointment: execute appointment registration after confirming the time slot.
  • getMyAppointments: query the current user's registration record list.

Usage order

  • Before registering, the hospital and department must first be determined; when there is no hospital context, first display the list of available hospitals, and after the user selects a hospital, display the department list.
  • After selecting a department, display the list of available appointment time slots for that department, and after the user selects a specific time slot, proceed with appointment confirmation.
  • After appointment confirmation, display the registration result card, including visit information.
  • Querying registration records requires no prerequisites and directly returns historical records.
  • All APIs with bound components should prioritize displaying cards, and should not be changed to plain text expanded item by item.