--- title: SAIF.Business.Claim.Maintenance operations and processes summary: Operation catalog and cross-operation hub for the claim-maintenance business objects. status: draft owner: SAIF Doc Gen last_reviewed: 2026-07-30 library: SAIF.Business.Claim.Maintenance reference_type: package --- # SAIF.Business.Claim.Maintenance operations and processes This page is the operation catalog and cross-operation hub for `SAIF.Business.Claim.Maintenance`. The library exposes twelve operations covering claim-header maintenance, accident/injury data, claim adjustments executed through Oracle packages, and the ancillary collections (support orders, vocational data, disability activity, work release/status, medical conditions, COVID-19 testing, policy history, attending physicians) that hang off a claim. Each operation's detailed, step-by-step logic lives in its own page under `operations/`. ## Operation catalog | Operation | Intent | Trigger | Inputs | Outputs | Rules | Tables | SQL | | --- | --- | --- | --- | --- | --- | --- | --- | | [Claim detail CRUD](operations/claim-detail-crud.md) | Retrieve and update the core claim header and its dependent child collections | `clsClaimDetail.GetClaimDetail(dpi, claimID)` followed by property edits and `Save()` | `ClaimID`, mutable `CL_INJURY_CLAIM` header fields, `UpdateNum`, `IDataPortalInfo` | Populated claim-detail object; persisted header update; derived pharmacy/legal-rep/policy side effects | [BR-CM-001](business-rules.md#br-cm-001-optimistic-concurrency-updates-fail-if-rowsaffected-1), [BR-CM-009](business-rules.md#br-cm-009-injury-occupational-disease-code-must-be-i-or-d), [BR-CM-010](business-rules.md#br-cm-010-active-claim-flag-must-be-y-or-n), [BR-CM-011](business-rules.md#br-cm-011-knowledge-date-is-required-and-bounded-by-injury-date-and-today), [BR-CM-012](business-rules.md#br-cm-012-disability-date-must-not-precede-injury-date-or-be-in-the-future), [BR-CM-013](business-rules.md#br-cm-013-coverage-code-must-be-a-b-c-or-e), [BR-CM-014](business-rules.md#br-cm-014-handicap-worker-reserve-flag-must-be-y-or-n), [BR-CM-015](business-rules.md#br-cm-015-wcd-claim-number-must-be-unique-across-claims), [BR-CM-016](business-rules.md#br-cm-016-claim-status-code-must-be-new-open-closed-or-denied), [BR-CM-017](business-rules.md#br-cm-017-state-occupational-disease-ppd-or-ptd-claims-require-a-disability-or-initial-treatment-date), [BR-CM-018](business-rules.md#br-cm-018-aggravation-decision-on-a-disabling-claim-requires-a-closed-status), [BR-CM-019](business-rules.md#br-cm-019-owcp-claim-number-must-be-unique-per-worker), [BR-CM-020](business-rules.md#br-cm-020-claim-status-may-not-change-without-at-least-one-condition), [BR-CM-021](business-rules.md#br-cm-021-claim-status-may-not-close-while-the-latest-decision-is-deferred), [BR-CM-022](business-rules.md#br-cm-022-medicare-orm-termination-date-must-fall-between-injury-date-and-seven-days-ahead), [BR-CM-023](business-rules.md#br-cm-023-disabling-occupational-disease-claims-should-have-a-disability-date), [BR-CM-024](business-rules.md#br-cm-024-disability-date-changes-require-wage-re-verification), [BR-CM-025](business-rules.md#br-cm-025-aggravation-request-after-aggravation-rights-end-date-warns-of-own-motion), [BR-CM-026](business-rules.md#br-cm-026-non-disabling-to-disabling-change-within-365-days-warns-the-user), [BR-CM-027](business-rules.md#br-cm-027-closing-a-claim-without-a-medically-stationary-date-warns-the-user), [BR-CM-028](business-rules.md#br-cm-028-aggravation-decision-change-warns-of-a-possible-aggravation-decision), [BR-CM-029](business-rules.md#br-cm-029-closing-or-denying-a-claim-sets-pharmacy-eligibility-to-ineligible), [BR-CM-030](business-rules.md#br-cm-030-denying-a-claim-sets-the-medicare-orm-termination-date-and-reopening-clears-it), [BR-CM-031](business-rules.md#br-cm-031-reopening-a-claim-with-a-cda-order-warns-the-user), [BR-CM-032](business-rules.md#br-cm-032-ohs-or-suspended-pharmacy-status-requires-majoris-enrollment), [BR-CM-033](business-rules.md#br-cm-033-caremark-or-denied-pharmacy-status-requires-caremark-enrollment), [BR-CM-034](business-rules.md#br-cm-034-formal-mco-enrollment-sets-the-matching-pharmacy-formulary-code), [BR-CM-035](business-rules.md#br-cm-035-accepted-claim-decision-derives-pharmacy-eligibility-from-mco-plan), [BR-CM-036](business-rules.md#br-cm-036-reopening-a-closed-claim-resets-pharmacy-eligibility-status), [BR-CM-037](business-rules.md#br-cm-037-first-accept-or-deny-decision-copies-responsible-adjuster-to-compensability-adjuster), [BR-CM-038](business-rules.md#br-cm-038-jurisdiction-code-transitions-cascade-related-identifier-fields), [BR-CM-039](business-rules.md#br-cm-039-deactivating-a-claim-auto-terminates-open-legal-representation) | [CL_INJURY_CLAIM](database-tables.md#cl_injury_claim), [CL_MERGED_CLAIM](database-tables.md#cl_merged_claim), [CL_MEDICAL_CONDITION](database-tables.md#cl_medical_condition), [CL_CLAIM_LEGAL_REPRESENTATIVE](database-tables.md#cl_claim_legal_representative), [MCO_GSA_LOCATION](database-tables.md#mco_gsa_location), [CL_CLAIM_PERSON](database-tables.md#cl_claim_person), [CL_BENEFIT_PERIOD](database-tables.md#cl_benefit_period) | [SQL-032](sql/SQL-032.md), [SQL-033](sql/SQL-033.md), [SQL-034](sql/SQL-034.md), [SQL-035](sql/SQL-035.md), [SQL-036](sql/SQL-036.md), [SQL-037](sql/SQL-037.md), [SQL-038](sql/SQL-038.md), [SQL-039](sql/SQL-039.md), [SQL-040](sql/SQL-040.md), [SQL-041](sql/SQL-041.md), [SQL-086](sql/SQL-086.md), [SQL-087](sql/SQL-087.md) | | [Accident injury management](operations/accident-injury-management.md) | Maintain injury date, injury circumstances, and injury address on a claim | `clsAccidentInjury.GetAccidentInjury(dpi, claimID)` followed by property edits and `Save()` | `ClaimID`, injury/exposure fields, injury address, supporting claim dates | Updated `CL_INJURY_CLAIM` row; conditional three-day-wait deletion; federal awards set to pending | [BR-CM-001](business-rules.md#br-cm-001-optimistic-concurrency-updates-fail-if-rowsaffected-1), [BR-CM-040](business-rules.md#br-cm-040-injury-date-is-required-when-modified), [BR-CM-041](business-rules.md#br-cm-041-injury-date-more-than-one-year-in-the-past-warns-the-user), [BR-CM-042](business-rules.md#br-cm-042-another-claim-within-fourteen-days-for-the-same-worker-warns-the-user), [BR-CM-043](business-rules.md#br-cm-043-initial-treatment-date-change-on-a-disease-claim-requires-wage-re-verification), [BR-CM-044](business-rules.md#br-cm-044-injury-date-may-not-follow-the-knowledge-date), [BR-CM-045](business-rules.md#br-cm-045-injury-date-may-not-follow-the-801-received-date), [BR-CM-046](business-rules.md#br-cm-046-injury-date-may-not-follow-the-stamped-in-received-date), [BR-CM-047](business-rules.md#br-cm-047-injury-date-may-not-follow-the-leave-work-date), [BR-CM-048](business-rules.md#br-cm-048-injury-date-may-not-precede-the-worker-birth-date), [BR-CM-049](business-rules.md#br-cm-049-injury-date-may-not-follow-the-worker-death-date), [BR-CM-050](business-rules.md#br-cm-050-injury-date-may-not-follow-a-work-release-date), [BR-CM-051](business-rules.md#br-cm-051-injury-date-may-not-follow-a-decision-request-effective-date), [BR-CM-052](business-rules.md#br-cm-052-injury-date-may-not-follow-a-disability-authorization-activity-date), [BR-CM-053](business-rules.md#br-cm-053-injury-date-may-not-follow-a-medically-stationary-date), [BR-CM-054](business-rules.md#br-cm-054-injury-date-may-not-follow-the-disability-date-on-injury-claims), [BR-CM-055](business-rules.md#br-cm-055-ppd-or-ptd-occupational-disease-claims-require-a-disability-or-initial-treatment-date), [BR-CM-056](business-rules.md#br-cm-056-initial-treatment-date-must-fall-between-1850-and-today), [BR-CM-057](business-rules.md#br-cm-057-injury-date-may-not-change-while-unposted-payments-or-adjustments-exist), [BR-CM-058](business-rules.md#br-cm-058-missing-policy-coverage-at-injury-date-warns-the-user) | [CL_INJURY_CLAIM](database-tables.md#cl_injury_claim), [CL_CLAIM_PERSON](database-tables.md#cl_claim_person), [ZIP_MCO_COUNTY](database-tables.md#zip_mco_county), [CL_DISABILITY_AUTH_ACTIVITY](database-tables.md#cl_disability_auth_activity), [CL_MEDICAL_CONDITION](database-tables.md#cl_medical_condition), [CL_CLAIM_REQUEST_DECISION](database-tables.md#cl_claim_request_decision), [CL_CLAIM_WORK_RELEASE_STATUS](database-tables.md#cl_claim_work_release_status), [CL_CLAIM_TD_THREE_DAY_WAIT](database-tables.md#cl_claim_td_three_day_wait) | [SQL-021](sql/SQL-021.md), [SQL-022](sql/SQL-022.md), [SQL-023](sql/SQL-023.md), [SQL-024](sql/SQL-024.md), [SQL-025](sql/SQL-025.md), [SQL-026](sql/SQL-026.md), [SQL-027](sql/SQL-027.md), [SQL-081](sql/SQL-081.md), [SQL-106](sql/SQL-106.md) | | [Claim adjustment](operations/claim-adjustment.md) | Void, combine, transfer, or restore a claim through `PK82140_CLAIM_ADJUSTMENTS` | Caller selects an `AdjustmentAction`, populates the matching context objects, and calls `Save()` | Adjustment type selector, current claim, combine claim, transfer worker and claim collection, acting user | Stored-function row count per adjustment; broken rules on validation or contention failure | [BR-CM-007](business-rules.md#br-cm-007-void-combine-transfer-restore-are-mutually-exclusive-adjustment-operations), [BR-PROC-001](business-rules.md#br-proc-001-claim-void-requests-must-provide-the-claim-identifier-current-update-number-and-acting-u), [BR-PROC-002](business-rules.md#br-proc-002-claim-combine-requests-must-identify-both-the-source-claim-and-the-claim-to-combine-into), [BR-PROC-003](business-rules.md#br-proc-003-claim-transfer-and-restore-flows-require-a-target-worker-identifier-in-addition-to-claim-v) | [CL_INJURY_CLAIM](database-tables.md#cl_injury_claim), [CL_CLAIM_PERSON](database-tables.md#cl_claim_person) | [SQL-029](sql/SQL-029.md), [SQL-030](sql/SQL-030.md), [SQL-031](sql/SQL-031.md), [SQL-082](sql/SQL-082.md), [SQL-083](sql/SQL-083.md), [SQL-084](sql/SQL-084.md), [SQL-085](sql/SQL-085.md) | | [Support order management](operations/support-order-management.md) | Create, update, delete, and connect child-support withholding orders for a worker | Caller invokes the support-order factories or collection retrieve and calls `Save()` | `WorkerID`, order fields, selected claim connections, acting user | Persisted support order and connection rows; generated to-do tasks; validation errors and warnings | [BR-CM-001](business-rules.md#br-cm-001-optimistic-concurrency-updates-fail-if-rowsaffected-1), [BR-CM-002](business-rules.md#br-cm-002-support-order-cannot-be-deleted-if-awards-exist-for-the-suo-claim), [BR-CM-003](business-rules.md#br-cm-003-support-order-cannot-be-deleted-if-payments-exist-for-the-suo-claim), [BR-CM-004](business-rules.md#br-cm-004-support-order-validates-payment-about-to-be-issued-status-before-changes), [BR-CM-005](business-rules.md#br-cm-005-benefit-payee-must-exist-for-support-order-before-payment-processing), [BR-CM-006](business-rules.md#br-cm-006-award-reduction-validation-before-support-order-modification), [BR-CM-008](business-rules.md#br-cm-008-claims-with-status-i-in-progress-or-v-voided-are-excluded-from-support-order-claim) | [CL_CLAIM_SUPPORT_ORDER_CONN](database-tables.md#cl_claim_support_order_conn), [CL_INJURY_CLAIM](database-tables.md#cl_injury_claim), [DUAL](database-tables.md#dual) | [SQL-001](sql/SQL-001.md), [SQL-002](sql/SQL-002.md), [SQL-008](sql/SQL-008.md), [SQL-009](sql/SQL-009.md), [SQL-049](sql/SQL-049.md), [SQL-050](sql/SQL-050.md), [SQL-051](sql/SQL-051.md), [SQL-052](sql/SQL-052.md), [SQL-054](sql/SQL-054.md), [SQL-055](sql/SQL-055.md), [SQL-056](sql/SQL-056.md), [SQL-057](sql/SQL-057.md), [SQL-058](sql/SQL-058.md), [SQL-059](sql/SQL-059.md), [SQL-060](sql/SQL-060.md), [SQL-092](sql/SQL-092.md), [SQL-110](sql/SQL-110.md), [SQL-111](sql/SQL-111.md) | | [Vocational data retrieval](operations/vocational-data-retrieval.md) | Load and maintain the vocational-detail history for a claim | `clsVocationalDetailCollection.GetVocationalDetails(dpi, claimID)` and collection `Save()` | `ClaimID`, vocational status/date, rehab provider, counselor, responsibility code | Populated vocational-detail collection; inserted/updated/deleted detail rows; synchronized claim responsibility code | [BR-CM-001](business-rules.md#br-cm-001-optimistic-concurrency-updates-fail-if-rowsaffected-1) | [VOCATIONAL_DETAIL](database-tables.md#vocational_detail), [CL_INJURY_CLAIM](database-tables.md#cl_injury_claim) | [SQL-017](sql/SQL-017.md), [SQL-073](sql/SQL-073.md), [SQL-099](sql/SQL-099.md), [SQL-118](sql/SQL-118.md) | | [Vocational coordinators](operations/vocational-coordinators.md) | Resolve and cache the vocational reference lists used to validate a vocational detail | Any read of the coordinator, provider, status, or status-detail lists, or rule evaluation during `IsValid` | `IDataPortalInfo` only — the lookups are process-wide reference data | Cached coordinator, provider, status, and status-detail lookups; resolved display names; validation errors | None catalogued* | None documented* | None catalogued* | | [Disability activity tracking](operations/disability-activity-tracking.md) | Maintain disability status activity and disability authorization activity history for a claim | Caller retrieves either activity collection, edits or adds items, and calls `Save()` | `ClaimID`, disability date, authorization reason code and date, sequence numbers, `UpdateNum` | Persisted activity rows; latest/current activity items; max disability date used by the claim header | [BR-CM-001](business-rules.md#br-cm-001-optimistic-concurrency-updates-fail-if-rowsaffected-1) | [CL_CLAIM_DISABILITY_ACTIVITY](database-tables.md#cl_claim_disability_activity), [CL_DISABILITY_AUTH_ACTIVITY](database-tables.md#cl_disability_auth_activity), [CL_INJURY_CLAIM](database-tables.md#cl_injury_claim) | [SQL-003](sql/SQL-003.md), [SQL-013](sql/SQL-013.md), [SQL-042](sql/SQL-042.md), [SQL-043](sql/SQL-043.md), [SQL-064](sql/SQL-064.md), [SQL-065](sql/SQL-065.md), [SQL-088](sql/SQL-088.md), [SQL-095](sql/SQL-095.md), [SQL-107](sql/SQL-107.md), [SQL-114](sql/SQL-114.md) | | [Work release/status management](operations/work-release-status-management.md) | Maintain work release and work status history under the injury-claim aggregate | Caller retrieves `clsWorkStatusInjuryClaim`, adds or edits rows, and calls `Save()` | `ClaimID`, work release/status codes and dates, sequence numbers, `UpdateNum`, leave-work date | Persisted work release and work status rows; updated claim header dates; broken-rule collection | [BR-CM-001](business-rules.md#br-cm-001-optimistic-concurrency-updates-fail-if-rowsaffected-1) | [CL_CLAIM_WORK_RELEASE_STATUS](database-tables.md#cl_claim_work_release_status), [CL_CLAIM_WORK_STATUS](database-tables.md#cl_claim_work_status), [CL_INJURY_CLAIM](database-tables.md#cl_injury_claim) | [SQL-018](sql/SQL-018.md), [SQL-019](sql/SQL-019.md), [SQL-074](sql/SQL-074.md), [SQL-075](sql/SQL-075.md), [SQL-076](sql/SQL-076.md), [SQL-100](sql/SQL-100.md), [SQL-101](sql/SQL-101.md), [SQL-102](sql/SQL-102.md), [SQL-119](sql/SQL-119.md), [SQL-120](sql/SQL-120.md) | | [Medical condition management](operations/medical-condition-management.md) | Maintain medical conditions, omitted conditions, and their compensability decision history | Caller retrieves the condition collections, edits conditions or decisions, and calls `Save()` | Claim data, condition fields, diagnosis codes, decision and denial fields | Persisted condition, decision, and omitted-condition rows; generated claim tasks; validation messages | [BR-CM-001](business-rules.md#br-cm-001-optimistic-concurrency-updates-fail-if-rowsaffected-1) | [CL_MEDICAL_CONDITION](database-tables.md#cl_medical_condition), [CL_COND_COMPENSABILITY_DECISN](database-tables.md#cl_cond_compensability_decisn), [CL_OMITTED_COND_DENIED](database-tables.md#cl_omitted_cond_denied), [CBP_DIAGNOSIS](database-tables.md#cbp_diagnosis) | [SQL-011](sql/SQL-011.md), [SQL-014](sql/SQL-014.md), [SQL-015](sql/SQL-015.md), [SQL-062](sql/SQL-062.md), [SQL-067](sql/SQL-067.md), [SQL-068](sql/SQL-068.md), [SQL-069](sql/SQL-069.md), [SQL-071](sql/SQL-071.md), [SQL-094](sql/SQL-094.md), [SQL-096](sql/SQL-096.md), [SQL-097](sql/SQL-097.md), [SQL-115](sql/SQL-115.md), [SQL-116](sql/SQL-116.md) | | [COVID-19 testing history](operations/covid-19-testing-history.md) | Append and read the COVID-19 testing history for a claim | `NewCovid19TestingHistory` or `GetCovid19TestingHistoryCollection`, followed by `Save()` | `ClaimID`, tested-for-COVID-19 flag, test result code, acting user | Inserted testing-history rows; history collection ordered by create date descending | None registered* | [CL_COVID19_TESTING_HISTORY](database-tables.md#cl_covid19_testing_history) | [SQL-012](sql/SQL-012.md), [SQL-063](sql/SQL-063.md) | | [Policy history tracking](operations/policy-history-tracking.md) | Record policy-number changes on a claim as an append-only policy history | Caller sets `clsClaimPolicy.PolicyNum` and calls `Save()`; the history page retrieves read-only | `ClaimID`, new policy number, policy sub-code, acting user | Updated claim header policy fields; inserted policy-history rows; in-memory history collection | [BR-CM-001](business-rules.md#br-cm-001-optimistic-concurrency-updates-fail-if-rowsaffected-1) | [CL_INJURY_CLAIM](database-tables.md#cl_injury_claim), [CL_CLAIM_POLICY_HISTORY](database-tables.md#cl_claim_policy_history) | [SQL-005](sql/SQL-005.md), [SQL-045](sql/SQL-045.md), [SQL-046](sql/SQL-046.md), [SQL-089](sql/SQL-089.md) | | [Attending physician retrieval](operations/attending-physician-retrieval.md) | Read attending physicians and alternate care providers for a claim from the claim-contacts API | `clsAttendingPhysicianCollection.GetAttendingPhysicians(dpi, claimID)` | `IDataPortalInfo`, `ClaimID` | Read-only collection of attending physicians with resolved termination reasons | None documented* | [ATTENDING_PHYS_EXP_REASON_CODE](database-tables.md#attending_phys_exp_reason_code) | [SQL-028](sql/SQL-028.md) | ## Process flow diagram The following diagram shows how the twelve operations relate across the claim-maintenance lifecycle: a claim is retrieved, its header and injury data are maintained, ancillary collections are edited, adjustments are executed through Oracle packages, and all changes converge on a save that enforces optimistic concurrency. ```mermaid flowchart TD Start([Caller requests claim maintenance]) --> Retrieve[Retrieve claim context
by ClaimID or WorkerID] Retrieve --> Header[Claim header maintenance] Header --> Detail[Claim detail CRUD] Header --> Injury[Accident injury management] Header --> Policy[Policy history tracking] Retrieve --> Ancillary[Ancillary claim collections] Ancillary --> Conditions[Medical condition management] Ancillary --> Disability[Disability activity tracking] Ancillary --> WorkRel[Work release and status management] Ancillary --> Voc[Vocational data retrieval] Voc --> VocRef[Vocational coordinators
cached reference lookups] Ancillary --> Covid[COVID-19 testing history] Ancillary --> Support[Support order management] Retrieve --> External[Attending physician retrieval
claim contacts API] Retrieve --> Adjust{Claim adjustment
requested?} Adjust -->|Yes| Proc[Void, combine, transfer,
or restore via PK82140] Adjust -->|No| Edit[Caller edits properties] Detail --> Edit Injury --> Edit Policy --> Edit Conditions --> Edit Disability --> Edit WorkRel --> Edit Voc --> Edit Covid --> Edit Support --> Edit Edit --> Validate{Validation rules pass?} Validate -->|No| Errors([Broken rules returned;
changes retained in memory]) Validate -->|Yes| Save[Save cascade:
children then header] Save --> Concurrency{RowsAffected = 1?} Proc --> Concurrency Concurrency -->|Yes| Done([Changes persisted;
objects marked clean]) Concurrency -->|No| Contention([DB contention error added;
save reported as failed]) External --> ReadOnly([Read-only projection returned]) ``` ## Database interactions The following table summarizes which operations read from or write to the database. Per-step SQL and table citations live in each operation's detail page under `operations/`. | Operation | SQL | Tables | Type | | --- | --- | --- | --- | | [Claim detail CRUD](operations/claim-detail-crud.md) | [SQL-032](sql/SQL-032.md), [SQL-033](sql/SQL-033.md), [SQL-034](sql/SQL-034.md), [SQL-035](sql/SQL-035.md), [SQL-036](sql/SQL-036.md), [SQL-037](sql/SQL-037.md), [SQL-038](sql/SQL-038.md), [SQL-039](sql/SQL-039.md), [SQL-040](sql/SQL-040.md), [SQL-041](sql/SQL-041.md), [SQL-086](sql/SQL-086.md), [SQL-087](sql/SQL-087.md) | [CL_INJURY_CLAIM](database-tables.md#cl_injury_claim), [CL_MERGED_CLAIM](database-tables.md#cl_merged_claim), [CL_MEDICAL_CONDITION](database-tables.md#cl_medical_condition), [CL_CLAIM_LEGAL_REPRESENTATIVE](database-tables.md#cl_claim_legal_representative), [MCO_GSA_LOCATION](database-tables.md#mco_gsa_location), [CL_CLAIM_PERSON](database-tables.md#cl_claim_person), [CL_BENEFIT_PERIOD](database-tables.md#cl_benefit_period) | Read / Write | | [Accident injury management](operations/accident-injury-management.md) | [SQL-021](sql/SQL-021.md), [SQL-022](sql/SQL-022.md), [SQL-023](sql/SQL-023.md), [SQL-024](sql/SQL-024.md), [SQL-025](sql/SQL-025.md), [SQL-026](sql/SQL-026.md), [SQL-027](sql/SQL-027.md), [SQL-081](sql/SQL-081.md), [SQL-106](sql/SQL-106.md) | [CL_INJURY_CLAIM](database-tables.md#cl_injury_claim), [ZIP_MCO_COUNTY](database-tables.md#zip_mco_county), [CL_CLAIM_TD_THREE_DAY_WAIT](database-tables.md#cl_claim_td_three_day_wait) | Read / Write | | [Claim adjustment](operations/claim-adjustment.md) | [SQL-029](sql/SQL-029.md), [SQL-030](sql/SQL-030.md), [SQL-031](sql/SQL-031.md), [SQL-082](sql/SQL-082.md), [SQL-083](sql/SQL-083.md), [SQL-084](sql/SQL-084.md), [SQL-085](sql/SQL-085.md) | [CL_INJURY_CLAIM](database-tables.md#cl_injury_claim), [CL_CLAIM_PERSON](database-tables.md#cl_claim_person) | Read / Write (stored procedure) | | [Support order management](operations/support-order-management.md) | [SQL-001](sql/SQL-001.md), [SQL-008](sql/SQL-008.md), [SQL-009](sql/SQL-009.md), [SQL-054](sql/SQL-054.md), [SQL-059](sql/SQL-059.md), [SQL-060](sql/SQL-060.md), [SQL-092](sql/SQL-092.md), [SQL-110](sql/SQL-110.md), [SQL-111](sql/SQL-111.md) | [CL_CLAIM_SUPPORT_ORDER_CONN](database-tables.md#cl_claim_support_order_conn), [CL_INJURY_CLAIM](database-tables.md#cl_injury_claim), [DUAL](database-tables.md#dual) | Read / Write (stored procedure) | | [Vocational data retrieval](operations/vocational-data-retrieval.md) | [SQL-017](sql/SQL-017.md), [SQL-073](sql/SQL-073.md), [SQL-099](sql/SQL-099.md), [SQL-118](sql/SQL-118.md) | [VOCATIONAL_DETAIL](database-tables.md#vocational_detail), [CL_INJURY_CLAIM](database-tables.md#cl_injury_claim) | Read / Write | | [Vocational coordinators](operations/vocational-coordinators.md) | None catalogued* | None documented* | Read (cached reference data) | | [Disability activity tracking](operations/disability-activity-tracking.md) | [SQL-003](sql/SQL-003.md), [SQL-013](sql/SQL-013.md), [SQL-042](sql/SQL-042.md), [SQL-043](sql/SQL-043.md), [SQL-064](sql/SQL-064.md), [SQL-065](sql/SQL-065.md), [SQL-088](sql/SQL-088.md), [SQL-095](sql/SQL-095.md), [SQL-107](sql/SQL-107.md), [SQL-114](sql/SQL-114.md) | [CL_CLAIM_DISABILITY_ACTIVITY](database-tables.md#cl_claim_disability_activity), [CL_DISABILITY_AUTH_ACTIVITY](database-tables.md#cl_disability_auth_activity), [CL_INJURY_CLAIM](database-tables.md#cl_injury_claim) | Read / Write | | [Work release/status management](operations/work-release-status-management.md) | [SQL-018](sql/SQL-018.md), [SQL-019](sql/SQL-019.md), [SQL-074](sql/SQL-074.md), [SQL-075](sql/SQL-075.md), [SQL-076](sql/SQL-076.md), [SQL-100](sql/SQL-100.md), [SQL-101](sql/SQL-101.md), [SQL-102](sql/SQL-102.md), [SQL-119](sql/SQL-119.md), [SQL-120](sql/SQL-120.md) | [CL_CLAIM_WORK_RELEASE_STATUS](database-tables.md#cl_claim_work_release_status), [CL_CLAIM_WORK_STATUS](database-tables.md#cl_claim_work_status), [CL_INJURY_CLAIM](database-tables.md#cl_injury_claim) | Read / Write | | [Medical condition management](operations/medical-condition-management.md) | [SQL-011](sql/SQL-011.md), [SQL-014](sql/SQL-014.md), [SQL-015](sql/SQL-015.md), [SQL-062](sql/SQL-062.md), [SQL-067](sql/SQL-067.md), [SQL-068](sql/SQL-068.md), [SQL-069](sql/SQL-069.md), [SQL-071](sql/SQL-071.md), [SQL-094](sql/SQL-094.md), [SQL-096](sql/SQL-096.md), [SQL-097](sql/SQL-097.md), [SQL-115](sql/SQL-115.md), [SQL-116](sql/SQL-116.md) | [CL_MEDICAL_CONDITION](database-tables.md#cl_medical_condition), [CL_COND_COMPENSABILITY_DECISN](database-tables.md#cl_cond_compensability_decisn), [CL_OMITTED_COND_DENIED](database-tables.md#cl_omitted_cond_denied), [CBP_DIAGNOSIS](database-tables.md#cbp_diagnosis) | Read / Write | | [COVID-19 testing history](operations/covid-19-testing-history.md) | [SQL-012](sql/SQL-012.md), [SQL-063](sql/SQL-063.md) | [CL_COVID19_TESTING_HISTORY](database-tables.md#cl_covid19_testing_history) | Read / Insert only | | [Policy history tracking](operations/policy-history-tracking.md) | [SQL-005](sql/SQL-005.md), [SQL-045](sql/SQL-045.md), [SQL-046](sql/SQL-046.md), [SQL-089](sql/SQL-089.md) | [CL_INJURY_CLAIM](database-tables.md#cl_injury_claim), [CL_CLAIM_POLICY_HISTORY](database-tables.md#cl_claim_policy_history) | Read / Write (history is insert only) | | [Attending physician retrieval](operations/attending-physician-retrieval.md) | [SQL-028](sql/SQL-028.md) | [ATTENDING_PHYS_EXP_REASON_CODE](database-tables.md#attending_phys_exp_reason_code) | Read (plus external REST call) | ## Stored procedure operations Operations implemented in Oracle packages referenced by this library. | Operation | Description | Source | Link | | --- | --- | --- | --- | | Void claim | Voids an active claim and returns a rows-affected count for the contention check. | `PK82140_CLAIM_ADJUSTMENTS.VoidClaim` | [Details](procedures/pk82140_claim_adjustments.md#operations) | | Combine claim | Combines the current claim into another claim for the same worker and policy. | `PK82140_CLAIM_ADJUSTMENTS.CombineClaim` | [Details](procedures/pk82140_claim_adjustments.md#operations) | | Transfer claim | Transfers one claim at a time to a different worker. | `PK82140_CLAIM_ADJUSTMENTS.TransferClaim` | [Details](procedures/pk82140_claim_adjustments.md#operations) | | Restore claim | Restores a voided claim to its own current worker. | `PK82140_CLAIM_ADJUSTMENTS.RestoreClaim` | [Details](procedures/pk82140_claim_adjustments.md#operations) | | Support order persistence and checks | Insert, update, delete, award/payment existence checks, connection reads, and to-do task determination for support orders.* | `PK82141_SUPPORT_ORDER.*` | [Details](procedures/pk82141_support_order.md) | | Vocational data reads | Vocational-detail retrieval by claim and the coordinator reference list.* | `PK82003_VOCDATA.*` | [Details](procedures/pk82003_vocdata.md) | ## Failure and edge-case behavior - Optimistic concurrency is the dominant failure mode: every persisting operation checks the affected row count and adds a DB contention error instead of throwing ([BR-CM-001](business-rules.md#br-cm-001-optimistic-concurrency-updates-fail-if-rowsaffected-1)). Detailed per-operation behavior is documented on each operation page. - Retrieve paths generally return an empty or unfilled object when no row matches, rather than raising a not-found error; callers must check the populated state themselves. - Warning-severity rules (nearby-claim, payment-about-to-be-issued, closed-claim medically-stationary date, policy coverage) surface messages without blocking the save. - Claim transfer is the only adjustment that loops over multiple claims; it stops at the first contention failure and leaves the remaining claims untransferred. - `PK82141_SUPPORT_ORDER` and `PK82003_VOCDATA` could not be located in the Oracle catalog, so the behavior documented for those calls is derived from the VB call sites and parameter shapes rather than verified package bodies.* - Attending physician retrieval depends on an external REST service and is read-only; its collection save always returns false. ## Related documentation - [Index](index.md) - [Overview](overview.md) - [Architecture](architecture.md) - [Dependencies](dependencies.md) - [Business rules](business-rules.md) - [Database tables](database-tables.md) - [SQL catalog](sql/index.md) - [Procedures](procedures/index.md) - [API reference](api/index.md) > **Note:** Statements marked with `*` were inferred from code structure, naming > conventions, or contextual evidence where direct confirmation was not available > in source artifacts. ## Sources - `Business\SAIF.Business.Claim.Maintenance\clsClaimDetail.vb` - `Business\SAIF.Business.Claim.Maintenance\clsAccidentInjury.vb` - `Business\SAIF.Business.Claim.Maintenance\clsClaimAdjustment.vb` - `Business\SAIF.Business.Claim.Maintenance\clsClaimSupportOrder.vb` - `Business\SAIF.Business.Claim.Maintenance\clsClaimSupportOrderCollection.vb` - `Business\SAIF.Business.Claim.Maintenance\clsClaimSupportOrderConn.vb` - `Business\SAIF.Business.Claim.Maintenance\clsClaimSupportOrderConnCollection.vb` - `Business\SAIF.Business.Claim.Maintenance\clsVocationalDetail.vb` - `Business\SAIF.Business.Claim.Maintenance\clsVocationalDetailCollection.vb` - `Business\SAIF.Business.Claim.Maintenance\clsVocationalStatusDetail.vb` - `Business\SAIF.Business.Claim.Maintenance\clsClaimDisabilityActivity.vb` - `Business\SAIF.Business.Claim.Maintenance\clsClaimDisabilityActivityCollection.vb` - `Business\SAIF.Business.Claim.Maintenance\clsDisabilityAuthActivity.vb` - `Business\SAIF.Business.Claim.Maintenance\clsDisabilityAuthActivityCollection.vb` - `Business\SAIF.Business.Claim.Maintenance\clsWorkRelease.vb` - `Business\SAIF.Business.Claim.Maintenance\clsWorkReleaseCollection.vb` - `Business\SAIF.Business.Claim.Maintenance\clsWorkStatus.vb` - `Business\SAIF.Business.Claim.Maintenance\clsWorkStatusCollection.vb` - `Business\SAIF.Business.Claim.Maintenance\clsWorkStatusInjuryClaim.vb` - `Business\SAIF.Business.Claim.Maintenance\clsMedicalCondition.vb` - `Business\SAIF.Business.Claim.Maintenance\clsMedicalConditionCollection.vb` - `Business\SAIF.Business.Claim.Maintenance\clsOmittedCondition.vb` - `Business\SAIF.Business.Claim.Maintenance\clsOmittedConditionCollection.vb` - `Business\SAIF.Business.Claim.Maintenance\clsConditionDecision.vb` - `Business\SAIF.Business.Claim.Maintenance\clsConditionDecisionCollection.vb` - `Business\SAIF.Business.Claim.Maintenance\clsCovid19TestingHistory.vb` - `Business\SAIF.Business.Claim.Maintenance\clsCovid19TestingHistoryCollection.vb` - `Business\SAIF.Business.Claim.Maintenance\clsClaimPolicy.vb` - `Business\SAIF.Business.Claim.Maintenance\clsClaimPolicyHistory.vb` - `Business\SAIF.Business.Claim.Maintenance\clsClaimPolicyHistoryCollection.vb` - `Business\SAIF.Business.Claim.Maintenance\clsAttendingPhysician.vb` - `Business\SAIF.Business.Claim.Maintenance\clsAttendingPhysicianCollection.vb` - `Business\SAIF.Business.Claim.Maintenance\CCClaimDataApi\AttendingPhysicians.vb` - `Business\SAIF.Business.Claim.Maintenance\CCClaimDataApi\ClaimContactsResponse.vb` - `Business\SAIF.Business.Claim.Maintenance\CCClaimDataApi\Contact.vb` - `Business\SAIF.Business.Claim.Maintenance\CCClaimDataApi\ResponseData.vb` - `Business\SAIF.Business.Claim.Maintenance\CCClaimDataApi\WorkerRepresentatives.vb`