Tag Archives: Certified Study Administrator

CDISC/CDASH Standards at your Fingertips

A standard database structure using CDISC (Clinical Data Interchange Standards Consortium) and CDASH (Clinical Data Acquisition Standards Harmonization) standards can facilitate the collection, exchange, reporting, and submission of clinical data to the FDA and EMEA. CDISC and CDASH standards provide reusability and scalability to EDC (electronic data capture) trials.

There are some defiance in implementing CDISC in EDC CDMS:

1. Key personnel in companies must be committed to implementing the CDISC/CDASH standards.

2. There is an initial cost for deployment of new technology: SDTM Data Translation Software, Data Storage and Hosting, Data Distribution and Reporting Software.

3. It can be difficult to understand and interpret complex SDTM Metadata concepts and the different implementation guides.

4. Deciding at what point in a study to apply the standards can be challenging: in the study design process, during data collection within the CDMS [CDASH via EDC tools], in SAS prior to report generation [ADaM], or after study completion prior to submission [SDTM].

5. Data management staff [CDM, clinical programmers], biostatisticians, and clinical monitors may find it difficult to converge on a new standard when designing standard libraries and processes.

6. Implementing new standards involves reorganizing the operations of (an organization) so as to improve efficiency [processes and SOPs].

7. Members of Data Management team must be retrained on the use of new software and CDISC/CDASH standards.

standards8. There are technical obstacles related to implementation in several EDC systems, including 8 character limitations [SAS] on numerous variables, determining when to use supplemental qualifiers versus creating new domains, and creating vertical data structure.

Comments? Join us at {EDC Developer}

Anayansi Gamboa, MPM, an EDC Developer Consultant and clinical programmer for the Pharmaceutical and Biotech industry with more than 13 years of experience.

Available for short-term contracts or ad-hoc requests. See my specialties section (Oracle, SQL Server, EDC Inform, EDC Rave, OpenClinica, SAS and other CDM tools)

As the 3 C’s of life states: Choices, Chances and Changes- you must make a choice to take a chance or your life will never change. I continually seek to implement means of improving processes to reduce cycle time and decrease work effort.

Subscribe to my blog’s RSS feed and email newsletter to get immediate updates on latest news, articles, and tips. I am available on LinkedIn. Connect with me there for technical discussions.

