PBM Lightweight as a Service
Najeeb PBM Lightweight as a Service (Pharmacy Benefit Management) is a comprehensive pharmacy claims processing solution designed to streamline and automate the adjudication of prescription drug claims for insurance companies in the Kingdom of Saudi Arabia.
This Service enables the utilization of the AI Engine capabilities without having to store any sensitive data outside the Insurance Company Network, as all the data submitted is processed ephemerally.
The "PBM Lightweight" flow differs from the "PBM Full-Mode" flow primarily in its validation logic. Unlike Full-Mode, the Lightweight flow does not validate member policies, consumption limits, or existing entitlements. Furthermore, it omits pre-creation checks for members, policies, and policy holders, as well as membership join validations. Consequently, if a member or policy does not already exist in Lightweight mode, the system automatically creates it on the fly.
Service Description
Najeeb PBM Lightweight as a Service provides a seamless API integration that enables insurance companies to submit pharmacy claims from their core systems (or directly from network pharmacies) and receive adjudicated results in real time. The service handles the entire prescription claim lifecycle, from formulary and drug utilization checks to final approval or rejection, with all processing happening ephemerally within your dedicated, isolated Najeeb instance.
Key Features
- Adjudication: Receive instant responses to pharmacy claim submissions
- Ephemeral Data Processing: All data is processed temporarily and securely within your isolated Najeeb instance
- Formulary Management: Automated checks against the insurance plan's drug formulary
- Drug Utilization Review (DUR): Built-in checks for drug interactions, duplicate therapy, and quantity limits
- Automated Validation: Built-in validation for drug codes and prescriber information
- KSA Compliance: Fully compliant with Saudi healthcare and pharmaceutical regulations
- Scalable Architecture: Handles high volumes of requests with reliable performance
Due to this, some capabilities of the full version of the AI Engine will be dropped under this request like:
- Policy and benefits validation
- Contractual rejections due to the lack of price list information
How It Works
- Request Submission: Your core system or dispensing pharmacy sends a pharmacy claim to the Najeeb API
- Processing: The request is processed within your isolated Najeeb instance with ephemeral data handling
- Validation: Automated validation of drug codes, formulary status, and prescriber credentials
- Response: Adjudicated result is returned to your system with approval, rejection, or additional requirements
Requirements Prior to Integration
Before integrating with Najeeb PBM Lightweight as a Service, ensure you have the following:
Technical Requirements
- API Access Credentials
- Valid API key (
access-key) provided by Najeeb - Access to your dedicated Najeeb instance endpoint
- Network connectivity to the Najeeb API infrastructure
- Data Requirements
- Transaction data (authorization number, unique transaction ID, transaction type, treatment date)
- Policy data (policy number, policy holder ERP ID)
- Medical provider data (CCHI number). For reporting purposes, we recommend sending a list of medical providers (including names and CCHI codes) to the Najeeb technical team in advance.
- Member data (member ID, date of birth, gender, marital status)
- Prescriber information (doctor ID, speciality, name)
- Item/service details (service code, description, NPHIES code and type, quantity)
- Diagnosis codes (ICD-10 format)
Data Preparation
Ensure your system can provide:
- Transaction Data: authorization number, a unique transaction ID, transaction type (
PREAUTHorCLAIM) - Policy Data: policy number, policy holder ERP ID
- Member Data: member ID, date of birth, gender, marital status
- Provider Data: medical provider CCHI number, doctor ID/specialty/name
- Item Data: service code, service description, NPHIES code and type, quantity, price, benefit/sub-benefit codes
- Diagnosis Data: ICD-10 diagnosis codes (primary/secondary)
For the ph_erp_id field, provide your internal policyholder identifier. If this identifier is not available, send the value "default" for all requests.:::
If the member_id was not defined earlier in Najeeb, then Najeeb will create a new member record with the demographics defined in the request member_dob & member_gender.
Important note:
If a member already exists in the system, the existing record will be retained—no duplicate will be created and no overwrite will occur.
However, if you send subsequent requests with the same member_id but differing demographic information, the PBM will flag a member information inconsistency warning.
transaction_idis the primary idempotency key and must be unique per request; a duplicate value returns an error.authorization_numberis not required to be unique; it can be reused across follow-up requests related to the same authorization.
service_code, service_description, nphies_code, nphies_type, and service_type are all required on every item.
Integration Guide
The Najeeb PBM integration is accomplished through a single API endpoint that receives a PBM (pharmacy benefit management) prior authorization from your insurance company core system. All data processing is ephemeral and handled entirely within your isolated Najeeb instance.
Najeeb offers additional endpoints for synchronizing historical claims and requests made by the member. While integration with these APIs is optional, it allows Najeeb to make more accurate decisions by leveraging the member's past data.
Base URL
https://api.{client_namespace}.najeeb.ai/v4.0/health
Authentication
All API requests are authenticated using an API key passed in a dedicated header:
access-key: YOUR_API_KEY
For access key provisioning, please contact Najeeb support.
API Endpoint
Create PBM Request
POST /approval-request/create-pbm-request
This endpoint receives a PBM prior authorization from your core system and processes it ephemerally within your isolated Najeeb instance. The request is validated and acknowledged synchronously.
Request Headers
| Header | Type | Required | Description |
|---|---|---|---|
access-key | string | Yes | API key for authentication |
Content-Type | string | Yes | Must be application/json |