إنتقل إلى المحتوى الرئيسي

DRG Coder & Validator

Preview

The DRG products are being released. This page describes the contract they are built to; details may still change before release.

Najeeb DRG Coder & Validator assigns an AR-DRG (Australian Refined Diagnosis Related Group) to an inpatient episode from its diagnoses, procedures and patient details.

  • Checks the provider's DRG against Najeeb's own and explains any difference.
  • Recalculates after review, so you also see the DRG left once Najeeb's decisions are applied.

The DRG solution comes in three products that share the same objects, so you integrate once and reuse them everywhere:

ProductWhat it doesHow you call it
Stand-alone DRG CoderGroups one episode on demand, and compares it with a provider DRG when you send onePOST /drg/group
Pre-auth DRG CoderCalculates the DRGs of an inpatient prior authorization while it is processed and revieweddrg_enabled: true on POST /approval-request/create
Claims Batch DRG ValidatorCalculates the DRGs of every inpatient claim in a batchdrg_enabled: true on the batch upload

The Four DRGs​

A prior authorization or claim can carry up to four DRGs. Each answers a different question.

DRGWho sets itWhat it isWhere you find it
Provider DRGThe provider (HCP)The DRG the provider calculated and billedprovider_drg
Claimed DRGNajeebThe DRG of the whole request: every diagnosis and every procedure sent. Compared with the provider DRG.drg.claimed
Approved DRGNajeebThe DRG of the diagnoses and only the approved procedures, after Najeeb's AI review and any later decision. Compared with the claimed DRG.drg.approved
Settled DRGThe payerThe DRG and weight the payer and provider agree on after reviewsettled_drg

Example:

  1. A provider bills F10B: a coronary stent, admitted for a heart attack.
  2. Najeeb's claimed DRG is also F10B, so the provider DRG matches.
  3. The AI rejects the stent, so the approved DRG is F60A, a medical DRG for the same admission without the procedure.
  4. After review, the payer records the settled DRG both sides agree on.

DRG Mode​

DRG results can be for reference only, or can affect decisions. Najeeb sets this per account.

ModeDRGs calculated and returnedEffect on decisions
SHADOW (default, shadow billing)YesNone. Results are for reference: they add issues and notes, never a rejection reason, and never change automation.
PRODUCTIONYesAn invalid provider DRG rejects every item with NPHIES reason AD-3-4 "Incorrect DRG calculated". See Invalid DRG and mismatch.

Every DRG result carries the mode it was calculated under, so you always know whether it can affect a decision.

Invalid DRG and mismatch​

CaseWhat it meansSHADOWPRODUCTION
Invalid DRGThe provider DRG cannot be a DRG: not in AR-DRG V9.0, an error DRG (960Z, 961Z, 963Z), a version other than 9, or malformedPROVIDER_DRG_INVALID and DRG_REJECTION_SHADOW issuesPROVIDER_DRG_INVALID and DRG_REJECTION_APPLIED issues, and AD-3-4 on every item
DRG mismatchA valid provider DRG that differs from Najeeb's claimed DRGPROVIDER_DRG_* comparison issuePROVIDER_DRG_* comparison issue. Never a rejection.

An invalid provider DRG never rejects your request. It is stored as sent, and Najeeb still calculates its own DRGs.

Classification and Code Sets​

ItemVersion
DRG classificationAR-DRG Version 9.0 (drg_version = 9)
Diagnosis codesICD-10-AM
Procedure codesSBS V3 (Saudi Billing System), sent in items[].nphies_code

Najeeb translates SBS V3 procedure codes to ACHI (10th Edition), the procedure classification AR-DRG is built on, before grouping. Results always report back the SBS codes you sent.

Access​

DRG coding is a setting of your Najeeb account, switched on separately for each product. Contact Najeeb to enable it.

ProductWhen DRG is not enabled for your account
Stand-alone DRG CoderRequests are rejected with 403 (E_DRG_014)
Pre-auth DRG CoderThe prior authorization is processed as usual. When it was sent with drg_enabled: true, its drg results have status: ERROR with issue E_DRG_014
Claims Batch DRG ValidatorThe batch is processed as usual. Its inpatient claims' drg results have status: ERROR with issue E_DRG_014

