This CapabilityStatement describes the capabilities of a Genentech FHIR server which receives patient enrollments, sends enrollment status updates and serves related Questionnaire resources.

Enables searching by extension ServiceRequestType on CoverageEligilibityRequest resource.

Example of questionnaire to be filled out when submitting enrollment bundle for product Alecensa.

Example of questionnaire to be filled out when submitting Copay enrollment bundle for product Cotellic.

Example of questionnaire to be filled out when submitting enrollment bundle for product Cotellic.

Example of questionnaire to be filled out when submitting enrollment bundle for product Herceptin.

Example of questionnaire to be filled out when submitting enrollment bundle for product Lucentis.

This profile constrains a Bundle resource for use to submit enrollment into Access Solutions services. It CAN be used in following scenarios:

• Prescriber Service with Patient Consent
• Prescriber Service Only
• Patient Consent Only (Digital Consent)

This profile constrains a Bundle resource for use as Copay enrollment submission

This profile constrains a Bundle resource for use as Copay error reconciliation.

This profile constrains a Bundle resource for use in copay workflow to:

1. add existing Patient to Copay program,
2. search for Patients who are currently enrolled. It is critical to include Practice Organization ID in MessageHeader.sender.identifier.value to indicate the Practice to which the searched Patient belongs to.

This profile constrains a Bundle resource which combines all elements from copay request with all elements from copay response. Combine uapi-copay-enrollment-bundle with uapi-bundle-query-response for copay.

This profile constrains a Bundle resource for use as Access Solutions patient consent form submission

This profile constrains a Bundle resource for use as the request message in a UAPI Query process–with a Parameters resource as the bundle’s message focus. It is based on IG http://build.fhir.org/ig/HL7/fhir-specialty-rx/branches/master/StructureDefinition-specialty-rx-bundle-query.html

This profile constrains a Bundle resource for use as the response message in a UAPI Query process–with a Parameters resource as the bundle’s message focus. It is based on IG http://build.fhir.org/ig/HL7/fhir-specialty-rx/branches/master/StructureDefinition-specialty-rx-bundle-query-response.html

This profile constrains a Bundle resource for use as the response message in a Copay Search use case. It returns potentially multiple matching patients in query-result-patient entry element.

This profile constrains a Bundle resource to carry the query results from a UAPI Query - it is derived from IG http://build.fhir.org/ig/HL7/fhir-specialty-rx/branches/master/StructureDefinition-specialty-rx-bundle-search-result.html

This profile constrains a Bundle resource for use as an element in UapiBundleQueryResponseMultiPatient bundle query-result-patient entry element. It contains Patient with related query-result resources.

This profile constrains a Bundle resource for use as the Status Update for Service Request Using Coverage Eligibility Response

This profile constrains the Condition resource

This profile constrains the Consent resource for Patient and Practioner

This profile constrains the Coverage resource

This profile constrains the CoverageEligibilityRequest resource to be used in sharing service request results in UAPI

This profile constrains the CoverageEligibilityResponse resource to be used in sharing service request results in UAPI

This profile constrains the MedicationRequest resource to be included in UAPI data exchanges

This profile constrains the MessageHeader resource to be included in each bundle

This profile constrains the Organization resource for representing practice and insurance

This profile constrains the Patient resource to be included in UAPI data exchanges

This profile constrains the Practitioner resource to be included in UAPI data exchanges

This profile constrains the Provenance resource to be included in UAPI data exchanges

This profile constrains the Related Person resource to be included in UAPI data exchanges

This profile constrains the ServiceRequest resource

States how many level of appeals the Insurance allows.

States what documents are required to submit for appeal.

States when the deadline is to submit for an appeal with the Insurance.

Date when the insurance company issued the insurance card.

Describes Plan year for Coverage Status Outcome

Describes Reference Number for Coverage Status Outcome

Describes the Medication(Product) related to Coverage eligibility Request

Describes the ServiceRequest related to Coverage Eligibility Request

Describes shipment method for GPF Shipments, currently supported values are ‘Upfront’ and ‘Replacement’

Provides the updated status of successfully enrolled Service Requests

Appeal Turn Around Time: Estimated time Insurance needs to review an appeal in business days.

Detailed breakdown of medication units with quantity to fill the prescription dosage requirement

Additional information for the dispenser

Timestamp when bundle was submitted

States what the first day of an on-file referral from a Primary Care Physician (When it starts)

States whether a referral from a Primary Care Physician is on-file with the Insurance

States what the last day of a on-file referral from a Primary Care Physician (When it expires)

States whether a referral from a Primary Care Physician is required.

States whether Peer to Peer is an option for appeals.

The preferred method of contact.

The preferred contact time.

PreDetermination Turn Around Time: Estimated time Insurance needs to review a PreDetermination in business days.

Prior Authorization Turn Around Time: Estimated time Insurance needs to review a Prior Authorization in business days.

States what the Spend down frequency is for Medicaid. Only applies to patients with Medicaid

