Backend

This page consolidates server-side responsibilities: report conversion, presigned generation + reconcile, uploadFileTypeReportAPI branching (new vs legacy), mark-as-done, Elasticsearch and Pusher side effects, print/render special cases, and PY-3 Storage Manager + Lambda-authenticated file-type-report helpers.

Cross-links: Overview, Workflow Guide, Design Decisions.

Backend Technicalities

livehealthapp (PY-2)

1. Report conversion

File: apps/livehealthapp/labs/API.py
Function: convertReportToFileOrNormal

Responsibilities:

• Authorize conversion (permissions + radiology guard + session shape).
• Delete existing ReportValue rows.
• Toggle fileInputReport and related flags (store_values_to_document_db reset in this path).
• Reset completion, approval, signing, partial sign, print-done fields.
• Trigger Pusher + patient report ES reindex + activity log.

2. File upload finalizer

File: apps/livehealthapp/reports/views.py
Function: uploadFileTypeReportAPI (+ save_file_type_report_to_report_value on the write path)

Responsibilities:

• Branch detection: if initialFilePath is present and path-like → presigned-aware fast path (file already in storage).
• Legacy branch: if fileData present → base64 decode path, restruct_uploaded_files, SmStore, then value write.
• Update ReportValue.value to the stored path.
• Mutate LabReportRelation completion / approval fields (e.g. completedTests, isApproved, timestamps, acting labUserId).
• commonPusherFunctionForLabReportRelation (or equivalent) for waiting-list freshness.
• Patient report Elasticsearch reindex for search surfaces.
• Upload activity log entry.

Report mutations (presigned-aware branch - conceptual)

Exact field names should be verified in the implementation block inside uploadFileTypeReportAPI when debugging a specific deployment branch.

3. Legacy preprocessing

Same file: restruct_uploaded_files in reports/views.py

Role: normalize/validate uploads in legacy mode - images, damaged PDFs, EOF quirks, internal failure codes. Historically this is the kind of work the revamp tries to move off the synchronous PY-2 request path toward async / infra-assisted processing.

4. Storage Manager (PY-2)

File: apps/livehealthapp/labs/storage_manager.py

URL wiring: apps/livehealthapp/livehealthapp/urls.py (or equivalent project urls.py in your branch) - sm_generate_presigned_url/, sm_reconcile_presigned_url/, uploadFileTypeReport/, uploadFileWithHeader/.

5. Mark-as-done support

File: apps/livehealthapp/labs/newAPI.py
Function: mark_report_as_done_api

Marks sibling operational reports complete with business rules (e.g. at least one operational report must remain incomplete in the bill), updates ES, triggers hooks/Pusher as implemented.

6. Downstream rendering

File-type reports are not “upload and forget”; print/download stacks branch on file paths vs parameter matrices.

crelio-app (PY-3)

1. Storage Manager APIs and core implementation

Capabilities include presigned POST generation, presigned download, reconcile, canonical path generation, extension gates, soft-delete / cleanup behaviors.

2. Canonical path generation (documented shape)

<DeploymentZone>/<LabId>/<PatientId>/<FileCategory>/<cloudDocId>_<filename>.<extension>

Example:

IN/123/456456/FileTypeReport/16915654908422848526992_foo.jpeg

Both PY-2 and PY-3 utilities support caller-supplied cloud_path patterns; the temp vs concrete distinction matters when Lambda rewrites paths.

3. File-type-report Lambda-facing APIs

File: apps/crelio-app/report/views/file_type_report_lambda.py
Routes: see apps/crelio-app/report/urls.py

FetchFileTypeReportPath (conceptual): looks up SM log for temp path, pulls file metadata, resolves S3 account details, emits canonical path. Important implementation detail from source analysis: extension normalization may force .pdf in the helper path - treat this as a normalization contract when reasoning about mixed image/PDF inputs on Lambda-shaped flows.

UpdateReportValueWithFilePath (conceptual): accepts filePath, temporary_filepath, labReportId; updates report_results.value, timestamps, completion flags; aligns SM log from temporary to final path.

4. Lambda authentication

File: apps/crelio-app/core/utils/aws/authenticate_lambda_requests.py

• Expects header X-Lambda-Token
• Validates against settings.CRON_SIGNING_KEY (naming may vary by environment - confirm in deployment secrets)

5. File type reports beyond manual UI upload

Example: apps/crelio-app/interfacing/models/device.py - instrument/device flows can persist file_category="FileTypeReport" style outputs.

Format linkage: apps/crelio-app/report/views/report_format_link.py - format type 4 correlates with fileInput=1 semantics in that module’s conventions.

DB and architecture

Relational state, object storage, Storage Manager logs, and Elasticsearch documents together implement the feature; PY-2 remains the observed domain finalizer for the default frontend path.

Core entities

What gets persisted where

File path semantics

Setup dependencies by layer

Architectural caveats (backend-focused)

1. Observed FE still finalizes in PY-2 - presigned + reconcile can be PY-2 while PY-3 exposes parallel helpers.
2. Lambda source not in repo snapshot - only contracts + auth + endpoints are verifiable here.
3. Header/footer remains uploadFileWithHeader / base64 transport on PY-2.
4. Temporary path may be what PY-2 stores in the observed path until/unless a later job rewrites - contrast with PY-3 “temp → canonical” helper intent.

For rationale and decision framing, see Design Decisions.