Clinic Use Case

Use case description

A person needs to make an appointment with a medical doctor. A software agent receives a task to automatically set up this appointment. The human user provides the software agent some minimum data, like, for example, specialty, date range, time range, and location. The software agent execute queries on known clinical servers trying to match their responses to the user request.

The user then receives a list with all found options. He chooses one and he informs the software agent to set up the appointment to this option. The software agent sends a request with all necessary data to the selected server which persists the data and it sends back a response with the appointment data.

Basic steps

The communication between the client agent and the clinic host needs a shared vocabulary. The Clinic ontology provides the necessary shared knowledge as it acts as a semantic interface.

The following steps can resume the basic query operation:

  • The agent sends a request to get a list of available servers that implements the clinic interface;
  • For each host in the list, the agent sends a request to get the list of medical doctors;
  • For each medical doctor in the response list, the agent sends a request to get his/her schedule availability;
  • The user then chooses one or more doctor and schedule date and time;
  • The software agent sends a put request to insert data to set up an appointment.

Accessing the Clinic data:



Listing all clinics data

http://www.activeontology.com.br/serin/www.unifor.br/clinic.owl/Clinic

Listing all doctors data

http://www.activeontology.com.br/serin/www.unifor.br/clinic.owl/Doctor

Listing an individual doctor data

http://www.activeontology.com.br/serin/www.unifor.br/clinic.owl/Doctor/1
Comments