This value set contains Benefit Types used in the UAPI

This value set contains Insurance Plan Types values used in copay enrollments in the UAPI. It is a combination of http://terminology.hl7.org/ValueSet/v3-ActCoverageTypeCode standard codes with subset of custom additional codes required for UAPI implementation.

This value set contains Coverage outcome as result of patient enrollment.

This value set contains Insurance Unit used in the UAPI

This value set contains Organization Types used in the UAPI

This value set contains preferred contact methods.

This value set contains preferred contact times.

This value set contains product Auth used in the UAPI

This value set contains product names used in the UAPI MedicationRequest profile.

This value set contains product service used in the UAPI

This value set contains Service Request types used in the UAPI ServiceRequest profile.

This value set contains Shipment method used for GPF medicine.

This value set contains system event types used in the UAPI MessageHeader profile.

Genentech Authorizations Supported in UAPI

Genentech Benefit Types Supported in UAPI

Genentech additional Benefit Types supported in UAPI

The BrandID identifies the product and the type(s) of Copay assistance the patient is applying for.

Copay Enrollment Channel

Copay Enrollment Status

Workflow selection. A workflow is a predetermined sequence of actions represented by a unique workflow name and capable of being mutated at the various available states via the settings object. Each workflow consists of a subset combination of these available internal actions:

Genentech possible Errors on rejected Copay Enrollment

Internal validation errors when processing incoming enrollment and claims copay messages.

Genentech additional Insurance Plan Types supported in UAPI for Copay enrollments.

This is used to define copay identifiers required by the system to process the Copay enrollment.

This is used to define copay identifiers returned by the Copay enrollment.

The enroll-by-id field identifies who is applying for Copay assistance.

Value to represent the type of Debit Card assignment that should occur with this enrollment.

This code system defines outcomes of eligibility status for requested services.

This code system defines event types used in UAPI message headers

Genentech Insurance Unit Supported in UAPI

Prescriber’s preferred contact methods supported in UAPI

Prescriber’s preferred contact times supported in UAPI

Genentech Product names supported in UAPI

Genentech product coverage categories returned in CoverageEligibilityResponse

This code system defines Service Request types used in UAPI to indicate Patient Assistance Program services

Genentech shipment categories supported in UAPI

Example to be used by Vendor Systems (external). This is example of a bundle which is to be sent to Universal API enrollment endpoint in order to request Access Solutions Services for Digital Consent Only.

Example to be used by Vendor Systems (external). This is example of a bundle which is to be sent to Universal API enrollment endpoint in order to request Access Solutions Services for Enrollment + Digital Consent.

Example to be used by Vendor Systems (external). This is example of a bundle which is to be sent to Universal API enrollment endpoint in order to request Access Solutions Services for Bundle Enrollment Only.

Example of Questionnaire Response for product Alecensa.

Example data query message send as a request in copay search use case. Task identifiers to indicate brandId in Parameters.

Example of UAPI Copay update

Example of Questionnaire Response for BIPA for Herceptin.

Example for 4 times a day

Example of MessageHeader which contains sender.endpoint with transaction identifier appended after /enrollmentID

Successful OperationOutcome

Example of Practice Organization which should be included in each enrollment bundle.

Example of Questionnaire Response for product Rozlytrek.

Example of Site of Treatment/Infusion Centre- Organization which may be included in each enrollment bundle.

Example to be used by Vendor Systems (external). This is example of a bundle which is to be sent to Universal API enrollment endpoint in order to request GPF SR

Example to be used by Vendor Systems (external). This is example of a bundle which is to be sent to Universal API enrollment endpoint in order to request Access Solutions Services.

Example to be used by Vendor Systems (external). This is example of a bundle which is to be sent to Universal API enrollment endpoint in order to request Access Solutions Services.

Example to be used by Vendor Systems (external). This is example of a bundle which is to be sent to Universal API enrollment endpoint in order to request Access Solutions Services.

Example to be used by Vendor Systems (external). This is example of a bundle which is to be sent to Universal API enrollment endpoint in order to request Access Solutions Services.

Example to be used by Vendor Systems (external). This is example of a bundle which is to be sent to Universal API enrollment endpoint in order to request Access Solutions Services.

Example to be used by Vendor Systems (external). This is example of a bundle which is to be sent to Universal API enrollment endpoint in order to request Access Solutions Services.

Example to be used by Vendor Systems (external). This is example of a bundle which is to be sent to Universal API enrollment endpoint in order to request Access Solutions Services containing prescriber information only.

Example to be used by Vendor Systems (external). This is example of a bundle which is to be sent to Universal API enrollment endpoint in order to request Access Solutions Services.

Example to be used by Vendor Systems (external). This is example of a bundle which is to be sent to Universal API enrollment endpoint in order to request Access Solutions Services.

Example to be used by Vendor Systems (external). This is example of a bundle which is to be sent to Universal API enrollment endpoint in order to request Access Solutions Services.

