Ability to create a patient when adding a related person that does not exist

[jackcmeyer]

🚀 Feature Proposal

When creating a Related Person, it assumes that the patient that you want to add as a related person already exists. If the related person does not exist, it is cumbersome to exit the related person modal and go create that patient, then come back to finally add the related person.

Users would like the ability to have some sort of "quick add" that allows me to create a new patient without leaving the related person modal.

Motivation

Be able to quickly add related persons that aren't currently existing patients.

[WaseemAlkurdi]

Example scenario: Let's take the context of a fertility/family planning clinic, where the doctor is creating an entry for an example patient John Doe:

That John Doe is married to Jane Doe, who should share the same record, as the clinic's context needs that . Currently, we have to create a separate entry for her:

then we would have to search for John Doe's record, open it, select Related Persons from there, Add Related Person, then search Jane Doe and select her as Wife. (The "Patients List" page didn't work at the time of posting this, but I will update with screenshots once it becomes available again).

In addition to being cumbersome and very anti-HospitalRun, this approach simply won't work in a fertility clinic, where a couple, not an individual patient, is the focus of the diagnosis and treatment.
Currently, the changes to one person's record would not automatically propagate to the other person's, as the database would consider them as separate patients who just happen to be related. But, as we have seen, this might not be wanted in an obstetrics/gynaecology/fertility/family practice, among others.

A solution would be to move Related Persons to the Add Patient page, where the doctor would be able to enter both John Doe and Jane Doe's details at once, then it would offer the user a checkbox to "join" records (like in the case of a fertility clinic), or leave them detached.

[JDarke]

I'd like to take a shot at this one, please.

[fox1t]

@JDarke nice! We need to wait for this since we need to define more specific requirements. Would you like to be involved also in requirements planning and user story definition?