When DRG is enabled, the Pre-auth and Claims Batch products still calculate DRGs only for requests sent with drg_enabled: true.

How the DRG Is Assigned​

  1. Major Diagnostic Category (MDC): the principal diagnosis places the episode in a body system, for example MDC 05, circulatory system.
  2. Adjacent DRG (ADRG): procedures and the principal diagnosis select the base group, for example F10 (interventional coronary procedures).
  3. DRG split: the episode's complexity score, built from the additional diagnoses, selects the final DRG within the base group, for example F10A (major complexity) or F10B (minor complexity).

Why an episode can have no procedures​

items can be empty. Many inpatient episodes are medical: the patient is treated without an operation or a procedure that affects grouping, for example pneumonia treated with antibiotics. These episodes are grouped on the diagnoses and the patient details alone, and receive a medical DRG. This is also why the approved DRG becomes a medical DRG when every procedure is rejected.

Common Objects​

All DRG products use the objects below.

DRG Reference Object (provider_drg, settled_drg)​

ParameterTypeRequiredDescriptionAccepted Values
drg_versionstringNoAR-DRG version of the code9 (default). Any other version makes a provider DRG invalid
drg_codestringYes, when the object is sentThe DRG codeUp to 16 characters. A provider DRG is never rejected for its format: see Invalid DRG and mismatch. A settled DRG must be a valid AR-DRG V9.0 code (E_DRG_020 otherwise)
drg_weightnumberNoRelative weight. Optional during shadow billing. Stored and returned, not checked.0–100, up to 4 decimals

null for the object, or for any of its fields, is read exactly as not sent.

"provider_drg": {
"drg_version": "9",
"drg_code": "F10B",
"drg_weight": 1.2345
}

In responses, provider_drg also has:

  • source: REQUEST, or ITEM when the DRG was found on a service line
  • validity: VALID or INVALID

settled_drg also has settled_at.

DRG Info Object (drg_info)​

Grouping inputs that are not part of a standard encounter. Every field is optional, and null is read exactly as not sent.

ParameterTypeRequiredDescriptionAccepted Values
separation_modeEnumNoHow the episode ended. No defaultSee Separation Mode
leave_daysintegerNoDays of leave during the stay0 or more, less than the stay length. Default 0
length_of_stayintegerNoLength of stay in days. See Length of stay1 or more
same_day_flagbooleanNoAdmitted and separated on the same day. Derived from the dates when not senttrue, false
admission_weightintegerNoWeight on admission, in grams. Used only for patients under 1 year old100–9999
mechanical_ventilation_hoursintegerNoHours of mechanical ventilation0 or more, not more than the stay in hours
"drg_info": {
"separation_mode": "09",
"leave_days": 0,
"length_of_stay": 3,
"same_day_flag": false,
"admission_weight": null,
"mechanical_ventilation_hours": 0
}

admission_weight is null here because the patient is an adult; it is used only for patients under 1 year old.

Earlier field names

drg_info.drg_version, drg_info.provider_drg_code and drg_info.provider_drg_weight, from an earlier version of this page, are still accepted as aliases of the provider_drg fields. When both are sent, provider_drg wins. Use provider_drg in new integrations.

Issue Object (issues)​

Every error, warning and note is reported as an issue, in the same shape at every level: the prior authorization or claim, each item, and each DRG result.

FieldTypeAlways presentDescription
levelEnumYesERROR, WARNING or INFO. See Severity Levels
codestringYesStable issue code. See Issue Codes
messagestringYesExplanation
fieldstringNoThe request field it is about, for example diagnoses[2].code, items[0].nphies_code, provider_drg.drg_code
valuestring or numberNoThe value sent in that field

DRG Result Object​

One calculation of the grouper. drg.claimed and drg.approved hold one each, and the Stand-alone DRG Coder returns one.

