edenlabllc/prm.api

Partnership Relations Management for Ukrainian Health Services government institution.

PRM API

Partnership Relations Management API for Ukrainian Health Services government institution.

Specification

• API docs
• Entity-relation diagram

Installation

You can use official Docker container to deploy this service, it can be found on nebo15/prm Docker Hub.

Dependencies

• PostgreSQL 9.6 is used as storage back-end.
• Elixir 1.4
• Erlang/OTP 19.2

Configuration

See ENVIRONMENT.md.

License

See LICENSE.md.

prm.api's Issues

[CRUD] Party methods

Implement all the Party methods according to the spec

[PRM] Get Labour contracts service

Implement the subj. service according to the spec

[IL] Approve declaration request

Implement the subj. service according to the spec
Basic logic

[Public.API] Doctor data model

Adjust the doctor's DM and api spec according to the last agreements

[Public.API] Specification enhancements

1. Add Resend Auth SMS method
2. Add Dictionary lookups methods: Addresses, etc.
3. Add verification status to Create Declaration request!!! In case if new phone should be verified.
4. Remove National_id.
5. Document type enum:
   • passport
   • national_id
   • birth_certificate
   • temporary_certificate

[IL] Update Legal Entity status

Implement the subj. service according to the spec
Basic logic

PRM DB creation

Create the PRM DB scheme and objects according to the spec on the PostgreSQL

[PRM] Update Labour contract service

Implement the subj. service according to the spec

[DEMO] IL.Register Employee method

Implement the subj according to the spec and service logic

[PRM] Create / read / update / delete for MSP

Implement CRUD for MSPs.

Auth UI design

• login page
• client approval page
• forgot password page

[IL] Get Employees List

Implement the subj. service according to the spec
Basic logic

Refactor tests to use ex_machina factory

[IL] Send verification code

Implement the subj. service according to the spec
Basic logic

[IL] Get legal entities

Implement the subj. service according to the spec
Basic logic

[IL] Get person declaration

Implement the subj. service according to the spec
Basic logic

[PRM] "Get Doctor Details" service

Implement the subj. service according to the spec

Logging pattern

Design and describe as a part of manifest Logging Pattern:

• What types of events to log
• What kind of information to collect
• Some kind of notifications
• Easy to use log info

etc

[DB] PRM data model changes: employee, user, doctor, legal_entity, divisions and more

new spec

updated model

[PRM] Search Declarations service

Implement the subj. service according to the spec

[IL] Create Declaration service

Implement the subj. service according to the spec and service logic

[IL+PRM] Update Employee

Implement the subj. service according to the spec
Basic logic

[DEMO] IL.Approve Employee

Implement the subj. method according to the spec and logic

[PRM] "Register a Doctor" service

Implement the subj. service according to the spec and service logic

[PRM] Get Declaration Service

Implement the subj. service according to the spec

[CRUD] Legal Entity

Implement the subj. group of methods according to the spec

[DEMO] Employees CRUD methods

Labour contract entity has been deprecated. Employee entity should be introduced instead.
Implement the below methods

1. create-new-employee
2. search-for-an-employee
3. get-employee-details

[IL] Create or Update Employee via Employee Request

Implement the subj. service according to the spec
Basic logic

[Reports] Search Declarations over the period

Implement the subj. service according to the spec

Create and set up GW for eHealth

[INTERNAL.API] Get Global Parameters

Implement the subj. service according to the spec

[IL] Get Employee Details

Implement the subj. service according to the spec
Basic logic

[PRM] Register new labour contract service

Implement the subj. service according to the spec

[IL] Get Employee Requests List

Implement the subj. service according to the spec
Basic logic

[CRUD] PRM Employee

Implement the subj. group of methods according to the spec

Revise DB entities

We a few issues right now:

• add validations,

• add proper embeds + embed records validation,

• make sure all [] columns are jsonb[]

  On the DB level some fields are jsonb[] while some are jsonb, while both are arrays of maps on the app level. This should be jsonb[] everywhere on the DB level.

[IL] Create declaration request

Implement the subj. service according to the spec
Basic logic

[PRM] "Update Doctor" Service

Implement the subj. service according to the spec

[PRM] "Register new declaration" service

Implement the subj. service according to the spec and service logic

[PRM] CRUD for confident persons

Implement the subj. service according to the spec

[IL] Check phone number

Implement the subj. service according to the spec
Basic logic

[IL] Get Legal Entity by ID

Implement the subj. service according to the spec
Basic logic

[PRM] "Search Doctor" service

Implement the subj. service according to the spec

[IL] Search for a Person

Implement the subj. service according to the spec
Basic logic

[IL] Verify code

Implement the subj. service according to the spec
Basic logic

[IL] Get Employee Request by ID

Implement the subj. service according to the spec
Basic logic

[CRUD] Ops DB Declarations

Implement all the Declarations private methods

[CRUD] Doctors

Implement the Doctors group of methods according to the spec

It should work with the prm.employee_doctor table

[MPI/PRM] Some dates are returned in wrong format - return date as date

Reproduce

1. Fetch doctors index endpoint:

curl http://104.155.75.171/api/doctors/

2. See some dates for returned objects are specified in the following format:

03-03-2001

This is not correct. Expected format should follow ISO 8601. Dates in correct format, for example, should look like this:

2012-04-23T18:25:43.511Z

Add hierarchy of divisions and legal entities

update DM and public API specs