Notifications
Clear all
Topic starter
I have an encounter that uses two separate Text components to load specific forms based on patient age (One for Vital Signs and one for PE). These text components work great to add the form to the encounter but are also creating an unnecessary trailing return in the text translation after the form.
This encounter also has a form that contains a button to load an additional form. Again this results in a trailing return in the text translation after the form that was added.
Is there any way to keep these trailing returns from populating?
Posted : July 30, 2019 5:22 am
