COA Licensing: What to Confirm Before Building an eCOA Form

Before an electronic clinical outcome assessment (eCOA) form is built, confirm with the copyright holder or licensing distributor whether the planned use is permitted. The checks below are contractual and differ by instrument. This is an operations guide for study startup, not legal advice. Where a study-specific license is required, read the agreement against six questions: (1) electronic administration on every planned mode and device, including any screenshot-review agreement, eCOA library license, or electronic-administration permission that licensor names; (2) the complete instrument, not only the questions, because the U.S. Food and Drug Administration (FDA) 2009 patient-reported outcome guidance treats an instrument as the means of capturing data plus the documentation that supports its use; (3) every language the protocol needs, including whether a listed translation is a validated version and whether the sponsor may commission a missing language; (4) scope fields that match the protocol—study identity, participants, administrations or visits, duration, and territories—because activity outside those fields is not licensed use; (5) who must sign, including a vendor undertaking if a technology provider will see source files; and (6) written confirmation that wording, layout, response scale, and recall period will not change without the copyright holder's prior approval. A license is permission under that holder's terms. FDA does not license instruments, and an approved modification still needs fit-for-purpose evidence for the context of use. Some measures are offered without a royalty for a defined single use, including English and Spanish PROMIS and Neuro-QoL for individual research or individual clinical use; commercial use, modification, translation, and many electronic implementations still need permission. Distributors that describe failed licensing name intellectual-property exposure, delays to site initiation and first patient in, protocol amendments when a planned endpoint cannot be collected as licensed, and invalid results from the wrong version.

Patient-reported, clinician-reported, observer-reported, and performance outcomes used as trial endpoints are usually copyrighted works. Selecting one does not transfer ownership to the sponsor. Permission is instrument-specific. For many commercial questionnaires it is a study-specific license with the copyright holder or the designated distributor. Mapi Research Trust's licensing note treats that license as the route to permission of use. The exception that matters operationally is narrow: HealthMeasures states that all English and Spanish PROMIS and Neuro-QoL versions, and some NIH Toolbox self- and parent-proxy instruments, are available without licensing or royalty fees for individual research or individual clinical use. Commercial users must seek permission regardless of purpose, and those terms still forbid unapproved modification or translation.

Where a license is the permission, Mapi Research Trust describes five rights a study-specific agreement can include. The list is that distributor's account of what a license may grant. It is not a warranty that every contract, or every other licensor, contains each item:

1. Study-Specific Administration Rights: The legal permission to administer the questionnaire to research participants enrolled in the named clinical protocol, across specified investigational sites and geographical territories.

2. Access to Master Source Files: Authorized delivery of the official master instrument in its original language, alongside certified existing language versions and authorized layout specifications.

3. Derivative Creation Permissions: Permission, when the agreement includes it, to develop an additional version the study needs, such as a new translation or an electronic implementation. A paper-use license does not imply that permission.

4. Scoring Syntax and Interpretation Manuals: Access to the scoring method and interpretation guidance the copyright holder designates. A file of questions without those materials is not the full instrument in FDA's 2009 definition, and missing-item rules or normative tables are included only when the licensor actually provides them.

5. Regulatory and Publication Rights: Permission to disseminate and publish study results in the scientific literature, when the agreement includes that right. What may be said in a submission or a label is a separate regulatory question.

A license is not a transfer of copyright, and it does not give the study team editorial discretion. The limit is real, and it is not one identical sentence at every licensor. Mapi Research Trust states that licensed users cannot modify content or layout, on paper or electronically, without the copyright holder's approval. The published conditions of use for the Fatigue Symptoms and Impacts Questionnaire–Relapsing Multiple Sclerosis (FSIQ-RMS), one ePROVIDE instrument rather than a rule for the whole catalog, say the user is not authorized to modify, retype, translate, copy, or otherwise duplicate the questionnaire without further written permission. HealthMeasures says users may not adapt, alter, amend, abridge, modify, condense, make derivative works of, or translate its instruments without prior written permission. EuroQol requires prior written consent to alter or translate EQ-5D. IQVIA reviews electronic migrations because a format change can affect whether respondents answer as they did on paper. Splitting one response scale across screens, or turning that scale, is a layout change of the kind these terms put behind written approval. A smaller display choice can fall on the same side of the line. Until the copyright holder agrees in writing, that change is outside the license.