Fair Use Notice: This article/video contains some copyrighted material whose use has not been authorized by the copyright owners. We believe that this not-for-profit, educational, and/or criticism or commentary use on the Web constitutes a fair use of the copyrighted material (as provided for in section 107 of the US Copyright Law. If you wish to use this copyrighted material for purposes that go beyond fair use, you must obtain permission from the copyright owner. Fair Use notwithstanding we will immediately comply with any copyright owner who wants their material removed or modified, wants us to link to their website or wants us to add their photo.

Disclaimer: The EDC Developer blog is “one man’s opinion”. Anything that is said on the report is either opinion, criticism, information or commentary. If making any type of investment or legal decision it would be wise to contact or consult a professional before making that decision.

Disclaimer:De inhoud van deze columns weerspiegelen niet per definitie de mening van {EDC Developer}.

Disclaimer: The legal entity on this blog is registered as Doing Business As (DBA) – Trade Name – Fictitious Name – Assumed Name as “GAMBOA”.

Advertisements

Where in the World is Ana?

First, I want to say thank you for reading my blog, connecting with me on LinkedIn or following whenever I go [thank you NSA].

Many of you, for months, have asked me if I was going to write more articles related to clinical trials. For sometime now, I have taking time-off from this EDC blog and concentrated on some other projects of equal importance. I will share some new insights and information as I get myself back on track.

So what is a girl who has a master’s degree in project management and computer networks doing as a programmer? It’s not that I didn’t like project management, per se. And entering in the IT network business years ago was quite difficult for girls like me in a world dominated by men. It’s basically that I didn’t find myself with the same passion for project management or computer networks that I have for programming and technology in general.

Because I am so interested in technology and programming, I tend to spend a lot more time than my peers in learning new technologies, and enhancing my existing skills. Many of my co-workers and ex-collega (Dutch) have commented on their admiration that my skill level is as high as it is, and that I am able to learn new technologies so quickly. But beyond just learning new technologies and APIs, I’m passionate about becoming a better overall programmer. Reason why in the last few months, I spent time learning IOs development (iPhone and Android apps). I am actually working on an app to ‘hack’ into my own car. 🙂 Well, not exactly. I want to be able to open my car and do some other basic command (like opening the garage door) using an APP.

Given my degree in project management, it should be clear that I have useful skills beyond the programming world. In fact, having a project management background has helped me interface with various groups in various organizations in which I’ve worked.

I have installed, maintained, and designed numerous relational databases and small networks. As a freelancer, I have worked in projects doing data analysis, project support and computer training.

Now you know a little about me personally. If you think I might be the type of developer you’re looking for, feel free to browse my resume and contact me.

Anayansi Gamboa
Resume / CV .

Comments? Join us at {EDC Developer}

P.S. I will be releasing some training videos / training material for several EDC tools in the near future including tips and best practices. Price has not been setup yet. All training will be web-based, password protected. If you wish to consult with me for a face-to-face training or on-site training, please contact me to discuss further.

Fair Use Notice: This video contains some copyrighted material whose use has not been authorized by the copyright owners. We believe that this not-for-profit, educational, and/or criticism or commentary use on the Web constitutes a fair use of the copyrighted material (as provided for in section 107 of the US Copyright Law. If you wish to use this copyrighted material for purposes that go beyond fair use, you must obtain permission from the copyright owner. Fair Use notwithstanding we will immediately comply with any copyright owner who wants their material removed or modified, wants us to link to their website or wants us to add their photo.

Disclaimer: The EDC Developer blog is “one man’s opinion”. Anything that is said on the report is either opinion, criticism, information or commentary, If making any type of investment or legal decision it would be wise to contact or consult a professional before making that decision.

Disclaimer:De inhoud van deze columns weerspiegelen niet per definitie de mening van {EDC Developer}.

Disclaimer: The legal entity on this blog is registered as Doing Business As (DBA) – Trade Name – Fictitious Name – Assumed Name as “GAMBOA”.

Professional Timeline – Clinical Programmer

Professional Timeline

Curriculum Vitae
CV

 

anayansi gamboa

Before Your Trial Goes Live – InForm FastStart

When EDC is used in a clinical trial, electronic case report form (e-CRF) data are defined to be the data that are manually entered into a computer by the patient or by the investigator’s staff.

CDISC defines e-CRF as a CRF in which related data items and their associated comments, notes, and signatures are linked electronically.

e-CRFs may include special display elements, electronic edit checks and other special properties or functions used for both capture and display of the linked data.

Prior to submitting a request – FastStart, you should throughly test your trial.

Technically speaking, FastStart requests ensures base is cooked when sending all UAT versions of the trial, Training and Production versions of the trial to Oracle implementation team. This will vary on the type of contract your company / sponsor has with them.

Your company or sponsor may have a setup of ‘Implementation’ instructions that will be provided to Oracle HSG (formerly PhaseForward) that includes all files, summary and instructions for each implementation. Some of these required files or special files are listed below.

Special Files:

Filename Contents
Customresources.XML Collects references to any html files that will be use to override standard InForm functionality within the trial. Includes the visit calculator (VISITCALCULATOR.HTML) and confirmation of enrollment message (ENROLLMENTCONFIRM.HTML).
InsertUsers.XML User details
InsertSites.XML Site details
InsertSiteGroups.XML Links users with specific sites
InsertGroups.XML Defines the properties and contents of groups e.g. queries, items
InsertRightsGroups.XML Groups multiple access rights, with details of specific users that are assigned those rights.Also contains details of any overrides to default levels of access at item level
InsertSignCRF.XML Defines form to be signed and group who have access to sign
Crbaffadavit.TXT Affadavit text which appears when signing the eCRF (used at eCRF level). The text is standard, but protocol number must be amended for each trial. NOTE: This file will be used for any trials using casebook level signatures.
logo.jpg Your company logo
EnrollmentOverride.htmlHomedefault.html Here you can modify your trial name

The eSignature is a replacement for the Investigator’s physical signature (paper form). This file captures confirmtion from the Investigator that he has reviewed and confirmed the information on each eCRF is accurate. This Affidavit text contains something like ‘I, Principal Investigator, for study 9999999, confirm I have reviewed this CRF form….’

Investigator– 21 CFR 50.3(d) defines the investigator as “The individual who actually conducts a clinical investigation – i.e., under whose immediate direction the test article is administered.”

Some recomendations about eSignature can be further research on Secure Access For Everyone (SAFE) standards. The goal is that once the investigator is credentialed by SAFE, his/her identity and electronic signature can be used by all SAFE compliant sponsors.

InsertUsers File

Training must be provided to sponsors users prior to granting access to an InForm trial. For example, CRAs will need to be well trained on all aspects of the EDC system in order to provide coaching for the investigator. This file documents all sponsors and site staff users within each clinical trial.

Easy, wasn’t it? Again, build your trial and test to make sure all files were cooked and working as expected. Log into your trial and ensure that the special files appear correctly. Enroll a subject to ensure the enrollment confirmation screen appears and, if used in the trial, the visit calculator appears.

Reference:

Electronic Clinical Data Capture, Position Paper Revision 1, May 1, 2005

How to manage Sites and Users in InForm Trial

Your comments and questions are valued and encouraged.
Anayansi Gamboa has an extensive background in clinical data management as well as experience with different EDC systems including Oracle InForm, InForm Architect, Central Designer, CIS, Clintrial, Medidata Rave, Central Coding, OpenClinica, Open Source and Oracle Clinical.

Open Source versus Commercial Systems

Types of EDC Systems: Commercial and Open Source

EDC systems can either be standalone databases on a desktop computer/server supporting a single site or they can be Web based with the ability to support multisite studies [1, 3, 27]. Based on the business model utilized and the licensing-distribution method followed, they can be broadly categorized as commercial and open-source EDC systems. Commercial EDC applications are usually developed by a for-profit company or developer group. They charge for user licenses with or without annual support contracts while the source code is not published. Some examples include Oracle® Clinical (Oracle, USA) [31], Clinsys® (Jubilant Organosys, USA) [6], InForm™ (Phase forward, USA) [22] DATATRAK Electronic Data Capture (DATATRAK, USA) [8]. On the other hand, free and open-source software are applications developed by a single or group of developers, often as a voluntary effort. The application and its source code are published online and users can download them without any cost. Some examples include DADOS P (Research on Research group, Duke University, USA) [7] OpenClinica® (Akaza Research, USA) [30], Redcap (Vanderbilt University, USA) [34] and TrialDB (Yale University, USA) [43] .

opensource_commercial

Commercial EDC Systems

Commercial EDC systems can either be purchased as a software package or through a license with periodic support either included in the package or charged separately. In some cases, users have to pay a one-time license fee while in other cases users can renew their license periodically. Troubleshooting and guidance are usually provided under support plans while bugs in the application are rectified and released under regular updates.

Commercial EDC applications are usually easy to use in light of the quality of documentation and customer support extended to users. Well-designed interfaces are responsible for their user-friendly design. Multiple levels of user access, security, adherence to industry and regulatory standards, support for the design of eCRF’s, data entry, and management are features common to many commercial EDC applications. Some of them may also be able to generate reports, for example, DATATRAK One™ (DATATRAK international Inc, USA) [8], Entrypoint Plus® (Phoenix Software International Inc, USA) [10], and CliniProteus (Roskamp Bioinformatics Core, USA) [5]. Although standalone EDC systems are prevalent, they are increasingly being offered as a part of a complete clinical trial management system (CTMS). For example Oracle Clinical and InForm are offered as a part of a larger CTMS.

Despite the benefits, commercial EDC systems are expensive [13] and frequently non-customizable. They have been considered inadequate in context to the needs of healthcare stakeholders (clinicians, administrators, and patients) [46]. Given the variety of clinical practices and research methods used, commercial EDC systems may not fit into the workflow at each clinical/research site, thus having implications on their effective and efficient use. Many of them do not support interoperable data standards, i.e. it may not be possible to merge data exported out of one EDC with data exported from another EDC system or research/clinical application. As a result data from multiple studies or sources cannot be merged and utilized for answering research questions. Since the source code is not released, users must depend on the developer group or vendor for customization and support-related requirements. This limitation is frequently referred to as “vendor lock-in,” which makes further development and maintenance of commercial EDC an expensive effort.

We reviewed the web to identify some of the prominent and popular commercial EDC systems. They include Oracle® Clinical, InForm™ and Rave® (Table 1). Among themselves they hold a larger share of the EDC market [3]. Other examples include DATATRAK and eTrials EDC (Merge Healthcare) [8, 11].

Oracle® Clinical [31] is a commercial EDC system for conduction of clinical studies and trials. It is a core component of an integrated eClinical research solution that integrates adverse event report reporting, thesaurus management, trial management and remote data capture features in a single application.

InForm™ [22] global trial management system delivers a variety of features essential for the effective and streamlined implementation of clinical studies and trials. It sports an impressive study setup page, scalability and has separate EDC and CDMS databases. Other features include an intuitive interface, streamlined workflow, reporting and analysis tools that help the study team to work more efficiently. It can also be seamlessly integrated with randomization, trial design, and medical coding modules.

The Rave® (Medidata solutions) [36] platform is another industry leader in EDC systems. It has an impressive study design tool that nullifies the need for programming skills. It offers a single, flexible and scalable platform that captures, manages and reports clinical research data. It also undertakes a balanced approach between ease of use, features and functionalities. It has the flexibility to interface with legacy systems, adheres to CDISC clinical data standards and sports a plugin for modifying the interface and functionality.

DATATRAK Electronic Data Capture has considerable market presence [8]. Its features range from patient data management, electronic forms, supports queries, alerts and visit scheduling and generation of custom reports. It is also equipped with custom checklists and workviews, configurable tools for data cleaning, real time statistical support and an integrated medical coding package.

eTrials EDC [11] is a web based application that collects, manages and analyzes clinical trial information in real time. It is a user-friendly yet robust application with an in-built workflow. It can generate reports and can easily integrate with data from other applications.

Despite being feature rich, scalable, secure and compliant to industry standards, these EDC systems are prohibitively expensive [13], thus limiting their use by individual investigators and users from developing countries that do not having adequate funding but are interested in research participation.

Open-source EDC Systems

Open and freely available source code released under open distribution licenses like general public license [14] is the defining feature in this category of EDC systems. Open source code generates a large community of users and developers that interact, modify, and enrich the source code over a period of time and report bugs and solutions, thereby enhancing the quality, features, and value of the EDC system. In order to sustain an open source license, developers usually charge for customization requests. The same is applicable to troubleshooting and support, which are usually delivered through a yearly contract or support plan. Thus, by providing free access to the source code and annulling restrictions on use, modification, and distribution, open-source EDC systems form an attractive alternative for users.

The availability of inexpensive (or free) open source EDC applications for individual physicians/researchers, departments, and institutes has the potential to improve clinical and research activities and enhance academic standards by reaching a wider audience. Since further development/customization and ownership costs are lower, institutional administrators can modify and adapt open-source EDC systems to suit their environment and workflow, thus ensuring the success of EDC implementation. User-friendly and simple interfaces, adherence to industry standard security protocols, customizability, interoperability, and low maintenance costs are some of the major benefits of open-source EDC systems. Additionally, the presence of user support groups and communities ensures continuing support.

Although open-source EDC systems have a unique mix of features, their adoption in healthcare organizations has been slow. Software cost and maintenance are not the only features that influence decision makers. For an institution/organization-wide implementation, decision makers usually prefer and opt for EDC systems that are easy to deploy, manage, and support. Not all open-source EDC systems qualify for the same. In addition, dependence on the developer community for support and updates may cripple the organization if the community stops being productive. It is possible to address this issue by hiring programmers who could work on further development and maintenance, But locating and training relevant workforce is a challenge as in many cases the background technology has a steep learning curve.

DADOS Prospective, OpenClinica® and Redcap are examples of open source EDC systems. DADOS Prospective is a Web-based application developed by the research on research group (RoR) [37] to support data collection activities among researchers, research groups, and research networks [7]. It enables users to replicate any case report form into an eCRF, collect data in single/multisite studies, and extract data in an interoperable format. It is compliant with Chapter 11, Title 21, Code of Federal Regulations [4] and Health Privacy and Accountability Act (HIPAA) guidelines for EDC. It can be used to streamline and support individual/departmental/institutional databases, registries, and single/multisite clinical/nonclinical studies and clinical at a low cost [28].

OpenClinica® [30] is an open source application that has both EDC and data management capabilities. As an EDC system, it not only facilitates collection, validation, and annotation of clinical data but also has features that allow study audits, reporting and data extraction.

Research electronic data capture—‘Redcap’ is an open source metadata driven application designed for the clinical and translational research target audience by Vanderbilt. Its features include: a streamlined process for building a database, an intuitive and secure data collection interface that supports data validation and automated data export in multiple formats. It also supports other advanced features such as branch logic and file upload. It is freely available to its consortium partners with a modest personnel investment of < 0.5 FTE that covers training and support activities [16, 34].

Source:http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3049639/

Articles from Clinical Orthopaedics and Related ResearcH
1Duke-NUS Graduate Medical School, Singapore, Singapore
2Research on Research Group, Duke University Medical Center, Durham, NC USA
3Department of Surgery, Duke University Medical Center, Box 3094, Durham, NC 27710 USA
4National Neuroscience Institute, Singapore, Singapore
Ricardo Pietrobon, Email: rpietro@duke.edu.
FAIR USE-
“Copyright Disclaimer Under Section 107 of the Copyright Act 1976, allowance is made for “fair use” for purposes such as criticism, comment, news reporting, teaching, scholarship, and research. Fair use is a use permitted by copyright statute that might otherwise be infringing. Non-profit, educational or personal use tips the balance in favor of fair use.”

Your comments and questions are valued and encouraged.
Anayansi Gamboa has an extensive background in clinical data management as well as experience with different EDC systems including Oracle InForm, InForm Architect, Central Designer, CIS, Clintrial, Medidata Rave, Central Coding, OpenClinica, Open Source and Oracle Clinical.

InForm vs Central Designer

InForm TM (Integrated Trial Management) System, is a web-based data entry system which builds an Oracle database for each individual clinical trial. InForm, supplied by PhaseForward and now part of Oracle line of products and services, is widely used across the pharmaceutical, biotechnology and CRO industry.

Central DesignerTM, also supplied by PhaseForward, is the tool used to design and build the eCRFs (electronic case report forms) and data entry rules for clinical trials.

Additional information can be found here: Oracle InForm

It is technically impossible to compare the two tools because they are very different.

The following table provides an overview of key differences:

informvsCD

Summary:
The introduction of Central Designer to the Clinical Trials has improved the overall EDC development time, deployment process and support company and industry standards. Next article, we will compare Central Designer with Medidata Rave.

End-of-Project Lessons Learned

Below is an example agenda for a half-day lessons learned meeting at the end of a project (sometimes called a Project Closeout Meeting). It includes:

  • who should attend.
  • meeting objectives.
  • meeting deliverables.
  • agenda items showing a suggested sequence of team discussion, brainstorming, and analysis by which the team can agree upon what went well on the project, what didn’t, and what should be done differently next time.

Meeting Objectives:

  1. Understand how this project performed against its original goals (time, resources, scope)
  2. Identify “lessons learned” and recommendations for future projects.
  3. Set actions to ensure lessons learned are considered during planning of next project.

The only way to avoid problems happening yet again in the future is carefully consider what went wrong and why, and make sure there is a way to transfer related recommendations forward

Deliverables from Meeting:

  • Report including:
    • Review and analysis of plan vs. actual milestone achievement and state of what we delivered vs. the original requirements
    • Team’s brainstorm list of wins and challenges
    • Team’s list of derived recommendations for achieving the wins and avoiding the challenges on future projects
    • Open issues list and action items
  • Key items will be turned into templates and checklists for use during projects.
Agenda Item Facilitator(s) Time
Introduction, agenda review, ground rules Stakeholder 5 min
Wins and challenges

Project retrospective: Review planned vs. actual on major milestones and how what we released mapped to original major requirements

Round-robin brainstorm: Go around the table and record a win or challenge from each person. Keep going until no one else has items to add.

Map back to major project issues—which challenges contributed most to milestone and Vision shortfalls? Which wins contributed most to what the project accomplished?

ALL

 

xx min
Create lessons learned recommendations

Wins: what do we think other projects should do to achieve these wins?

Challenges: how should future projects avoid each issue we identified?

Stakeholder xx min
Next steps

Review action items and finalize assignments.

Stakeholder xx min.

 

Reference:
Global Brain Inc.’s Quality Rapid Product Development QRPD methodology

4 Programming Languages You Should Learn Right Now (eClinical Speaking)

I am a strong believer that learning a new language makes you better at the others, but I am not a “learn to code” advocate since a foreign language (I know 3 languages and currently learning my 4th and I have a “to learn” language including Italian and Arabic, if I ever find some free time) or even music (I love to play drums) are equally beneficial. But if you want to obtain a job in the pharmaceutical industry, here are the list of programming languages you should learn:

  1. C#:

What it is: A general-purpose, compiled, object-oriented programming language developed by Microsoft as part of its .NET initiative.

Why you should learn it: If you are looking to become a Medidata Custom Function programmer or Oracle InForm EDC Developer then you should.

2. Python:

What it is: An interpreted, dynamically object-oriented, open-source programming language that utilizes automatic memory management.

Why you should learn it: If you are like me always looking to learn new technology, love Google platforms and perhaps want to become a Timaeus Trial Builder, you should learn it. It is used on a lot open-source technologies.

Everyone should learn to code

3. PL/SQL or SQL:

What it is: PL/SQL stands for Procedural Language/SQL.

Why you should learn it: If you are like me additive to databases then Oracle should be your choice. If you want to become an Oracle Clinical programmer or Database administrator, you should learn Oracle PL/SQL.

4- SAS

What it is: SAS stands for “Statistical Analysis System” (software). It is the most powerful and comprehensive statistics software available.

Why you should learn it: SAS skills are in high demand nowadays. If you are able to obtain the SAS Certification and a few years of experience in the Pharmaceutical industry, you will be in good shape. If you are new and looking for training there are several options available from SAS Institute to private vendors such as Clinovo to even learning on your own. I most warn you as it will be difficult to obtain a job without experience. Nevertheless, once you are in, it can only get better.

Remember that your job is not just to code but to solve real problems. Your ability to code covers a lot of range of skills: from critical thinking, problem analysis & solving, logic, etc.

So which one are you going to give a try?

Let me know what is your preference. Happy Programming!

The best thing about a boolean is even if you are wrong, you are only off by a bit.(Anonymous)

Anayansi Gamboa has an extensive background in clinical data management as well as experience with different EDC systems including Oracle InForm, InForm Architect, Central Designer, CIS, Clintrial, Medidata Rave, Central Coding, OpenClinica Open Source and Oracle Clinical.

Disclaimer: The legal entity on this blog is registered as Doing Business As (DBA) – Trade Name – Fictitious Name – Assumed Name as “GAMBOA”.

Source:
SAS Institute
Learn PL/SQL

How to Manage Sites and Users in InForm Trial?

So you created your first InForm Trial and now what? Before you can actually enter data into your trial, you need to set up a user management system which assigns permissions to different users in your system depending on their job “role”.

In InForm, this is accomplished by using a tool called ‘User Management Tool’ or simple UMT. This tool allows sponsor to manage sites and users once the trial have gone live. There may be many different user groups with different levels and ranges of permissions.

Creating an InForm Trial – UMT:

  1. Create your InForm trial in the UMT. I won’t go into details on how to actually do this and depend upon the contract agreement with the vendor (i.e. Oracle/PhaseForward); they will perform this task for you.
  2. Select Trial Version = latest InForm version (i.e. 5.0)
  3. Select Countries where this trial will take place
  4. Select Status. Each InForm trial has 4 main statuses.
    1. Fast Start = Pre-Go Live
    2. Fast Forward = Trial is now live
    3. Fast Lock = Trial is lock
    4. Decommission = Trial is completed/archived

Managing users and groups can be a tedious task but tools such as UMT makes them easier to manage.

Roles: Roles (e.g. CRA, PI, System Administrator, etc) are used to assign specific permissions to individual users or groups, typically to perform specific functions in the InForm system.

The system allows you to either manually enter a role or import using a template called ‘MUL’ or Masters Users List. If you decided to upload your rights and roles via MUL, the system will generate a log file. It is imperative that you check this file and check any errors before proceeding.

Once the roles have been added to the UMT, you need to approved them before you build your clinical trial. The system also comes with defaulted and approved rights and roles.

Another option available is to create what is called as ‘signature groups’. If you are familiar with Medidata Rave system, this is equivalent to checking the ‘Signature required’ box and setting the investigator signature in Architect project main page.

Common use of Signatures in clinical trials are at the form level (i.e. 1 signature per form or at the subject level or studybook = 1 signature per subject).

Item Groups: Items groups is used to overrides or restrict a particular user access to a form or field. This is equivalent to ‘Restrictions – View/Entry’ in Medidata Rave.

One good example of display override usage is the coding fields restrictions. If only Clinical Coders are allowed to view / entry data on those items, you will limit access to all roles but the coders role.

Here’s a snippet of the code in .XML:

<!–?xml version=”1.0″?>–>
<MEDMLDATA xmlns=”PhaseForward-MedML-Inform4″>
/*some other code goes here*/
<ITEMGROUP
GROUPNAME=”Hidden Coding Items”
GROUPDESCRIPTION=”Hidden Coding Items”>
<!– Insert ItemRef Names –>
<ITEMREF REFNAME=”PT_NAME”/>
<ITEMREF REFNAME=”HLGT_NAME”/>
<ITEMREF REFNAME=”HLT_NAME”/>
<ITEMREF REFNAME=”LLT_NAME”/>
<ITEMREF REFNAME=”SOC_NAME”/>
</ITEMGROUP>
</MEDMLDATA>

Two other important groups that you need to be aware of is the Query and the Report Groups. The former, as the name entails, allows a user to open, answer, reissue and close queries during the course of a clinical trial. The latter, allows a particular user to run reports.

For example, an Ad Hoc User can access Ad Hoc reports via Cognos. The roles associated to this group could be your project manager, Clinical Research Associate (CRA) or your Lead Data Manager (LDM/CDM).

Once you have completed your basic setup, you will need to prepare or cook those xmls files onto your clinical trial. The rights/roles we discussed needs to be in an approved status. You also want to make sure you ‘lock for QC’ or lock the trial to prevent anyone from making changes to already added sites/users.

Sites and Users marked for upload to InForm will automatically be cooked into your trial.

Last step we need to take is to generate the XML files by selecting the link ‘Generate InFormXML.’ Now, your UAT trial is created, your URL is set up and you are ready to perform User Acceptance Testing.

Remember to validate your XML files, especially if your clinical trial is running across several countries. I have found issues with foreign languages symbols or special characters entered in the UMT system. Avoid at all cost any special characters.

Source: User Management Tool Reference Guide from PhaseFoward

Your comments and questions are valued and encouraged.
Anayansi Gamboa has an extensive background in clinical data management as well as experience with different EDC systems including Oracle InForm, InForm Architect, Central Designer, CIS, Clintrial, Medidata Rave, Central Coding, OpenClinica, Open Source and Oracle Clinical.

Central Designer – Troubleshooting Tips

If an edit check or function fails to behave as expected, it is time to use your ‘troubleshooting’ skills. The following tips may help you when you are troubleshooting rules in InForm:

Rules:

  • check if rules are running
  • check the rule logic
  • check Rule Dependencies: a rule on a form has access to items on that form, but not other forms or other visits
  • check InForm machine’s Application Event Log

Though some vendors will correct major problems with their products by releasing entirely new versions, other vendors may fix minor bugs by issuing patches, small software updates that address problems detected by users or developers.

Check the release notes for Central Designer for known problems. The release notes provide descriptions and workaround solutions for known problems.
Remember that there is a report available you can run “Data Entry Rule Actions Report”. This report outputs all data entry rules in CSV format and can be formatted into an edit check specification documentation for QA testing.
A rule can be written in more than one way, which makes it difficult to impose any restrictions:
Scenario: Route item has 3 choices. OP, SC and IV. Query should fire if the user does not choose either OP or SC. This rule could be written in many ways:

–Value = route.Value

If (value == 3)

–Value = route.Value == 3

If (value == true)

–Value = !(route.Value == 3)

If (value == false)

–Value = (route.Value == 1 || route.Value == 2)

If (value == false)

–Value = route.Value !=1 && route.Value != 2

If (value == true)

Keep it consistent across the trial. Do not overuse the conditional statements when a simple range check should be program.

Note: Be aware that if you want to reuse a rule that uses data from a logical schema in another study, the other study must also contain the logical schema.

If you have explored most of the obvious possibilities and still
cannot get your rule / edit check to work, ask someone in your team to peer review the build.

 

  • unit test your code
  • context available for defining test cases
  • Site name, date/time, locale; Form associations; Empty values; Unknown dates; Repeating objects
  • test case results: Pass or Fail based on expected results
  • perform formal QA / QT

Remember to check the Event log via Control Panel -> Administrative Tools -> Event Viewer

Reference Document : Central Designer – Rule Troubleshooting.pdf

Your comments and questions are valued and encouraged.
Anayansi Gamboa has an extensive background in clinical data management as well as experience with different EDC systems including Oracle InForm, InForm Architect, Central Designer, CIS, Clintrial, Medidata Rave, Central Coding, OpenClinica, Open Source and Oracle Clinical.