HCG Level Monitoring

The HCG Level Monitoring system allows users to track β-hCG (human Chorionic Gonadotropin) blood test results over time. This data is critical for calculating doubling times and assessing early pregnancy health.

Recording a Blood Test

Users can log HCG entries through the primary dashboard. The system supports both basic and advanced data entry to provide more granular risk assessments.

Basic Entry

Date: The date the blood sample was taken (stored in YYYY-MM-DD format).
HCG Value: The concentration of HCG in the blood (mIU/mL).
Notes: Optional field for context (e.g., "Tested at Quest Diagnostics").

Advanced Monitoring

By toggling the Advanced Details option, users can provide additional physiological data to improve calculation accuracy:

Last Menstrual Period (LMP): Used to calculate estimated gestational age.
Cycle Length: Adjustable between 21 and 45 days (default is 28). This allows the system to adjust gestational age based on individual ovulation patterns.
Ovulation Date: If known (e.g., via tracking or IVF), this provides the most accurate baseline for HCG progression analysis.

Data Visualization and Analysis

Once entries are saved, the application provides:

Trend Mapping: A visual chart showing the rise of HCG levels over time.
Risk Assessment: The backend compares entries against medical-grade algorithms (Analysis Results) to determine if the HCG rise is within the expected range for the calculated gestational age.

API Reference

For developers looking to programmatically manage HCG data, the following endpoints are available. All requests require an active session via the Authentication system.

1. Fetch All Entries

Retrieve a list of all HCG entries for the authenticated user.

Endpoint: GET /api/hcg-entries
Response: Array<HcgEntry>

2. Create New Entry

Add a new blood test result to the database.

Endpoint: POST /api/hcg-entries
Payload:

{
  "date": "2023-10-25",
  "hcgValue": 1500,
  "units": "mIU/mL",
  "notes": "First draw",
  "lmpDate": "2023-09-20",
  "cycleLength": 28,
  "ovulationDate": "2023-10-04"
}

3. Update an Entry

Modify an existing record by its ID.

Endpoint: PUT /api/hcg-entries/:id
Payload: Partial or full HcgEntry object.

4. Delete an Entry

Permanently remove a record.

Endpoint: DELETE /api/hcg-entries/:id

Data Schema (Type Definitions)

The following structure defines an HCG entry within the system:

[!TIP] For the most accurate AI analysis and risk assessment, ensure that at least two HCG entries are recorded 48–72 hours apart to allow the system to calculate the "doubling rate."