44 create new patient

[priesgo]

Adds endpoint to create individual.

Receives a JSON following the Individual model as payload in the POST request. Authentication credentials are passed in the header instead of encoded in the payload. This makes apparent that we need a better authentication mechanism to avoid passing user and password in every request, we need something like a token created at login time.

Succesful creation returns a JSON as follows:

{
  "id": "PH00008635",
  "message": "Individual was created",
  "success": true
}

The new internal id is based on the assumption that internal ids follow the pattern ^PH\d{8}$. If an id like PH1234 exists it will break this assumption and this endpoint will fail. This may be something to improve.

Error conditions:

• Demo user is not allowed to post new users
• Any other payload mimetype than application/json is rejected
• Empty payload
• Any field in the JSON not existing in the individual SQLAlchemy model
• TODO: sanity checks on the individual, eg: sex must be provided

Last this is using SQLAlchemy although we may be moving away from it. The main reason for this is that we have a model in SQLAlchemy that makes parsing the JSON into the DB model easier. If we eventually move away from SQLAlchemy hopefully we will have the database model represented in something else.

[pontikos]

Thanks @priesgo .
Do we have some code to test this? @alanwilter

[pontikos]

@YuanTian1991 can you implement the frontend for this please?

The "new patient" button could be in the side-bar. The new patient page can look like the "edit patient" page for now, but in the future will allow uploading of files (e.g genetics, medical imaging etc).

[priesgo]

No, I didn't add any test code. I'll wait for @alanwilter to merge his branch on testing and then I will follow his lead on this.

[alanwilter]

I know it's merged already but, just a curiosity, in auth.py you created USER = "user", why that and why it was not used e.g. here?