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

Testing

Genentech Testing Process Overview

Genentech provides two environments for testing: QA (test) and UAT (stage). Before beginning the testing process, ensure you have access to both environments and are set up as a vendor on the Genentech side.

Initial Testing in Test Environment

• Begin testing in the Test environment.
• The Test environment includes “extended validations.” If there are any errors in the enrollment, it will return an error message detailing the missing or incorrectly formatted information. These "extended validations" are not present in production. Refer to the Validations page

Transition to Stage Environment

• Once testing in the Test environment is complete and you are nearing deployment to the Production environment, proceed to test in the Stage environment.
  
  

Preparation

• Before starting the testing, thoroughly review all requirements for the specific product or type of enrollment to ensure all necessary information is included.

• Use a validator app to validate bundle prior to submitting for testing. For example, you can use https://validator.fhir.org/ to check if your bundle follows basic FHIR standard, however, it won't validate Genentech's customized resources.

• Bundle creation cheat sheet: PENDING

Testing Availability, Support and Process

• All testing, including Genentech testing support, is conducted asynchronously, i.e. no live sessions or regular meetings required.
  
• Availability of test environments:
  
  • Weekdays: available
    
  • Saturday: not available
    
  • Sundays: available starting 5a UTC (Sun) / 1am ET (Sun) / 10pm PT (Sat)
    
    
    

GPF and BIPA Enrollments - UPDATED 6/24/25

UPDATED: Testing Process for GPF and BIPA Enrollments

The testing process for external vendors utilizing the enrollment API for Genentech Patient Foundation (GPF) and Benefit Investigations (BIPA) has been streamlined by removing Genentech's manual processing of enrollments. The new auto-processing of enrollments involves the following steps:

(1) Submit an enrollment to any of the applicable enrollment API endpoints below based on the type of enrollment and desired test outcome:

BIPA ENROLLMENT

Test:
https://test-us-e1.apis.roche.com/pharma-cmg-ehr-fhir-exp-test/v2/enrollment?testEnrollment=true&expectedOutcome=accepted

Stage:
https://stage-us-e1.apis.roche.com/pharma-cmg-ehr-fhir-exp-stage/v2/enrollment?testEnrollment=true&expectedOutcome=accepted

GPF ENROLLMENT

Test:
https://test-us-e1.apis.roche.com/pharma-cmg-ehr-fhir-exp-test/v2/enrollment?testEnrollment=true&expectedOutcome=Approved

https://test-us-e1.apis.roche.com/pharma-cmg-ehr-fhir-exp-test/v2/enrollment?testEnrollment=true&expectedOutcome=Denied

Stage:
https://stage-us-e1.apis.roche.com/pharma-cmg-ehr-fhir-exp-stage/v2/enrollment?testEnrollment=true&expectedOutcome=Approved

https://stage-us-e1.apis.roche.com/pharma-cmg-ehr-fhir-exp-stage/v2/enrollment?testEnrollment=true&expectedOutcome=Denied

Conditions:

• words 'Approved' and 'Denied' are case-sensitive.
  
• Use 'household-size' value = 5 for testing purposes
  
  

(2) Receive a Success Message: Upon submission, you will receive the standard enrollment response (OperationOutcome with 200 message = "All OK') confirming the enrollment has been successfully received.

(3) Check Status Update: Since the process is now automated, you can immediately call for a “Status Update” on the enrollment.

(4) If you receive an error after submitting an enrollment, please do the following:

• ensure that your enrollment bundle is FHIR compliant
• verify that the enrollment bundle contains all the required fields Refer to Mapping page
• verify that the enrollment bundle contains the required questionnareResponses based on the product and service request
  
  

Copay Enrollments

For Copay enrollments, the response is real-time: If the enrollment is successful, all information is returned immediately. If there are errors, an error message is returned. No additional processing or manual steps are involved in the testing process.

Example Test Scenarios

• Submit a GPF enrollment for "Upfront" shipment that includes:
  • adult patient, prescription, prescriber signature, site of treatment
  • include patient consent with Household size and Household annual amount
    
• Submit a GPF enrollment for "Replacement" shipment that includes:
  • minor patient, no prescription, prescriber signature, relatedPerson
  • include patient consent with Household size and Household annual amount
    
• Submit Access Solutions enrollment with:
  • no patient consent
  • with patient consent
  • a request for a Starter service request (limited products with Starter SRs)
  • a prescription
  • combo products (Ophthalmology, BioOncology, Rheumatology products)
    
• Copay Card Enrollments:
  • drug copay only
  • drug & admin copay
  • an enrollment that will be Denied
    • for Xolair, Hemlibra, Piasky: to get a denial, use patient firstname = NotDetermined or NotEligible
    • for all other products: email UAPI-TestSupport-d@gene.com requesting override switch be turned on. This will result in Copay enrollments being denied.

Sample Access Solutions Enrollment Bundles:

Enrollment + Patient Consent: BIPA SR, Copay Referral SR, Prescription, Digital Consent, Prescriber Signature, 2 Diagnosis Codes
Example Cotellic bundle

Enrollment Only: BIPA SR, Prescription, Prescriber Signature (optional)
Example Actemra Subcutaneous bundle

Enrollment + Patient Consent: BIPA and Starter SR, Digital Consent, Prescriber Signature, Site of Treatment, Starter Prescription
Example Xolair Bundle

Enrollment + Patient Consent: Patient Foundation SR, Digital Consent, Prescriber Signature, Site of Treatment. Contains prescription for implant kit (initial fill/refill).
Example Susvimo bundle

Enrollment + Patient Consent: BIPA SR, Copay Referral SR, Patient Consent, and Site of Treatment.
Example Ocrevus bundle

Patient Consent Only: Patient Consent only bundle, no Service Request provided Example Patient Consent Only bundle

Sample Copay Enrollment Bundles:

Copay Card Enrollment Request: Single product, both drug & admin copay
Example Ocrevus Copay enrollment bundle

Copay Card Enrollment Request: Combo products with 2 brandIds
Example Polivy & Rituxan for Oncology Copay enrollment bundle

Copay Card Response: Copay response for an Approved (active) enrollment.Example Vabysmo Copay Approved Response

Copay Card Response: Copay response for an Denied (cancelled) enrollment with OperationOutcome resource.Example Vabysmo Copay Denied Response