Results for “per_medical_assessment_api”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.PER_MEDICAL_ASSESSMENT_API package body is a public PL/SQL API belonging to the Oracle Human Resources (PER) module, specifically the Oracle HRMS Occupational Health / Medical Assessment functionality. Its business purpose is to provide a programmatic, server-side interface for creating, updating, and deleting medical assessment records associated with employees, applicants, and other persons defined in Oracle EBS. Medical assessments capture the outcome of occupational health consultations — including consultation dates, examiners, consultation results, associated incidents or disabilities, and follow-up dates — and this API encapsulates the DML and validation logic required to maintain that data consistently. Rather than allowing direct inserts or updates against the underlying table, Oracle EBS exposes this package so that form-level logic, concurrent processes, and custom integrations can manipulate medical assessment information through a controlled, supported entry point. The package carries the $Header marker indicating an original version in the PER product family, and, like other PER APIs, it is intended to respect the effective-dating and validation conventions of Oracle HRMS.

Key Procedures and Functions

The package exposes three documented procedures, all following the standard Oracle HRMS API naming convention:

• CREATE_MEDICAL_ASSESSMENT — Inserts a new medical assessment record. It accepts the person identifier, effective date, consultation details (date, type, result), examiner and organization information, optional references to an incident or disability, a next consultation date, a description, and a full descriptive flexfield attribute set. The p_validate parameter allows the caller to run the procedure in validation-only mode, rolling back the insert and reporting whether the operation would succeed.
• UPDATE_MEDICAL_ASSESSMENT — Modifies an existing medical assessment record identified by the appropriate primary key and effective date, applying the same validation and date-tracking conventions used at creation. It is the supported route for correcting consultation outcomes, rescheduling follow-ups, or adjusting flexfield attribute values.
• DELETE_MEDICAL_ASSESSMENT — Removes a medical assessment record, typically subject to the validation rules and referential constraints defined for the entity, and is likewise invocable in validate-only mode to confirm deletion is permissible before committing.

The parameter signatures are not reproduced here beyond the documented excerpt; callers should consult the package specification for the authoritative parameter list of each procedure.

Tables Accessed

The package operates on a single documented base table, accessed through its APPS synonym:

• PER_MEDICAL_ASSESSMENTS — The principal store of medical assessment rows. The CREATE_MEDICAL_ASSESSMENT procedure inserts into this table; UPDATE_MEDICAL_ASSESSMENT modifies existing rows; and DELETE_MEDICAL_ASSESSMENT removes them. All consultation, examiner, incident, disability, and flexfield columns map to attributes of this table.

No additional tables are documented as directly referenced through APPS synonyms within the metadata, although the API may indirectly rely on PER person and date-tracking objects through its validation logic.

Usage Notes

In Oracle EBS 12.1.1 and 12.2.2, this API is typically invoked from the Oracle HRMS Medical Assessment or Occupational Health forms, from concurrent programs that import or process health data, and from custom PL/SQL when integrating external occupational health systems. The metadata records that the package is referenced by four other packages, confirming its role as a reusable service layer rather than a standalone program. Because the package is classified as an API and owns only DML logic, callers are expected to supply a valid effective date, a person identifier, and consultation data, and to handle the p_validate pattern to preview results before committing. Direct DML against PER_MEDICAL_ASSESSMENTS should be avoided; the API is the supported interface. The search term "medCOM helth ONLINE" reflects a user searching for medical/com health functionality online, which maps to this occupational health API rather than a distinct product component.