It is common industry practice to design blinded studies to avoid introducing bias into study results. When running a blinded study, there are two types of content: blinded and unblinded. Unblinded content contains sensitive study information, for example, randomization, and can only be viewed by a limited group of people to ensure that study teams do not know which subjects are assigned to test groups versus placebo groups. Blinded content is unrestricted and can be viewed by all users without risk of biasing study results.
With the Create Content field on the User object and the Blinding standard picklist, Admins can define which users can create unblinded (restricted) content and which cannot, allowing organizations to securely and confidently manage restricted content in Vault. When you create, classify, or reclassify a document, or update certain fields, Vault automatically sets the Content (
blinding__v) document field.
Note: Depending on your Vault’s configuration, the Content document field may appear as Blinding.
About Content Field Defaulting
When configured, Vault automatically populates the Content (
blinding__v) document field when you create, classify, or reclassify a document, or when you update the Study, Study Country, or Study Site document fields.
Vault uses the value from the Create Content field on your user record.
Creating Blinded & Unblinded Content
Based on your user configuration, Vault automatically sets the Content document field to Blinded if you can only create blinded, unrestricted content that poses no risk to study results. If you can create unblinded content, Vault sets the Content (
blinding__v) field to Unblinded, ensuring that documents are only available to a small group of users.
Switching from Unblinded to Blinded Content
When configured, users who can create unblinded content can sometimes update the Content (
blinding__v) document field via a user action. When the Create Content field is set to Unblinded for a document in a given lifecycle state, you can select the Change to Blinded user action from the document Actions menu. This sets the Content (
blinding__v) field to Blinded, making the content available to all defined users. Your document role must include the Edit Fields permission to run this action.
Note that setting this field from Unblinded to Blinded cannot be undone.