mmurfin87 wrote on Saturday, June 20, 2015:
I’m working on importing claims data and I have tracked down the affected code and tables.
Claims are held in the ‘claims’ table where some sort of logic based on which fields are empty determines its status in the Billing UI. Tables ‘ar_session’ and ‘ar_activity’ maintain accounting line items for each claim.
It isn’t clear to me yet whether a claim absolutely must be associated with an encounter id yet. I’ll assume it is and generate an encounter for each claim though, even if it has no data.
From the database’s perspective, an encounter is just an id that is managed by the one-field ‘sequences’ table. Generally, there is an entry in the ‘forms’ and ‘form_encounter’ tables for these encounters. Although again it isn’t clear if these are absolutely necessary entries or if there are any other necessary entries needed in other tables. Table ‘issues_ecounter’ also holds the issues entered in the New Patient Encounter form but can be blank.
My plan then is to convert the Medware claims into entries into the ‘claims’ table with line items being converted into the ‘ar_*’ tables and update the ‘sequences’ table with the highest id i create so that future entries won’t clobber my imported data.
Anyone see any issues or have any helpful hints?