hieofone-directory/hieofone-directory

Health Information Exchange of One Directory Server.

dev-master 2020-11-01 19:43 UTC

Requires

• php: >=5.5.9
• adci/full-name-parser: ^0.2.4
• bshaffer/oauth2-server-httpfoundation-bridge: ^1.3
• bshaffer/oauth2-server-php: ^1.10
• cache/filesystem-adapter: ^1.0
• doctrine/dbal: ^2.5
• fideloper/proxy: ^4.0
• google/apiclient: ~2.0
• graham-campbell/markdown: ^11.1
• jenssegers/date: *
• knplabs/github-api: ^2.1
• laravel/framework: ^6.0
• laravel/socialite: ^4.0
• laravelcollective/html: ^6.0.0
• php-http/guzzle6-adapter: ^1.1
• phpseclib/phpseclib: ~2.0
• shihjay2/openid-connect-uma-php: dev-master
• simplesoftwareio/simple-qrcode: ~1.4
• socialiteproviders/generators: ^4.1
• socialiteproviders/manager: ^3.3

Requires (Dev)

• filp/whoops: ~2.0
• fzaninotto/faker: ~1.4
• mockery/mockery: ^1.0
• nunomaduro/collision: ^2.0
• phpunit/phpunit: ^7.5
• symfony/css-selector: 2.8.*|3.1.*
• symfony/dom-crawler: 2.8.*|3.1.*

MIT

• Michael Shihjay Chen

• php
• javascript
• oauth2
• health
• laravel
• medical
• oidc
• fhir
• hieofone
• uma

README

HIE of One Directory is a simple server that incorporates OAuth2 and OpenID Connect protocols to facilitate the aggregation of multiple HIE of One Authorization Servers for clients such as physician groups, hospitals, health co-operatives, and third-party health service providers. In effect, a personalized directory of authorized HIE Of One Authorization servers provides the requesting party a "one-stop-shop" for their list of patients for practice work flow management. The only personal information that is sent from the authorization server to the directory is the root URL of the authorization server and the name of the authorization server which will contain the name of the patient.

Installation

Run the following commands to install:

sudo curl -o install.sh https://raw.githubusercontent.com/shihjay2/hieofone-directory/master/install.sh  
sudo chmod +x install.sh  
sudo bash install.sh

Dependencies

1. PHP
2. MySQL
3. Apache
4. CURL

Features

1. OAuth2 OpenID Connect compliant server
2. OAuth2 OpenID Connect relying party for Google and Twitter

How a patient registers with the HIE of One Directory

Requisite conditions:

1. Patient has registered a domain name where the HIE of One Authorization Server is installed (ie domain.xyz)
2. Client software (such as an EHR with a patient portal) has the capability to make HTTPS calls (such as CURL) and is able to process JSON responses.

Step 1:

Patient logs into their HIE of One Authorization Server and authorizes participation to a directory

Step 2:

Patient clicks on Register to a Directory (proposed)

Step 3a:

If the HIE of One Authorization server belongs on a sub-domain that is created by a root domain that has an HIE of One Directory present, a CURL request will be made to verify if a directory exists. If so, the directory URL and name will be listed for patient's approval.

Step 3b:

If a specific directory is not located in the root domain of the patient's authorization server, then the patient will need to either visit the directory service URL (via a QR code) or manually enter the URL of the directory root URL in the URL box after Step 2.

Step 4:

If authorized, a call to the directory's registration route which will then dynamically register the authorization server to the directory.

Security Vulnerabilities

If you discover a security vulnerability within HIE of One Directory, please send an e-mail to Michael Chen at shihjay2 at gmail.com. All security vulnerabilities will be promptly addressed.

License

The HIE of One Directory is open-sourced software licensed under the GNU AGPLv3 license.