Praneel Panchigar
85f2c8cecc
Bugfix/bill type code fixes * Fix LOB_PROGRAM_RELATIONSHIP extraction and preserve debugging code - Add format requirements to LOB_RELATIONSHIP_INSTRUCTION for proper caching - Strengthen LOB_RELATIONSHIP prompt with explicit pipe delimiter requirements - Preserve all DEBUG blocks and print statements in dynamic_funcs.py and file_processing.py - Update crosswalk mappings and gitignore - Ensure format instructions are cached at API level to prevent missing pipe delimiters * Merge main into bugfix/dynamic_issuefixes Resolved merge conflicts in: - fieldExtraction/src/investment/dynamic_funcs.py (merged debug print statements) - fieldExtraction/src/investment/file_processing.py (merged debug statements and exhibit inheritance code) All conflicts resolved successfully. * Update FILL_BILL_TYPE prompt with place-of-service priority and optional exhibit_text - Add optional exhibit_text parameter to FILL_BILL_TYPE function - Update instructions to prioritize place-of-service over service-only terminology - Add new examples: 'home dialysis' and 'dialysis' while keeping original examples - Add conditional exhibit context section when exhibit_text is provided - Maintains backward compatibility (exhibit_text defaults to None) Ref: PLAN_BILL_TYPE_CD_IMPROVEMENTS.md * Implement two-step bill type CD determination with exhibit text fallback - Add EXHIBIT_TEXT to answer_dict in combine_one_to_n() for contextual analysis - Update fill_bill_type() to use two-step approach: 1. First attempt: service term only (no exhibit text) 2. Second attempt: service term + exhibit text (only if first fails) - Update extract_codes_from_service() to pass exhibit_text to fill_bill_type() - Add debug print when full exhibit text context is used - More efficient: only makes second LLM call when service term alone fails Ref: PLAN_BILL_TYPE_CD_IMPROVEMENTS.md * Remove debug print statement and merge main into bill_type_code_fixes - Remove debug print statement from fill_bill_type() in code_funcs.py - Merge latest changes from main branch - Includes updates to prompt_templates.py (payer_name parameter) - Includes updates to file_processing.py (provider info ordering) - Includes updates to aarete_derived.py, crosswalk mappings, and tin_npi_funcs * Remove remaining debug print statements from dynamic_funcs.py and file_processing.py Approved-by: Katon Minhas
Branching and Release Management Guide
Overview
This guide outlines the naming conventions, branching strategy, and merging process for our Git repository.
Branch Naming Conventions
- Feature Branch:
feature/<name>- Example:
feature/add_build_stage
- Example:
- Bugfix Branch:
bugfix/<name>- Example:
bugfix/pages_duplication
- Example:
- Hotfix Branch:
hotfix/<name>- Example:
hotfix/deployment_failure
- Example:
....
Branching Strategy
Creating Branches
- Create a feature branch from
mainusing the appropriate naming convention. - Create a small and complete change.
mainmust always have deployable code. - Create a Pull Request back to
main. - Ensure all checks have passed.
- Merge new code.
- Ensure the functionality is verified in the dev environment.
Refer to the branching guide in Confluence for more info on this
This guide ensures that all team members follow the best practices for branch management and releases.