FieldTypeDescription
drg_request_idnumberNajeeb's ID for this calculation. Use it with Get DRG Result
kindEnumCLAIMED, APPROVED or STANDALONE. See Kind
is_currentbooleantrue for the latest calculation of its kind. Always false for STANDALONE
modeEnumSHADOW or PRODUCTION, at the time of calculation
calculated_atstringISO-8601 DateTime
triggerEnumWhat caused the calculation. See Trigger
statusEnumGROUPED, UNGROUPABLE or ERROR. See Status
drg_versionstringAR-DRG version used
drg_resultobjectSee DRG Result Fields. null when status is ERROR
diagnosesarrayEach diagnosis with code, type, name (ICD-10-AM term), valid and used_for_grouping
itemsarrayEach procedure grouped, with erp_item_id, nphies_code, achi_code, mapping_equivalence (1 exact, 2 SBS narrower, 4 inexact), valid and used_for_grouping
issuesarrayIssues of this calculation

DRG Result Fields​

FieldTypeDescription
najeeb_drg_codestringDRG assigned by Najeeb
najeeb_drg_descriptionstringDRG long description, up to 80 characters
najeeb_drg_weightnumberAlways null for now: DRG weights are not loaded yet. Keep the field; it will be filled without a change to the API
mdc_codestringMajor Diagnostic Category, "00"–"23". Always a string
mdc_descriptionstringMDC description
grouper_statusstring"00"–"09". See Grouper Status
grouper_status_descriptionstringGrouper status description
ungroupablebooleantrue when the episode grouped to an error DRG
complexitynumberEpisode Clinical Complexity Score, rounded to the nearest 0.5. Range 0–32
complexity_rawnumberThe same score with 6 decimals
provider_drgobjectThe provider DRG at the time of calculation, or null
settled_drgobjectThe settled DRG at the time of calculation, or null
compared_withEnumWhat this DRG was compared with: PROVIDER (claimed and stand-alone), CLAIMED (approved), or null when there was nothing to compare
compared_drg_codestringThe DRG it was compared with
matchingbooleanWhether the two DRGs are equal. null when compared_with is null
matching_reasonEnumWhy they match or differ. See Matching Reason
matching_split_reasonEnumFor DIFFERENT_ADRG and DIFFERENT_SPLIT: the kind of test that separates them. See Split Reason
matching_teststringThe AR-DRG test they part on, in words, for example complexity score >= 4
matching_messagestringNajeeb's explanation of the difference
values_usedobjectValues the grouper used: age_years, age_days, length_of_stay, same_day_flag, admission_weight. age_days and admission_weight are null for patients 1 year old or older

Issues​

Severity Levels​

LevelMeaningWhat to do
ERRORSomething could not be processed. On a DRG result, grouping did not run and status is ERROR. In the Stand-alone DRG Coder, the request fails with a 4xx status.Fix the field named in field, then send again
WARNINGProcessing ran, but an input was invalid, conflicting or replaced, or the DRGs differReview the field and the message
INFOProcessing ran normally. A default was applied, a value was derived, or a note is attachedNothing required

Issue Codes​

Request Issues​

Prior authorizations and claims always carry a root issues list, whether or not DRG is used. For now it holds the same information as the existing notes and request_alerts, which are kept unchanged.

CodeLevelMeaning
AI_NOTEINFOA note from Najeeb's AI review
PREDEFINED_REASON_BYPASSINFOEvery item arrived with a predefined reason, so no evaluation ran
REQUEST_ALERTWARNINGA request-level alert
OCN_PHARMACYWARNINGThe provider is an OCN pharmacy
SIMILAR_REJECTED_REQUESTSWARNINGSimilar requests were previously rejected
PROVIDER_DRG_INVALIDWARNINGThe provider DRG is invalid. See Invalid DRG and mismatch
DRG_REJECTION_APPLIEDWARNINGPRODUCTION mode: AD-3-4 was applied to every item because the provider DRG is invalid
DRG_REJECTION_SHADOWINFOSHADOW mode: AD-3-4 would have been applied; no item was changed
APPROVED_DRG_CHANGEDINFOThe approved DRG differs from the claimed DRG. The message names the cause

The provider-DRG comparison issue of the current claimed DRG is also copied here.

