When building eDHR applications it is critical that the data you want saved to a record is saved how you expect it - when you expect it. This requires extensive testing of work orders in every possible way an operator can execute an application in order to ensure the items being written to the record appear as expected and in the correct format/order.
Currently:
- App tested in the Player with a sample WO
- Data is written to the record(s)
- A ‘Record Review App’ Must be opened to observe how the record looks.
- Adjustments are made to app logic based on how the record should appear to the person doing the record review (E.g. QC)
- All record history can’t be altered and developers only have a handful of work orders to test with so it’s a lot harder to see the changes to the record history over time using the same work orders.
Proposed:
In Test mode there should be an option to emulate a record history widget based on a Record Placeholder you select - so that when an app is being tested the developer can look at how that record would appear to a QC person or an Auditor, for example.
This would massively speed up development/deployment of Tulip apps vs how the process is currently done today and alleviate a painpoint for developers.
