Portals, or an easier way?

June 17, 201114 yr

Newbies

I am setting up an insurance billing database for use via IWP, and I am having some trouble getting the "reporting" interface right. I'm trying to do this with a portal...this may not be the best way.

Basically, I am tracking patient visits for each month. There are 3 types of patient visits available, and different combinations of those visits result in different billing codes that are sent to insurance. I am having trouble building the layout that the doctors will look at to see the status of patients in a certain clinic.

I have a patient_demographics table linked to a patient_visits table (one-to-many) via a patientID field. The visit table has the information I'm really interested in - the visit date, the visit type (clinic, ST visit, or FF visit) and the visit location.

My "dream" layout would have just the dates of the visits for that month, by type:

[demo::patientID] [demo::patientLN] [demo::patientFN]

[visit::clinic visit date] [visit::ST visit date] [visit::FF#1 date] [visit::FF #2 date] [visit::FF#3 date] [visit::FF#4 date]

I *can* get a "standard" style (1 visit per line) portal, filtered for the specified month & visit location. The layout is based on table:patient_demographics, so there is only 1 line per patient. The portal is based on the related visits table.

I run into trouble trying to get the visit dates inline...I tried to create 6 "one-field" portals (with "visit::visit_date as the field), and then filter each portal based on visit type (so, the 1st one is visit type = "clinic", 2nd one is visit type = "st", 3rd one is visit type = "ff", 4th one is visit type = "ff" + show 2nd record...etc). When I do the one-field portals, it shows the records for all visits, not those of this particular patient.

I have also tried creating multiple relationships to do the filtering, but things got confusing fast. I have a habit of making things too complicated...Hopefully someone will be able to help.

Thanks,

Lacinda