We're updating the issue view to help you get more done. 

How should optional components interact with patient indexing?

Description

Was just discussing this with .

The patient index is currently based only on the core functionality of the patient-data component. However, additional optional components can and will add to this base functionality (e.g., Owners in patient-access, exomic data, etc.). Because of the current architecture, these additional data cannot be included in the index and cannot be efficiently searched/filtered on (making an Owner filter more difficult than it needs to be, for example).

It seems like each optional component should register itself with the Patient class in some way, along with controllers for JSON and Excel serialization and loading, maybe a UI, optional data indexing, filtering options, etc, but that's just my $0.02.

Environment

None

Status

Assignee

Sergiu Dumitriu

Reporter

Orion Buske

External issue ID

None

External issue ID

None

Priority

Medium