VISION™’s Invoicing Incentivises Sites

Integrated invoicing is a powerful mechanism for incentivising site participation. It also eliminates extraneous trial management activities. What is it and how does it work? This article takes a closer look at integrated invoicing and how it can work for you. 

Sites deserve to be paid for completed study activities in a timely manner.  Payment milestones such as examination completion, lab result analysis, subject visits are known in advance and documented in the master fee schedule for the study or site. Since these billing milestones are well-defined, the study can be configured to automate the creation and submission of site invoices. This eliminates paperwork for the sites, ensures accuracy, relieves study managers of invoice verification activity and speeds payment.

VISION™’s integrated invoicing functionality allows configuration of invoice line items in a flexible and powerful manner. Examples include:

  • Subject enrollment
  • Study visit completion
  • Physical exam completion
  • Lab samples drawn and sent to lab 

Invoice line item generation can be tied to field completion, a form’s state (e.g., Reviewed or Finalized), the states of a set of related forms, or a combination of the above. Sites across a study are rarely run the same, and it is not uncommon to see a variation in payment schedules across sites. VISION™ allows the invoiced amount for each line item to be configured for each individual site if desired.

It’s common practice to configure the EDC so that the investigator sign off on each invoice activates submission. This serves as an indication that the investigator has reviewed and approved each invoice. Did you know that VISION™ can also be configured so that the invoice can be annotated when payment has been made? Study monitors and project managers can easily see the real-time status of all invoices using VISION’s reporting tool. 

Streamline trail administration activities by using this powerful feature! Sponsors/CROs who don’t take advantage of integrated invoicing often tell us they wish they had used it.

Learn more about integrated invoicing in this International Animal Health Journal article. 

Schedule a Demo

How NOT to Design eCRFs

There are so many ways to design electronic CRFs. Perhaps by looking at how NOT to design them, we can come up with some fresh ideas for how to make your next study a smashing success.

Fail to consider how well the forms will function on handheld devices.

The sun us setting on big screens and desktop workstations. Soon a new day will dawn, and the sun will shine solely on small screens. They provide mobility and greater access across the board. They are the key to conducting business in the information age.

Take, for example, form layout. Regardless of whether you are viewing it in landscape or portrait, a long list of fields is not conducive to the thought-processes of the human brain. Fields need to be grouped together in a way that makes sense to the person filling it out. And news flash: the person filling out the forms for your study is guaranteed to be relying on a human brain.

Put simply: don’t shortchange the design process of the study build in favor of a quick turnaround. You will thank yourself later when you are parsing through the raw data for usable statistics.

Require users to navigate extensively to do their jobs.

Do not bury important fields at the bottom of the form. Don’t force your sites to have to dig deep to get what you need. Cater the form configurations to quick and easy navigation.

Employ checkboxes instead of radios.

Simplify the investigators’ jobs before they even begin. Give them less options when possible. Dummy-proof your study to the point where the patients themselves could fill out their forms.

Don’t provide options for “Neither,” “N/A,” “Not Done,” or “Other.”

Bottlenecks happen when a field is lacking necessary options. The investigator will simply leave it blank if they do not see the option they need. Then the monitor goes in and queries the blank field. The investigator responds that they didn’t perform that particular test. The issue gets shunted up the line until it gets to Prelude and a mid-study update is requested to add the pertinent option to the field in question. This takes time, causes confusion, and costs extra support hours, depending on the complexity of the request. There will always be mid-study updates. It’s a normal part of the process, but some things can be prevented. Do your best to predict issues before they happen, and your study will run much more efficiently. Just don’t overthink it…

Assume that the data will be entered in a certain order.

After taking into account all of the above, we’ll leave you with this: You can’t predict everything. Put as much thought into your eCRF’s as you can, but first you have to learn the difference between what you can control and what you cannot. Providing a radio in place of a list of checkboxes is all well and god, but don’t assume they will fill out the first item on the form first. Don’t go overboard with field suppressions and calculations. Try to think the way a clinical would. That’s all you can do.

 
 

More

How Can the Dynamic Drop-Down Menu be Utilized in a Study?

VISION’s user-friendly tools for customizing forms includes a handy tool known as the dynamic drop-down. This deceivingly simple field packs a lot of punch. While you can leave the drop-down menu as just that, a menu and nothing more, did you know that you can also use this menu to populate other fields or even populate it from other fields?

A great place to use this tool is on the Adverse Events and Concomitant Medications forms, so that the two can communicate with each other. If a con med gets administered to a subject due to an adverse event, both need to be documented. Using a dynamic drop-down menu on each form for the relevant subject saves a great deal of time and streamlines documentation. Once it is noted on the con med form that a medication was administered after an adverse event, then a menu appears with all previously entered adverse events for that subject. Simply select the correct event, and now the medication and adverse event are linked. Vice versa, If an adverse event required the administration of a medication in a subject, then you can select from a drop-down menu on the adverse events form all previously entered con meds.

This tool opens the door to many more opportunities for customization and, therefore, simplification of data-entry. Signature drop-down menus can either be populated from another field, i.e., from a list of names, or be role-based, meaning the names of every user who has been assigned a specified role will appear as an option. The menu for the reason a subject was withdrawn can be pre-populated conditionally, e.g., only if the subject was euthanized. This would save the investigator time as there would be no need to answer a slew of unnecessary questions to close out a patient. The transcribed CRF form features a drop-down menu that can be based on all forms or form groups, or it can include or exclude specific forms or form groups. Dynamic drop-downs can even communicate between subjects and sites, e.g., when updating con med and adverse event dictionaries.

Do you have a need for any other dynamic features? Let us know!

 
 

More

Feedback and SRD Field Spec as Story Tellers of the Study Build

The study build is the most volatile and, therefore, the most important part of the study’s life cycle. Keeping a good record of the build gives the rest of the study a fighting chance at success. It’s a time for testing, training, re-testing, amending, testing and retesting again. Did we mention it’s a time for testing? Changes get added and reverted then added back in, the final protocol may not be ready, there are usually multiple people requesting updates to study forms, sometimes conflicting with each other. It is important to be able to see exactly when requests were made and by whom.

This “story” of the study build has a major impact on the study once it goes Live and after it has been completed. It even affects future studies. Being able to see all in one place where the build went right and where there is room for improvement makes site-training easier, it provides a starting point for future study builds, and it streamlines the development of future protocols.

The Prelude field spec and feedback features are the most powerful tools for telling this story. The field spec allows the team to see in a nutshell how every form and field is set up. If they are unsure the effects of a calculation or constraint on a specific field, they can go directly to the form in question and test it. Then they can add feedback directly into the system if they feel a change is needed. From there the request goes through the feedback cycle until it is resolved. Then it is tested again. Prelude provides more feedback categories than any other EDC provider for added clarity and efficiency.

Each team member can use these tools to see exactly what changes have been requested, which changes have been approved, and the completion status of the approved changes. They can view at a glance all roles, permissions, constraints, calculations, etc., to find everything they need to know about the progress of the build, and they can view a succinct record of the Prelude team’s responses to each feedback item. Furthermore, the audit trail provides information about who left what feedback or query and when. In this way, Prelude offers a full package of features to streamline the build process and keep a thorough record each study’s build.