Introduction

This implementation guide describes the sample use case flows for testing the CCDP APIs on the Synapxe HXIS Sandbox.

Reference: Official CCDP documentation.

This CCDP FHIR specification defines the FHIR profiles (constraints) that are used in this project. All FHIR-based specifications rely on an underlying set of base "resources".

CCDP FHIR® Resources

The following resources will be used for its payloads:

  • Patient resource to retrieve patient reference ID and facilitate integration with source system to create, update and view patient profile.
  • Appointment resource to retrieve available slots and book an appointment for a specific health and care service, for example, from SingHealth Polyclinics into a General Medicine Consultation.
  • Observation Enable consumers to track their health by facilitating the self-service entry and retrieval of health observation data.
  • Encounter resource to record interactions between patients and healthcare providers, including visits, admissions, and remote consultations.
  • Questionnaire resource to allow a consuming system to present one or more questions from the provider system to allow a patient to complete as an assessment before/after their visit to facilitate care team or clinician.
  • QuestionnaireResponse resource to submit the response to a questionnaire back to the provider system.
  • CarePlan resource to enable channel applications to perform pre-requisite checks to facilitate the booking of Healthier SG appointments.
  • Invoice resource to allow consumers (and caregivers) to view, retrieve bill details, get outstanding amount/bills and retrieve fully paid bills.
  • Slot resource to enable slot viewing, booking, cancellation, rescheduling. Consumers register same-day appointments, add visitors, and view queue status, itinerary.
  • PaymentTransaction (Custom) resource to provide consumers options to make online payment for their outstanding bills.
  • Notification (Custom) resource to enable delivery of messages to the users via your mobile application.
  • NotificationDevice(Custom) resource for binding ties the retrieval of the registration status of the notification device after its registration.