TODO: Brian mail dev list on Monday when version 1.0 is ready
TODO: Brian will prepare wiki page with screenshots of workflow of AmrsRegistrationModule
*Interception: Darius might lead a discussion on proposed changes to user, person, and patient
Darius mentioned that neither Java or Hibernate support multiple inheritence... hence you cannot have a user and a patient being the same person and be true to the programming language.
Roles would be collections of the underlying person.
Patient and User are roles of a person. We shouldn't need Hibernate magic to make that happen.
Add person_id attribute to both User and Patient could solve the problem.
Hence a proper foreign-key relationship as opposed to assuming person_id=patient_id=user_id.
Add person_id on User and Patient.
To start, we could have Patient extend Person in java, but User does not. User has a Person object as an attribute and all calls to User.getName() do getPerson.getName() under the hood in the User object
Have an Organizational Role that goes onto person (instead of only onto user which gets reused for privileges...which Burke hates)
Plan to describe work and agree upon it so the community can help
Sunny wants a job description or other org role on person as well. Right now they're using person_attributes for that
We want to stay out of too many Human Resource peices. Maybe that is where we could integrate with HRIS.