Consistent Primary Key
Would be helpful if a single appointment/visit/progress note/claim/payment had the same identifying key so they could be easily tracked from report to report.
-
David Plankenhorn commented
I believe that a single 'primary' key to transverse all of these tables would be problematic as there can be one-to-many relationships that may arise at differing stages (e.g., multiple session notes due to Alert Manager issues, rebilling issues after a required Progress Note revision, etc.). Appointment to Progress Note, Visit to Billing and Billing to Claim key values already exist - what is missing is a reported key value between Progress Note and Visit (which must exist as eCR supports a 'Progress Note Summary' view.