Example to be used by Vendor Systems (external). This is example of a bundle which is to be sent to Universal API enrollment endpoint in order to request Access Solutions Services.

Example to be used by Vendor Systems (external). This is example of a bundle which is to be sent to Universal API enrollment endpoint in order to request Access Solutions Services.

Example to be used by Vendor Systems (external). This is example of a bundle which is to be sent to Universal API enrollment endpoint in order to request Access Solutions Services.

Example to be used by Vendor Systems (external). This is example of a bundle which is to be sent to Universal API enrollment endpoint in order to request Access Solutions Services.

Example to be used by Vendor Systems (external). This is example of a bundle which is to be sent to Universal API enrollment endpoint in order to request Access Solutions Services.

Example to be used by Vendor Systems (external). This is example of a bundle which is to be sent to Universal API enrollment endpoint in order to request Access Solutions Services.

Example to be used by Vendor Systems (external). This is example of a bundle which is to be sent to Universal API enrollment endpoint in order to request Access Solutions Services.

Example to be used by Vendor Systems (external). This is example of a bundle which is to be sent to Universal API enrollment endpoint in order to request Access Solutions Services.

Example to be used by Vendor Systems (external). This is example of a bundle which is to be sent to Universal API enrollment endpoint in order to request Access Solutions Services.

Example to be used by Vendor Systems (external). This is example of a bundle which is to be sent to Universal API enrollment endpoint in order to request Access Solutions Services.

Example to be used by Vendor Systems (external). This is example of a bundle which is to be sent to Universal API enrollment endpoint in order to request Access Solutions Services.

Example to be used by Vendor Systems (external). This is example of a bundle which is to be sent to Universal API enrollment endpoint in order to request Access Solutions Services for Evrysdi.

Example to be used by Vendor Systems (external). This is example of a bundle which is to be sent to Universal API enrollment endpoint in order to request biPA for combo therapy Herceptin plus Perjeta

Example to be used by Vendor Systems (external). This is example of a bundle which is to be sent to Universal API enrollment endpoint in order to request Access Solutions Services containing prescriber information only.

Example to be used by Vendor Systems (external). This is example of a bundle which is to be sent to Universal API enrollment endpoint in order to request Access Solutions Services for Susvimo.

Example to be used by Vendor Systems (external). This is example of a bundle which is to be sent to Universal API enrollment endpoint in order to request Access Solutions Services for Venclexta.

Example to be used by Vendor Systems (external). This is example of a bundle which is to be sent to Universal API enrollment endpoint in order to request Patient Foundation Enrollment

Example of copay bundle 1 - enrollment initiated from internal Genentech system - PACT.

Example of copay bundle 1 - copayCRX1

Example of copay bundle 2 with Combo Therapy

Example of eob resource which includes important response attributes returned as a result of copay enrollment request

Example of eob resource which includes important response attributes returned as a result of copay enrollment request

Example of eob resource which includes important response attributes returned as a result of copay enrollment request

Example of Operation Outcome resource which includes rejection message for Copay Enrollment

Example to be used by Vendor Systems (external). This is example of a bundle which is to be sent to Universal API enrollment endpoint in order to submit Patient Consent.

Example data query message without full resources (identifiers in parameters instead)

Example data query response message (single search) for GPF service.

Example response message to rejected Copay Enrollment request - returned in response to submission of UapiBundleCopayEnrollment resource.

Example response message to successfully Copay Enrollment request - returned in response to submission of UapiBundleCopayEnrollment resource.

Example response message to successfully Copay Enrollment request with 2 brands - returned in response to submission of UapiBundleCopayEnrollment resource.

Example response message to Copay Search request. It returns 2 matching patients in the MultiPatient bundle

Example response message to rejected Copay Update request.

Example to be used by MAS Service implementation (internal). This is example of a bundle which went through Mulesoft transformation enriching the data with additional elements required by GNE FHIR Server.

Example to be used by MPS Redesign (internal). This is example of a bundle which is to be sent to Universal API enrollment endpoint in order to request Access Solutions Services.

Example representing combination of request and response bundle elements which will be generated internally by UAPI and published as an event to Genentech internal MessageBus. This contains error response to coapy enrollment request. This is used for notifications to internal Genentech systems.

Example representing combination of request and response bundle elements which will be generated internally by UAPI and published as an event to Genentech internal MessageBus. This is used for notifications to internal Genentech systems.

Example data query message without full resources (identifiers in parameters instead) after the internal Genentech middletier transformations

Example of UAPI Status Update - C&R

Example of UAPI Status Update - GPF

Example of Questionnaire Response for Patient Foundetion for product Herceptin.

Example of a Digital Consent with Marketing Info permission

Example of a Digital Consent given by the Patient

Example of a Digital Consent given by the RelatedPerson

Example of complex dispense instructions with Injectable filled Device.

Example of complex dispense instructions with multiple vial sizes of product.

Example of complex dispense instructions with multiple vial sizes of product.

Example of empty MedicationRequest - when prescription information not required for SR