A frequent operational breakdown is an agreement that delivers the questions and not the scoring method. In the December 2009 guidance on patient-reported outcome measures used to support labeling claims, FDA defines an instrument as a means to capture data, such as a questionnaire, plus all the information and documentation that supports its use. That generally includes clearly defined methods and instructions for administration or responding, a standard format for data collection, and well-documented methods for scoring, analysis, and interpretation of results in the target population. When the contract does not include the scoring method and administration instructions, the sponsor does not yet hold the instrument FDA described. Florence Mowlem's January 2026 article in Applied Clinical Trials uses "buying blind" for a different, earlier problem: copyright holders often withhold the official measure until the license is executed and paid, so teams assess scientific fit and technical feasibility without the instrument in hand. The same article argues that a minimal package, aligned with FDA's instrument definition, should include the licensed COA, scoring information, and administration instructions. That is an argument about what should be visible before signature. It is not a report that scoring gaps are routinely discovered after enrollment.

Most sponsor-run outcome collection is now electronic, and a paper license does not automatically cover that build. Mapi Research Trust's 2024 note on eCOA licensing and screenshot review says that system design and translation work typically cannot start until the licensing agreements are in place, because of copyright, and that some copyright holders set strict electronic-use conditions. Many of the instruments were developed on paper. Moving them onto a screen changes pagination, line length, and how a response scale is presented. Those are the changes screenshot review is meant to catch.

Licensors manage electronic implementation through widely divergent, enforceable governance frameworks. Clinical operations leaders must review the specific contractual mechanisms governing their selected instrument family:

• ePROVIDE / Mapi Research Trust Model: This is not a single rule for every instrument Mapi distributes. On FSIQ-RMS, the published conditions of use require a license and a user fee for commercial and funded academic users, and a screenshot review agreement for commercial users. Examination copies on that page are limited to judging suitability; they cannot be used in research or clinical practice. Mapi's own eCOA note describes screenshot review as the check that the electronic form still represents the paper instrument. Read the instrument page: other ePROVIDE measures name different reviewers, and some do not make screenshot review mandatory.

• IQVIA COA Licensing Framework: IQVIA's current COA page says a fully executed license is required before use of any IQVIA COA or scoring algorithm, including funded and unfunded academic research. Licenses are per use—for example, per study or per registry—for a set duration. For an electronic migration, the user provides screenshots for review and approval on every device on which the COA may be deployed, and IQVIA's examples are tablet, smartphone, and computer. An eCOA vendor cannot add an IQVIA COA to a library until an eCOA library license agreement is executed. IQVIA also states that users may not develop new translations themselves.

• EuroQol Registration and Universal Digital Format: From 6 April 2022, new EQ-5D license agreements use the universal digital versions rather than device-specific files. Users register each study. After registration, non-commercial academic, educational, public-health, and similar use is free of a license fee. Licensees and vendors create the digital representation from EuroQol's documents. The office no longer reviews every reproduction, though it can still help if asked. For commercial users it requests implementations selected at random as a quality check. A deviation from the representation guidelines is at the licensee's and vendor's risk. This is the counter-example to a universal pre-launch screenshot gate.

• HealthMeasures terms, and HEAP when it applies: English and Spanish PROMIS and Neuro-QoL, and some NIH Toolbox self- and parent-proxy instruments, are publicly available without licensing or royalty fees for individual research or individual clinical use. Commercial users must seek permission for any purpose. HealthMeasures' services page says that when a static form is administered digitally outside its licensed platforms, the HealthMeasures Electronic Administration Permission (HEAP) supplies a permission letter and a screenshot review so the electronic form keeps the measure's validity. New translations require a license, and HealthMeasures manages that translation path. Confirm the current electronic terms for a non-commercial research build before treating HEAP as automatic for every file.

When a build starts from an examination copy, it starts outside the permission those copies grant. On the FSIQ-RMS conditions of use, an examination copy is only for judging whether the questionnaire is suitable. It cannot be used in research or clinical practice, and it cannot be distributed to others. If the later agreement requires screenshot review, or refuses a screen the team already coded, the build has to be redone and the user-acceptance testing repeated. EuroQol is the reminder that not every licensor inserts that review before launch.

graph TD
  subgraph LegalTrack["Legal & Licensing Track"]
    L1["Identify Copyright Holder & Model"] --> L2["Submit Study Scope & Request Quote"]
    L2 --> L3["Execute Master License & Vendor Undertakings"]
    L3 --> L4["Receive Master Source Files & Scoring Manual"]
    L4 --> L5["Execute Screenshot Review Agreement"]
  end
  subgraph BuildTrack["Technical Build Track"]
    B1["Review Protocol Schedule of Events"] --> B2["Draft Screen Wireframes & Logic Flow"]
    B2 --> B3["Configure eCOA Form in Sandbox"]
    B3 --> B4["Generate High-Resolution Screenshots"]
  end
  L4 -.-> B3
  B4 --> M1{"Licensor Screenshot Approval Gate"}
  L5 --> M1
  M1 -- "Rejection / Layout Defect" --> B3
  M1 -- "Formal Sign-Off" --> B5["Execute Multi-Language UAT"]
  B5 --> B6["Production Release to Sites"]

