Universal API Implementation Guide - Local Development build (v1.1.20) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Release 2026 MAR

Announcements

• FDA Approves Genentech’s Venclexta® Plus Acalabrutinib Combination Regimen for Previously Untreated Chronic Lymphocytic Leukemia on 2/19/2026. Click HERE for more information.
• PENDING DATE: New Copay indication for Venclexta questionnaire

MARCH 20 RELEASE

For Patient Foundation enrollments, the linkId "denied-coverage" will only be required in bundle if patient has insurance.

BEFORE:

"linkId": "denied-coverage",
"text": "If insured, has the patient's insurance denied coverage for this medication?",
"type": "choice",
"enableWhen": [
    {
    "question": "applied-for-pf",     
    "operator": "=",     
    "answerBoolean": true
    }
    ],
"enableBehavior": "all",
"required": true,
"repeats": false,
"answerOption": [
  "valueString": "Yes",
  "valueString": "No"]	

UPDATED to:

"linkId": "denied-coverage",
"text": "If insured, has the patient's insurance denied coverage for this medication?",
"type": "choice",
"enableWhen": [
    {
    "question": "has-insurance",     
    "operator": "=",     
    "answerBoolean": true
    }
    ],
"enableBehavior": "all",
"required": true,
"repeats": false,
"answerOption": [
  "valueString": "Yes",
  "valueString": "No"]

MARCH 6 RELEASE

Bug Fix for Partial Population of Prescriber Form

Issue Description:

Issue:
An issue was identified where certain data fields on the Patient Foundation Prescriber Form were failing to populate, even when the required data was correctly present in the incoming FHIR enrollment bundle.

Business Impact:
Case Managers and Patient Foundation specialists perceived this as missing information. This led to unnecessary outreach to Healthcare Providers (HCPs) to "re-collect" data that had already been submitted, causing administrative friction, delays in processing, and bad customer experience.

Resolution:
The mapping logic within the form has been corrected to ensure that compound product names located in the MedicationRequest.medicationCodeableConcept.coding.code element are processed accurately. This fix ensures the form populates correctly for all compound product names.

Technical Fix & Requirement:
To ensure 100% data fidelity on the Prescriber Form, all compound product names must follow the formatting logic:

1. Delimiter: Compound product names must use dashes (-) between each word
2. Constraint: Spaces are not accepted within the code element for compound products.
   

Example:
Correct format: rituxan-for-oncology
Incorrect format: rituxan for oncology, rituxanforoncology

Formatting Standard:

{
  "resourceType" : "MedicationRequest",
  "id" : "8ca2e059-e448-445a-be13-bbacca49b452",
  "meta" : {
    "profile" : [
      🔗 "https://fhir.developer.gene.com/StructureDefinition/uapi-medicationrequest"
    ]
  },
  "text" : {
    "status" : "extensions",
    "div" : ""
  },
  "status" : "active",
  "intent" : "order",
  "medicationCodeableConcept" : {
    "coding" : [
      {
        "system" : "https://fhir.developer.gene.com/CodeSystem/uapi-product-name",
        "code" : "rituxan-for-immunology",
        "display" : "Rituxan for Immunology"
      }
    ]
  },

Validation:

Bundles containing compound medications that include spaces or lack the required dashes will result in partial Prescriber Form population.

List of Compound Product Names can be found on ValueSet: UAPI Value Set - Product Name page