Home › Forums › Developers › General developer's discussion ›

Proposed Visit Changes to 1.8

Submitted by Ben_Charlton on Sun, 17/08/2014 - 21:42
in

With regard to migration I assume the Venom visit codes wont be available by default and will require practice integration

Which I assume the method would be an update or adjustment to the appointment archetype, to include lookup.presentingComplaint* and lookup.visitReason

Should we provide this at roll out or leave it to integrators...

It seems that it would be beneficial to provide it as a core archetype going forward for new installations.  

‹ Patch to Upgrade Jasperreports to version 5.5. Product Batch Numbers and Expiry Dates ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: Proposed Visit Changes to 1.8

Submitted by tanderson on Mon, 18/08/2014 - 20:31.

I imagine that the VeNom Reason for Visit codes will eventually find their way into OpenVPMS, but at this stage not in 1.8.

They would be stored in a lookup.visitReasonVeNom.  The act.patientClinicalEvent and act.customerAppointment archetypes would pick them up by changing the reason node to use lookup.visitReason*.

 

Syndicate content