Grouping Issues​

CodeLevelFieldMeaning
UNGROUPABLEWARNING—The episode grouped to an error DRG. The message gives the grouper status
PRINCIPAL_DIAGNOSIS_INVALIDERRORdiagnoses[n].codeNot a valid ICD-10-AM code. The DRG result fails with E_DRG_008
PRINCIPAL_DIAGNOSIS_NOT_ALLOWEDWARNINGdiagnoses[n].codeExternal cause codes (U50–Y98) cannot be a principal diagnosis
PRINCIPAL_DIAGNOSIS_UNACCEPTABLEWARNINGdiagnoses[n].codeThe code is not acceptable as a principal diagnosis
DIAGNOSIS_INVALIDERRORdiagnoses[n].codeNot a valid ICD-10-AM code. The DRG result fails with E_DRG_008: a DRG calculated without one of the diagnoses is not reliable
DIAGNOSIS_DUPLICATES_PRINCIPALINFOdiagnoses[n].codeRepeats the principal diagnosis; ignored
DIAGNOSIS_SEX_CONFLICTWARNINGdiagnoses[n].codeConflicts with the patient's sex; ignored
DIAGNOSIS_AGE_CONFLICTWARNINGdiagnoses[n].codeConflicts with the patient's age; ignored
INTERVENTION_INVALIDWARNINGitems[n].nphies_codeNot a valid procedure for grouping; ignored
INTERVENTION_SEX_CONFLICTWARNINGitems[n].nphies_codeConflicts with the patient's sex; ignored
INTERVENTION_AGE_CONFLICTWARNINGitems[n].nphies_codeConflicts with the patient's age; ignored
INTERVENTION_INEXACT_MAPPINGWARNINGitems[n].nphies_codeThe SBS code has only an inexact ACHI equivalent; the DRG may differ
INTERVENTION_BROADER_MAPPINGINFOitems[n].nphies_codeThe SBS code is more specific than its ACHI equivalent; grouping used the ACHI code
INTERVENTION_NOT_MAPPEDWARNINGitems[n].nphies_codePre-auth and batch: shaped like an SBS code but not in SBS V3; left out of grouping
INTERVENTION_SKIPPEDINFOitems[n].nphies_codePre-auth and batch: not an SBS procedure code (for example a drug or device); left out of grouping
TOO_MANY_PROCEDURESWARNING—Batch: more than 30 procedures; the first 30 in line order were used
DRG_INFO_INCONSISTENTWARNINGclaims[row_id=n]Batch: the lines of a claim sent different DRG values; the lowest row_id was used
AGE_INVALIDWARNINGmember_dobAge at admission is invalid
SEX_INVALIDWARNINGmember_genderSex is invalid
LENGTH_OF_STAY_INVALIDWARNINGdrg_info.length_of_stayLength of stay is invalid
LENGTH_OF_STAY_MISMATCHWARNINGdrg_info.length_of_stayThe length of stay sent differs from the dates; the smaller value was used
SAMEDAY_INVALIDWARNINGdrg_info.same_day_flagSame-day flag is invalid
SEPARATION_MODE_INVALIDWARNINGdrg_info.separation_modeSeparation mode is missing or invalid and the DRG needed it
ADMISSION_WEIGHT_INVALIDWARNINGdrg_info.admission_weightAdmission weight is invalid or conflicts with the age
ADMISSION_WEIGHT_MISSINGWARNINGdrg_info.admission_weightThe patient is under 1 year old and no admission weight was sent; 2500 g was used
VENTILATION_HOURS_NOT_SENTINFOdrg_info.mechanical_ventilation_hoursNo ventilation hours were sent; 0 was used

Provider DRG Issues​

In a claimed or stand-alone DRG result with a valid provider DRG, issues starts with exactly one comparison issue. Its field is provider_drg.drg_code, or the item the DRG was found on.

