承接 docplanner/integrations-api-sdk-php 相关项目开发

从需求分析到上线部署,全程专人跟进,保证项目质量与交付效率

邮箱:yvsm@zunyunkeji.com | QQ:316430983 | 微信:yvsm316

docplanner/integrations-api-sdk-php

Composer 安装命令:

composer require docplanner/integrations-api-sdk-php

包简介

DocPlanner integration API SDK

README 文档

README

  • PHP 5.5 and later
  • Guzzle 6.2 or later

Installation & Usage

Composer

To install the bindings via Composer, run composer require docplanner/integrations-api-sdk-php.

Manual Installation

Download the files and include autoload.php:

    require_once('/path/to/DocPlanner/Client/vendor/autoload.php');

Getting Started

Please follow the installation procedure and then run the following:

<?php
require_once(__DIR__ . '/vendor/autoload.php');
//Get OAuth2 access token
$authorization = new DocPlanner\Client\Authorization('https://www.{domain}/oauth/v2/token');
$accessToken = $authorization->getAccessToken('YOUR_CLIENT_ID', 'YOUR_CLIENT_SECRET');

// Configure access token for authorization 
$config = DocPlanner\Client\Configuration::getDefaultConfiguration();
$config->setAccessToken($accessToken);
$config->setHost('https://www.{domain}/api/v3/integration');

$apiInstance = new DocPlanner\Client\Api\DoctorsApi(
    // If you want use custom http client, pass your client which implements `GuzzleHttp\ClientInterface`.
    // This is optional, `GuzzleHttp\Client` will be used as default.
    new GuzzleHttp\Client(),
    $config
);
$facility_id = 56; // int | ID of the Facility
$with = array(\DocPlanner\Client\Model\DoctorsScopes::SPECIALIZATIONS); // string[] | 

try {
    $result = $apiInstance->getDoctors($facility_id, $with);
    print_r($result);
} catch (Exception $e) {
    echo 'Exception when calling DoctorsApi->getDoctors: ', $e->getMessage(), PHP_EOL;
}

// Configure access token for authorization 
$config = DocPlanner\Client\Configuration::getDefaultConfiguration()->setAccessToken($accessToken);

$apiInstance = new DocPlanner\Client\Api\AddressesApi(
    // If you want use custom http client, pass your client which implements `GuzzleHttp\ClientInterface`.
    // This is optional, `GuzzleHttp\Client` will be used as default.
    new GuzzleHttp\Client(),
    $config
);
$facility_id = 56; // int | ID of the Facility
$doctor_id = 56; // int | ID of a doctor in a facility

try {
    $result = $apiInstance->getAddresses($facility_id, $doctor_id);
    print_r($result);
} catch (Exception $e) {
    echo 'Exception when calling AddressesApi->getAddresses: ', $e->getMessage(), PHP_EOL;
}
?>

Authorization

To get access to API you need to make request to https://www.{domain}/oauth/v2/token for access token using your client credentials (client_id and client_secret). Then it could be injected to Configuration which is used to instantiate API clients. Whole authorization process is based on OAuth2 protocol with grant_type = client_credentials and scope = integration. Obtained token is valid for the next 24h, so it is good practice to cache it for that period.

###Example

//Get OAuth2 access token
$authorization = new DocPlanner\Client\Authorization('https://www.{domain}/oauth/v2/token');
$accessToken = $authorization->getAccessToken('YOUR_CLIENT_ID', 'YOUR_CLIENT_SECRET');

// Configure access token for authorization 
$config = DocPlanner\Client\Configuration::getDefaultConfiguration()->setAccessToken($accessToken);

$apiInstance = new DocPlanner\Client\Api\AddressesApi(null, $config);

Documentation for API Endpoints

All URIs are relative to https://www.{domain}/api/v3/integration

