julialongtin wrote on Sunday, February 20, 2011:
Pardon me while I Re-state some assumptions, in an attempt to make sure I'm understanding this right, and try to supply a possible solution (with major issues)
You're using the 'active' flag of a patient to determine whether a patient is currently being seen by your organization. specifically, you turn them inactive when you no longer expect to see this client.
You are currently using the reports system, and using its built in filters to only show active clients, when you do reports.
You are wanting to do reports based on clients which were active at a given point, not just the current state of the world.
You are also wanting to track when you started seeing a client, and when you stopped.
Now, if i were trying to solve the problem of '"i need to know whether a client is active or not, track when they became active, and track when i think i'm done with them", this is what I would do:
To model the data, i would create an encounter form. this encounter form would become authoratative when signed per my signaures system, so it would show as the default activity page for this user (think how history works, only strting from an encounter, getting signed, then being all visible). when a close date is entered, a new encounter form would have to be filed for the new activity period.
I would then make my world a living pain, while I tell the report system to do reports on this. not-trivial. getting the behavior out of an encounter form that you want is pretty simple. getting the reports to work against it would take real work.
Now that i've made things as clear as mud…