jacob-mathison/doczyai-pipelines
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Activity

Merged in optimization/prov_info (pull request #829)

Browse Source 
optimization_prov_info to main

* removed on signature page field which is unnecessary


Approved-by: Katon Minhas
This commit is contained in:
VenkataKrishna Reddy Avula
2026-01-07 15:19:35 +00:00
committed by Katon Minhas
parent 874354dc44
commit d97a31aa5b
2 changed files with 0 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
fieldExtraction/src/prompts/investment_prompts.json
-6
View File
@@ -264,12 +264,6 @@
"prompt": "Extract the PROVIDER organization name(s) from the retrieved contract text.\n\nThe provider is the healthcare organization entering into the agreement (NOT the payer/insurance company like Highmark, Aetna, UnitedHealthcare, Blue Cross Blue Shield, etc.).\n\nGUIDELINES:\n1. Look for the provider name in phrases like:\n - 'This Agreement is between [PAYER] and [PROVIDER]'\n - 'Agreement between [PAYER] and [PROVIDER]'\n - 'by and between [PAYER] and [PROVIDER]'\n - '[PROVIDER] (hereinafter referred to as \"Provider\")'\n - 'Provider: [PROVIDER]'\n2. The provider name often appears in the opening paragraph or preamble of the contract.\n3. Return the EXACT provider name as it appears in the document, including legal suffixes (LLC, Inc., P.C., etc.).\n4. If the provider name includes 'd/b/a' (doing business as), return the FULL name including the d/b/a portion.\n5. If MULTIPLE provider organization names appear in the contract (e.g., multiple entities entering the agreement), return ALL of them separated by ' | '.\n - Example: 'Provider Group A, LLC | Provider Group B, P.C. | Provider Group C d/b/a City Medical'\n6. Do NOT return:\n - The payer/insurance company name\n - Individual physician names (unless that is the practice name)\n - Department names only\n - Addresses or other metadata\n7. If the provider name cannot be determined from the retrieved text, return 'N/A'.\n\nBriefly explain your reasoning. Return ONLY the provider name(s) separated by ' | ' if multiple, nothing else.",
"retrieval_question": "What is the provider organization name? Agreement between payer and provider. This agreement is made between. By and between. Hereinafter referred to as Provider. Provider name in contract preamble. Provider party to the agreement. Healthcare organization entering agreement."
},
{
"field_name": "ON_SIGNATURE_PAGE",
"relationship": "one_to_one",
"field_type": "provider_info",
"prompt": "Does the provided text contain signature elements? Signature elements include phrases like 'IN WITNESS WHEREOF', 'executed this agreement', 'undersigned', 'By:', signature lines, date fields for signing, or any indication that the document is being signed. If signature elements are present anywhere in the given text, respond 'Y'. If signature elements are missing from the text, respond 'N'. The location or position of these elements within the text does not matter - they can be at the top, middle, bottom, or in different sections. Write 'Y' or 'N'."
},
{
"field_name": "REIMB_PROV_TIN",
"relationship": "one_to_n",
fieldExtraction/tests/test_tin_npi_funcs.py
-3
View File
@@ -129,7 +129,6 @@ class TestTinNpiFuncs:
"TIN": "123456789",
"NPI": "1234567890",
"NAME": "Test Provider",
"ON_SIGNATURE_PAGE": "N",
}
]
)
@@ -268,7 +267,6 @@ class TestTinNpiFuncs:
"TIN": "123456789",
"NPI": "1234567890",
"NAME": "Test Provider",
"ON_SIGNATURE_PAGE": "N",
}
]
)
@@ -326,7 +324,6 @@ class TestTinNpiFuncs:
"TIN": "123456780", # Corrected from 12345678O
"NPI": "1234567890", # Corrected from 123456789O
"NAME": "Test Provider",
"ON_SIGNATURE_PAGE": "N",
}
]
)