Visit Reason Query
Submitted by EastsideVetEmerg on Sat, 10/10/2015 - 11:39
Hi,
So, I was looking at wanting for force users to select a visit reason because of it's effect on another module we have installed. I had some questions:
1) I have changed out visit reasons so there is no default and then changed the min cardinality of reason to 1 in the act.customerAppointment 1.0 archetype.
2) My actual question is... it is reasonable to use the Venom "Presenting Complaint" codes as my "Visit Reasons"?
I would like to track reasons for consultation/presentation (and the "Problems" are not being used for a variety of reasons). Then basically I was going to tie each Venom "Presenting Complaint" to a questionnaire...
Thanks,
Adrian
Re: Visit Reason Query
VeNom uses a separate "Reason for visit" classifier for the appointment and visit reason e.g.
There are 284 of these classifiers.
We don't provide these in the OpenVPMS distribution, but it would be fairly straight forward to do so.
Re: Visit Reason Query
Hi Tim,
Thanks for that. I think it would be useful/make sense to include these, esp if we are using the Venom codes increasingly for other parts of OVPMS.
Thanks,
Adrian