CodeLevelMeaningExample message
PROVIDER_DRG_MATCHINFOThe provider DRG equals Najeeb's DRGProvider DRG F10B matches Najeeb's DRG.
PROVIDER_DRG_COMPLEXITY_HIGHERWARNINGSame base group; the provider DRG needs a higher complexity score than the episode hasF10A needs a complexity score of 4 or more; this episode scores 1, so Najeeb assigned F10B (…). Additional diagnoses that raised the score: none. Did not raise it: E11.9, I10. A complication or comorbidity may be missing from the diagnoses sent, or sent with an invalid code.
PROVIDER_DRG_COMPLEXITY_LOWERINFOSame base group; the provider DRG is a lower level than the episode supportsNajeeb assigned F10A (…) with a complexity score of 8; provider DRG F10B (…) needs a complexity score below 4. …
PROVIDER_DRG_INTERVENTION_MISSINGWARNINGThe provider DRG is surgical, but no procedure sent leads to a surgical DRGProvider DRG H08B (…) is a surgical DRG, but no procedure sent qualified for one, so Najeeb grouped to H64C (…), a medical DRG. …
PROVIDER_DRG_INTERVENTION_EXTRAWARNINGNajeeb's DRG is surgical because of a procedure sent; the provider DRG is medicalNajeeb grouped to H08B (…), a surgical DRG, because of procedure(s) 30445-00-00 (…). Provider DRG H64C (…) is a medical DRG. …
PROVIDER_DRG_DIFFERENT_MDCWARNINGDifferent body systems (MDC): the principal diagnosis differsProvider DRG F10A (…) belongs to MDC 05 (…); Najeeb grouped to E62B (…) in MDC 04 (…) because the principal diagnosis J18.9 (…) belongs to that body system. …
PROVIDER_DRG_PRE_MDCWARNINGOne DRG is Pre-MDC (long ventilation, transplant, ECMO, tracheostomy) and the other is notProvider DRG A14C (…) is a Pre-MDC DRG … This episode did not qualify: no ventilation hours were sent …
PROVIDER_DRG_VENTILATION_SPLITWARNINGThe DRGs part on the ventilation hours… Ventilation hours sent: 400.
PROVIDER_DRG_WEIGHT_BANDWARNINGThe DRGs part on the newborn's admission weight… Admission weight used: 2500 g (the 2500 g default, because no weight was sent).
PROVIDER_DRG_SEPARATION_SPLITWARNINGThe DRGs part on the separation mode or length of stay… Separation mode used: 09; length of stay: 3 day(s).
PROVIDER_DRG_SAMEDAY_SPLITWARNINGThe DRGs part on the same-day flag… Same-day flag used: 1.
PROVIDER_DRG_AGE_SPLITWARNINGThe DRGs part on the patient's age… Age used: 63 year(s).
PROVIDER_DRG_PROCEDURE_SPLITWARNINGSame base group; the DRGs part on a specific procedure… Procedures that drove Najeeb's grouping: …
PROVIDER_DRG_DIAGNOSIS_SPLITWARNINGSame base group; the DRGs part on a diagnosis group… Principal diagnosis: …
PROVIDER_DRG_DIFFERENT_ADRGWARNINGSame body system, different base group, decided by a procedure or diagnosis group… Procedures that drove Najeeb's grouping: 38306-00-00.
PROVIDER_DRG_DIFFERENT_SPLITWARNINGSame base group, different level, for a reason not listed above—
PROVIDER_DRG_NOT_CONFIRMEDWARNINGNajeeb could not group the episode, so the provider DRG cannot be checkedNajeeb could not group the episode (960Z: …), so provider DRG F10A cannot be confirmed.

How the provider DRG was found:

CodeLevelMeaning
PROVIDER_DRG_FROM_ITEMINFOprovider_drg was not sent; the provider DRG was taken from a service line. See Provider DRG on an item
PROVIDER_DRG_MULTIPLE_ITEMSWARNINGSeveral service lines carry different DRGs; the first was used
PROVIDER_DRG_CONFLICTWARNINGprovider_drg and a DRG service line differ; provider_drg was used
PROVIDER_DRG_UNKNOWNWARNINGA line typed DRG has a code that is not in AR-DRG V9.0
PROVIDER_DRG_ERROR_GROUPWARNINGA DRG line carries an error DRG (960Z, 961Z, 963Z)