Class Method HTTP request Description
APINotificationCallbacksApi pullMultipleNotification GET /notifications/multiple
APINotificationCallbacksApi pullNotification GET /notifications
APINotificationCallbacksApi pushNotifications POST /{client-endpoint-url}
APINotificationCallbacksApi releaseNotifications POST /notifications/release
AddressesApi getAddress GET /facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}
AddressesApi getAddresses GET /facilities/{facility_id}/doctors/{doctor_id}/addresses
BookingsApi cancelBooking DELETE /facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/bookings/{booking_id}
BookingsApi getBooking GET /facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/bookings/{booking_id}
BookingsApi getBookings GET /facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/bookings
BookingsApi moveBooking POST /facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/bookings/{booking_id}/move
BookingsApi requestOpinion PUT /facilities/{facility_id}/doctors/{doctor_id}/opinion-request
CalendarBreaksApi addCalendarBreak POST /facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/breaks
CalendarBreaksApi deleteCalendarBreak DELETE /facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/breaks/{break_id}
CalendarBreaksApi getCalendarBreak GET /facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/breaks/{break_id}
CalendarBreaksApi getCalendarBreaks GET /facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/breaks
CalendarBreaksApi moveCalendarBreak PATCH /facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/breaks/{break_id}
CalendarsApi disableCalendar POST /facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/calendar/disable
CalendarsApi enableCalendar POST /facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/calendar/enable
DoctorsApi getDoctor GET /facilities/{facility_id}/doctors/{doctor_id}
DoctorsApi getDoctors GET /facilities/{facility_id}/doctors
FacilitiesApi getFacilities GET /facilities
FacilitiesApi getFacility GET /facilities/{facility_id}
InsurancesApi addAddressInsuranceProvider POST /facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/insurance-providers
InsurancesApi deleteAddressInsuranceProvider DELETE /facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/insurance-providers/{insurance_provider}
InsurancesApi getAddressInsuranceProviders GET /facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/insurance-providers
InsurancesApi getInsurancePlans GET /insurance-providers/{insurance_provider_id}/plans
InsurancesApi getInsuranceProviders GET /insurance-providers
InsurancesApi updateOrCreateAddressInsuranceProvider PUT /facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/insurance-providers
PatientPresenceApi markPatientAbsence DELETE /facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/bookings/{booking_id}/presence/patient
PatientPresenceApi markPatientPresence POST /facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/bookings/{booking_id}/presence/patient
ServicesApi addAddressService POST /facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/services
ServicesApi deleteAddressService DELETE /facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/services/{address_service_id}
ServicesApi getAddressService GET /facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/services/{address_service_id}
ServicesApi getAddressServices GET /facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/services
ServicesApi getServices GET /services
ServicesApi updateAddressService PATCH /facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/services/{address_service_id}
SlotsApi bookSlot POST /facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/slots/{start}/book
SlotsApi deleteSlots DELETE /facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/slots/{date}
SlotsApi getSlots GET /facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/slots
SlotsApi replaceSlots PUT /facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/slots

Documentation For Models

docplanner/integrations-api-sdk-php 适用场景与选型建议

docplanner/integrations-api-sdk-php 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 1.51k 次下载、GitHub Stars 达 5, 最近一次更新时间为 2020 年 12 月 17 日, 在 PHP 生态内属于活跃度较高的组件。

它主要适用于以下技术方向: 「php」 「api」 「sdk」 「docplanner」 等业务场景。在实际项目中,围绕这些方向常见需要落地的问题包括:接口对接、性能调优、并发安全、与既有框架(Laravel / ThinkPHP / Yii / Webman 等)的兼容适配,以及生产环境的日志埋点与稳定性保障。

我们在过去多个企业项目中使用过 docplanner/integrations-api-sdk-php 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。

围绕 docplanner/integrations-api-sdk-php 我们能提供哪些服务?
定制开发 / 二次开发

基于 docplanner/integrations-api-sdk-php 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。

BUG 修复 & 性能优化

线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。

项目外包 & 长期维护

承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。

yvsm@zunyunkeji.com QQ:316430983 微信:yvsm316 西安尊云信息科技 · 专注 PHP / Go / 分布式系统研发

统计信息

  • 总下载量: 1.51k
  • 月度下载量: 0
  • 日度下载量: 0
  • 收藏数: 5
  • 点击次数: 3
  • 依赖项目数: 0
  • 推荐数: 0

GitHub 信息

  • Stars: 5
  • Watchers: 36
  • Forks: 3
  • 开发语言: PHP

其他信息

  • 授权协议: proprietary
  • 更新时间: 2020-12-17