Global multi-center clinical trials require verified linguistic versions across all participating countries. However, the assumption that an executed license automatically provides turnkey translations is among the most pervasive causes of site initiation delays. Study startup teams must navigate three distinct translation-related contractual checkpoints:

First, separate a certified translation from a file that merely exists. Distributors list language versions that have not all been through the same linguistic validation. IQVIA, for the translations it develops, describes linguistic validation with cognitive debriefing, and it will not let the user create a new translation alone. Confirm the status of each file the protocol needs with the distributor. The methods for linguistic validation and cultural adaptation are a different decision, covered in COA translation and cultural adaptation methodologies.

Second, a missing language is not a gap the sponsor can fill quietly. Mapi's licensing note treats permission to develop a new translation as a right the license may grant, not a right that comes with selecting the endpoint. IQVIA states that users may not develop new translations on their own, and that a fully executed license must be in place before IQVIA starts that work. HealthMeasures requires a license for a new translation and manages the vendor path. Read the ownership clause before commissioning anyone: new translations are often controlled by the copyright holder, and deploying an unauthorized translation is not use of the licensed instrument.

FSIQ-RMS lists Mapi/ICON Language Services as the recommended vendor for translation work. IQVIA charges a translation fee when it must develop a new linguistically validated translation or translate a modification it has approved, and it does not permit the user to develop that translation alone. An outside agency is a problem on those terms because the copyright holder can refuse the file. It is not a rejection rule for every instrument in every catalog.

A COA license is permission with boundaries the agreement actually writes down. Mapi Research Trust tells licensees to check that use still matches the licensed number of patients, schedule of events, translations, and mode of administration. EuroQol fees and permissions follow the study registration: the office then states the terms and any fee. A later protocol change does not update the license by itself.

EuroQol's registration determines whether a fee applies. The obtain-EQ-5D page says fees follow the information supplied on that form and the user-license policy, registering does not commit the user to buy a license, and non-commercial academic, educational, public-health, and similar use is free after registration. HealthMeasures does not charge a royalty for the defined single-use case described above, and IQVIA says some academic and individual-clinical requests may qualify for a waiver or discount. A protocol amendment that adds visits, countries, or languages still has to be mirrored in the license, which is the same change-control problem discussed in protocol amendment change control workflows.

The failure mode is easier to see in a hypothetical study than in a list of clauses. Nothing below is a reported trial. A sponsor plans a Phase 2b study of an investigational oral therapy in relapsing neuroinflammatory disease at 40 sites in the United States, Germany, France, Italy, and Spain.

The study protocol specifies a key secondary endpoint: patient-reported fatigue severity and daily functional impact measured via a proprietary, copyrighted 7-day recall symptom-and-impact PRO instrument. The trial schedule of events dictates administration at Screening, Baseline, and Weeks 4, 8, 12, 16, 20, and 24, establishing a planned volume of 8 administrations per patient across an enrolled cohort of 250 participants (2,000 total scheduled administrations).

The Operational Shortcut: Facing a first-patient-in date that will not move, the clinical operations lead sees that the distributor has not yet executed the license. To keep the build moving, the lead sends the eCOA vendor an examination copy that was requested only to judge whether the instrument belonged in the protocol, and tells the vendor to configure the form.

The Three Latent Development Errors: During the accelerated six-week software build, three critical structural misalignments were embedded into the application:

1. Unauthorized Layout Modification: The questionnaire contained a core 6-point Likert response grid assessing cognitive fatigue. To prevent horizontal scrolling on handheld smartphones, the eCOA developer divided the question into two separate screen cards: Card A presented options 1 through 3, and Card B presented options 4 through 6, joined by a 'Next' button.

2. Unverified Language Assumptions: The study team commissioned an independent local translation agency to translate the instrument into German, French, Italian, and Spanish, assuming the executed license would grant blanket localization rights upon payment.

3. Unlicensed Extension Visits: Midway through system configuration, Protocol Amendment 1 introduced an optional 12-week open-label safety extension featuring three additional monthly assessments (Weeks 28, 32, and 36). The engineering team added these visits to the eCOA schedule without notifying legal or licensing specialists.

The Confrontation at License Execution: When the distributor returned the executed commercial license, the build and the contract did not describe the same study:

• The agreement covered US English electronic administration only, capped strictly at 2,000 administrations. European territories and languages were omitted pending execution of country-specific schedules.

• The distributor enforced a mandatory Screenshot Review Agreement, requiring all digital screen layouts across all target languages to be reviewed and approved prior to production release.

• In the scenario, the distributor refused the two-card split. The conditions of use did not allow that layout change, and the distributor required the response scale on one screen. The example does not include a study showing that the split changed response distributions.