Approved DRG Issues​

An approved DRG result is compared with the claimed DRG. Its comparison issue uses the same endings as the provider issues, with the prefix CLAIMED_DRG_, at level INFO: a difference here is the expected effect of rejected procedures, not an error.

CodeLevelMeaningExample message
CLAIMED_DRG_MATCHINFOThe approved DRG equals the claimed DRGThe approved DRG F10B equals the claimed DRG.
CLAIMED_DRG_INTERVENTION_MISSINGINFOThe claimed DRG was surgical; after the decisions no approved procedure leads to a surgical DRGThe claimed DRG F10B is surgical, but no approved procedure qualifies for one, so the approved DRG is F60A (…), a medical DRG. Procedures not approved: 38306-00-00.
CLAIMED_DRG_…INFOEvery other ending of the provider table, for approved against claimed
CLAIMED_DRG_NOT_AVAILABLEINFOThe claimed DRG could not be calculated, so the approved DRG is not compared

… marks text shortened here; the full messages name the DRG descriptions.

Status​

status gives the outcome of one DRG calculation, separate from the grouper's own grouper_status.

ValueMeaning
GROUPEDA DRG was assigned
UNGROUPABLEThe episode grouped to an error DRG (960Z, 961Z, 963Z). See issues for the reason
ERRORDRG grouping could not run. drg_result is null, and issues holds the ERROR issue with an E_DRG_ code. In pre-auth and batch, the prior authorization or claim is still processed

Data Rules​

Dates​

Send every date as a full ISO-8601 DateTime with the provider's timezone offset, for example 2026-02-21T00:30:00+03:00.

Age, length of stay and the same-day flag are calculated on the provider's local calendar date:

  • A value with an offset (+03:00) is read on the date written.
  • A value without a timezone (2026-02-21T00:30:00) is read on the date written.
  • A value in UTC (Z) is first converted to Saudi time (UTC+03:00).
Example

A patient admitted at 00:30 on 21 February in Riyadh, sent as 2026-02-20T21:30:00Z, is read as admitted on 21 February. Sending local dates with their offset avoids any ambiguity.

The time of day does not affect grouping. A discharge just after midnight counts as an extra day.

Length of stay​

Najeeb calculates the length of stay from encounter_start_date and encounter_end_date, minus leave_days. A same-day stay has a length of stay of 1, as defined by AR-DRG.

Length of stay sent and length of stay from the dates

If you also send drg_info.length_of_stay and it differs from the value calculated from the dates, Najeeb uses the smaller of the two, as AR-DRG requires, and returns a LENGTH_OF_STAY_MISMATCH warning.

Admission weight​

Admission weight matters only for patients under 1 year old. When none is sent for such a patient, AR-DRG uses 2500 g and Najeeb returns an ADMISSION_WEIGHT_MISSING warning.

Weight and ventilation hours in supporting info​

Send these values in drg_info. In the Pre-auth DRG Coder and the Stand-alone DRG Coder, they are also read from supporting_info when drg_info does not have them; drg_info always wins. The names differ between the two, so use this table:

drg_info fieldsupporting_info[].codevalueunit
admission_weightadmission-weight, or birth-weight for newbornsWhole number of grams as a string, for example "2350"g
mechanical_ventilation_hoursventilation-hoursWhole number of hours as a string, for example "36"h
"supporting_info": [
{ "code": "admission-weight", "value": "2350", "unit": "g" },
{ "code": "ventilation-hours", "value": "36", "unit": "h" }
]

The Claims Batch DRG Validator has no supporting_info. Use the claim-line fields instead.

Quantities​

Quantity never affects grouping. A partially accepted procedure counts as performed in the approved DRG. Quantity fields keep their usual meaning in the prior authorization and claim.

Limits​

ItemLimit
Diagnoses1–30, exactly one PRIMARY
Procedures0–30

Enums​

Kind​

ValueMeaning
CLAIMEDNajeeb's DRG of the whole prior authorization or claim
APPROVEDNajeeb's DRG of the approved procedures only
STANDALONEA Stand-alone DRG Coder result, linked to a prior authorization or claim or not. Never replaces their own DRGs

