Pharmaceutical, biopharmaceutical, and medical devices companies turn to Tulip for use cases spanning training, work instructions, line clearance, logbooks, history records, quality control, and batch/device release. With newly released GxP features in the Tulip platform, it is easier than ever for manufacturers subject to regulatory compliance to take advantage of digital transformation.
The Tulip Platform includes prebuilt apps that you can use to understand the ins and outs of the platform for that use case and how easy it is to get started with building no-code apps in GxP environments. Videos from Giovanni Carrara, our Community Lead at Tulip, will give you a firsthand look at the platform in action by exploring these apps. Let’s take a look at how Tulip’s robust version control and approval workflows can ensure that the correct versions of apps are running in your environment.
The previous blog in this series looked at how to implement E-signatures in Tulip. Let’s dive into version controls and approvals:
The versions menu in Tulip provides full version history of all the apps that have been published. You can see when the app was created, the different versions available, and what has changed between each version.
Version History of Cleaning Logbook App
You can also specify that only specific end users can publish apps within your Tulip account, controlling who has access in your organization to set apps live through the permissions menu.
Permissions for a Cleaning Logbook App
You can specify user permissions, so if you want to provide someone editing abilities, publishing capabilities, or view-only access, it is only a few clicks away.
With approval workflows, specific groups of people within your organization can be required to sign off on the app before an app is published. This can ensure that the correct version is running and that it meets all of your organization’s requirements. Your list of approvals can be customized within your account.
If you have one approval workflow with a compliance team, for example, you can easily add a requirement for an engineering team member to sign off on any changes as well. With Tulip, deploying apps with approvals is quick and easy, while maintaining robust capabilities.
The next blog in this series will look at app completion data in Tulip. If you want to learn more about the future of life sciences manufacturing, we recently hosted an event with industry experts full of presentations, panels, and roundtable discussions. You can view the event recordings here.
If you want to learn about how Tulip can be implemented in your operation, contact us for more.