• In the scenario, the distributor refused the sponsor-commissioned European translations and required the official versions through its named language vendor.

The Operational Fallout: When the agreement finally came back, European site activation stayed blocked while official translations were licensed, rebuilt, and put through screenshot review. The English build was rolled back to a single screen and had to be retested before release. Electronic-record controls for that rebuilt form are a separate evidence question, covered in the eCOA Part 11 evidence guide. The sponsor also had to amend the license so the three extension visits were inside the authorized administration count: 250 participants times 11 time points is 2,750, against a license written for 2,000. Records captured on the split layout were not the licensed instrument, so that window could not be used as the planned secondary endpoint without a justification the agreement did not provide.

Copyright permission and regulatory fitness answer different questions. An executed license, or even written approval of a layout change, meets the copyright holder's conditions. It does not establish that the instrument is fit for the trial's context of use.

FDA's public COA FAQ addresses how to seek advice and how qualification works. It does not address instrument copyright or commercial licensing. The agency does not grant COA licenses. Qualification is voluntary: the FAQ states that a COA does not need formal regulatory qualification to be used successfully in drug development, including to support labeling claims. The sponsor still has to support the context of use with evidence the review division can assess.

FDA's fit-for-purpose question sits in a different document from the license. The final Level 1 guidance, Patient-Focused Drug Development: Selecting, Developing, or Modifying Fit-for-Purpose Clinical Outcome Assessments (PFDD Guidance 3). The guidance page is dated October 2025. It is FDA's current thinking on selecting, developing, or modifying a fit-for-purpose COA. It does not require a copyright license, and a license is not a finding that the instrument is fit for a particular trial. What counts as adequate evidence for a context of use is the subject of fit-for-purpose COA evidence requirements. If a copyright holder allows a wording change or the removal of an item, that permission does not replace evidence that the modified instrument is still fit for the context of use.

Electronic migration has its own methods literature. In the January 2024 issue of Value in Health, Mowlem and colleagues, writing for the eCOA Consortium, consolidated recommendations for electronic implementation and migration of patient-reported outcome measures. The abstract states the aim as a faithful migration that preserves the integrity of the measure. Whether a move across web, tablet, and phone also needs new comparability evidence is a separate measurement decision, discussed in eCOA mode measurement comparability.

Run the confirmations before configuration when the licensor's terms say the build waits on the agreement. Mapi describes that wait as typical, not as a rule that every copyright holder imposes. Where a measure is free of a royalty for a defined single use, the version, electronic-permission, translation, and no-modification checks still apply:

1. Copyright owner and distribution channel: Identify the rights holder and the distributor that actually grants permission, such as ePROVIDE/Mapi, IQVIA, EuroQol, or HealthMeasures. Do not assume a paid study license is required until that page is read.

2. Complete instrument package: Confirm the deliverables include the questions, the scoring method, administration instructions, and any interpretation guidance the licensor provides. FDA's 2009 definition of an instrument includes that supporting documentation. Ask for the scoring materials the licensor actually supplies, and do not assume the package includes missing-item rules or imputation code.

3. Electronic administration rights: Check that the permission covers the planned devices and modes, including provisioned tablets, web, or bring-your-own-device phones if those are in the protocol. Execute a library or screenshot-review agreement only when that licensor requires one. For HealthMeasures, commercial use needs permission, and the services page routes digital administration of static forms through HEAP. Confirm the current electronic terms before treating that filing as automatic for a non-commercial research build.

4. Languages and translation authority: Match planned countries to the validated files that exist. If a language is missing, get written permission to translate it, and check whether that instrument names a vendor. FSIQ-RMS recommends Mapi/ICON Language Services. IQVIA does not allow users to create translations themselves.

5. Protocol scope: Compare the agreement with the schedule of events: enrollment cap, visits, unscheduled assessments, and the license term through database lock. The schedule itself should already be specified in the protocol. How those endpoint definitions are written is covered in how ICH M11 structures protocol endpoint definitions.

6. Signatories: Confirm which parties must sign. That can include the sponsor, the contract research organization, the eCOA vendor, and a translation vendor. Ask whether the vendor may see source text before execution, and do not send files until the undertaking the licensor requires is signed.

7. Screenshot review, when it applies: If the licensor requires screenshot review, put that cycle on the path to first patient in. Do not hold a EuroQol build for a review the office no longer performs on every reproduction.

8. No unapproved changes: Tell the build team that wording, layout, response format, and recall period stay as licensed unless the copyright holder approves a change in writing, and name who escalates when a screen will not fit.

A license that matches the protocol keeps collection inside the copyright holder's terms. It does not make the endpoint fit for purpose. Where English or Spanish PROMIS or Neuro-QoL is used for individual research or individual clinical use, the royalty may be zero, and the version, electronic-administration, translation, and modification checks remain.