Trigger​

ValueWhen
CREATEThe prior authorization was created
RETRYThe prior authorization was retried with retry: true
AI_DECISIONNajeeb's AI review finished
AUTOMATIONAn automated decision changed the items
REVIEWER_UPDATEA reviewer changed item decisions in the Najeeb portal
INTEGRATION_UPDATEYour system changed item decisions through Update Prior Authorization
BATCH_CHUNKA claims batch was processed
CLAIM_REVIEWA claim's item decisions changed after the batch
MANUALA stand-alone request

Separation Mode​

ValueDescription
01Discharge or transfer to an acute hospital
02Discharge or transfer to a residential aged care service
03Discharge or transfer to a psychiatric hospital
04Discharge or transfer to other health care accommodation
05Statistical discharge — type change
06Left against medical advice
07Statistical discharge from leave
08Died
09Other, including discharge home

Grouper Status​

ValueDescription
00Normal grouping
01Invalid or missing principal diagnosis
02Diagnosis code cannot be used as principal diagnosis
03Episode does not meet criteria for any DRG
04Invalid age
05Invalid sex
06Invalid separation mode
07Invalid admission weight
08Invalid length of stay
09Invalid same-day field

Matching Reason​

Najeeb explains a difference from the coarsest to the finest, and reports the first that applies. "Compared DRG" is the provider DRG for a claimed result, and the claimed DRG for an approved result.

ValueMeaning
MATCHThe two DRGs are equal
NAJEEB_UNGROUPABLENajeeb could not group the episode, so nothing can be confirmed
PRE_MDCOne DRG is Pre-MDC (long ventilation, transplant, ECMO, tracheostomy) and the other is not
DIFFERENT_MDCDifferent body system (MDC). Caused by the principal diagnosis
INTERVENTION_MISSINGThe compared DRG is surgical; Najeeb's is medical because no qualifying procedure was sent or approved
INTERVENTION_EXTRANajeeb's DRG is surgical because of a procedure; the compared DRG is medical
DIFFERENT_ADRGSame body system and partition, different base group. matching_split_reason says what decided it
DIFFERENT_SPLITSame base group, different level. matching_split_reason says what decided it, usually COMPLEXITY

Split Reason​

ValueTest on
COMPLEXITYThe complexity score (ECCS), from the additional diagnoses
WEIGHTThe newborn's admission weight
VENTILATIONThe hours of mechanical ventilation
SEPARATIONThe separation mode or the length of stay
SAMEDAYThe same-day flag
AGEThe patient's age
PROCEDUREA group of procedures
DIAGNOSISA group of diagnoses
OTHERAny other test

MDC​

CodeDescription
00Unassignable to MDC
01Diseases & Disorders of the Nervous System
02Diseases & Disorders of the Eye
03Diseases & Disorders of the Ear, Nose, Mouth & Throat
04Diseases & Disorders of the Respiratory System
05Diseases & Disorders of the Circulatory System
06Diseases & Disorders of the Digestive System
07Diseases & Disorders of the Hepatobiliary System & Pancreas
08Diseases & Disorders of the Musculoskeletal System & Connective Tissue
09Diseases & Disorders of the Skin, Subcutaneous Tissue & Breast
10Endocrine, Nutritional & Metabolic Diseases & Disorders
11Diseases & Disorders of the Kidney & Urinary Tract
12Diseases & Disorders of the Male Reproductive System
13Diseases & Disorders of the Female Reproductive System
14Pregnancy, Childbirth & the Puerperium
15Newborns & Other Neonates
16Diseases & Disorders of Blood, Blood Forming Organs, Immunological Disorders
17Neoplastic Disorders (Haematological & Solid Neoplasms)
18Infectious & Parasitic Diseases, Systemic or Unspecified Sites
19Mental Diseases & Disorders
20Alcohol/Drug Use & Alcohol/Drug Induced Organic Mental Disorders
21Injuries, Poisonings & Toxic Effects of Drugs
22Burns
23Factors Influencing Health Status & Other Contacts with Health Services