This repository has been archived by the owner on Jan 9, 2023. It is now read-only.
Modify the patient object to capture configurable fields #470
Labels
🚀enhancement
an issue/pull request that adds a feature to the application
in progress
indicates that issue/pull request is currently being worked on
Currently, the patient object is a limited set of fields. It's right and good that the application would ship with a preferred set of fields on a patient entity. However, even our first few deployments have made it clear that there needs to be an ability to both remove and add fields. Given that ORM nature of our data storage, this should be (generally a non-issue). However, that requires a few changes.
One of which is the implementation of a dynamic form build capability. Current thinking is that this Ember Addon would be the appropriate way to go. https://github.com/toddjordan/ember-cli-dynamic-forms
Thus, the following steps should be taken.
That said, the following fields must ALWAYS be available on the patient registration screen, even if they are not all required:
cc: @jkleinsc for review.
The text was updated successfully, but these errors were encountered: