medicafe 0.240419.2__zip

medicafe-0.240419.2/MediLink/MediLink_Scheduler.py

@@ -0,0 +1,132 @@
+"""
+MediLink Scheduler: A medical claim scheduling and management system that integrates functionalities from MediScheduler and MediLink to optimize medical claim submissions based on patient deductible status, insurance provider deadlines, and a 90-day submission window. It leverages real-time data from insurance APIs for dynamic scheduling to maximize insurance payments by aligning claim submission with deductible fulfillment.
+
+Features:
+- Deductible Optimization: Determines optimal submission times based on deductible fulfillment to maximize reimbursements.
+- Dynamic Scheduling: Updates claim submission timelines in response to changes in deductible status and insurance coverage data.
+- Secure Data Handling: Ensures the security of sensitive patient data through encryption and HIPAA-compliant practices.
+- Integration with MediLink Systems: Seamlessly formats, submits, and tracks claims across MediLink and associated systems.
+- Robust Error Handling and Notifications: Implements mechanisms for error detection and user alerts regarding scheduling and submission errors.
+
+Main Functionalities:
+1. Configuration and System Initialization:
+   - Configures and establishes secure connections to insurance APIs.
+   - Loads encrypted system settings and initializes subsystems for logging, data encryption, and notifications.
+
+2. Scheduler Integration:
+   - Enhances MediLink's main menu to include an option for "Optimize and Schedule Submissions".
+   - This option is visible only when there are new or imminent claims, activating the scheduling function for these claims.
+
+3. Scheduling Process:
+   - Identifies new or urgent claims.
+   - Fetches real-time deductible information from insurance APIs.
+   - Computes remaining deductible and determines suitable submission dates.
+   - Schedules claims with consideration for deductible status and the 90-day deadline, updating a scheduling log with details.
+
+4. User Dashboard Update:
+   - Displays scheduled submissions, including deductible statuses and scheduled dates.
+   - Allows users to manually adjust or override automated scheduling decisions.
+
+5. Pre-Submission Checks:
+   - Daily verification of claims ready for submission.
+   - Prepares 837P claim files and finalizes submission details with user confirmation.
+   - Securely transmits data to insurance providers and logs all submission activities.
+
+6. Direct Submission Handling:
+   - Uses MediLink_Up.submit_claims to manage final claim submissions.
+   - Ensures that all scheduled claims are submitted with requisite details.
+
+7. Data Security:
+   - Applies encryption to any new data storage or sensitive data involved in the scheduling process.
+   - Maintains compliance with HIPAA and relevant security standards.
+
+8. Error Management and Alerts:
+   - Extends error handling capabilities to include specific scheduling and submission issues.
+   - Enhances notifications for reminders and updates on deductible status.
+
+9. Integration with MediLink Logging and Error Handling:
+   - Integrates scheduler operations into MediLink’s existing logging and error management frameworks.
+
+10. Maintenance and Data Cleanup:
+    - Regularly refreshes insurance data mappings and updates deductible information.
+    - Manages cleanup of processed claims to maintain database integrity and performance.
+
+11. User Interface Improvements:
+    - Updates UI to ensure user-friendliness and provides clear operational feedback.
+    - Revises help documentation to reflect new functionalities and guides for scheduling tasks.
+
+Database Management:
+- Maintains a JSON-based database for patient billing data, labeled as patient_billing_db, storing information from various sources (Z.dat file, APIs, SFTP).
+- Database content includes claim statuses, deductible details, error logs, and identifiers for billing readiness.
+- Facilitates efficient tracking and processing of claims, with considerations for integrating individual patient data in batched submissions.
+- Stays on the local machine in a defined secure location per config, ensuring HIPAA compliance without the need for data encryption at rest.
+
+Note: Potential for data corruption or synchronization issues due to system limitations; backup and manual verification measures are advised.
+"""
+
+
+# JSON DB structure draft.
+{
+  "patients": {
+    "patient_id": {
+      "first_name": "John",
+      "last_name": "Doe",
+      "date_of_birth": "1985-07-12",
+      "insurance_details": {
+        "provider_id": "XYZ123",
+        "policy_number": "P123456789",
+        "coverage_start_date": "2020-01-01"
+      },
+      "contact_info": {
+        "email": "john.doe@example.com",
+        "phone": "555-1234"
+      }
+    }
+  },
+  "claims": {
+    "claim_id": {
+      "patient_id": "patient_id",
+      "date_of_service": "2023-04-01",
+      "status": "pending",
+      "scheduled_submission_date": "2023-04-15",
+      "actual_submission_date": null,
+      "billing_amount": 500.00,
+      "deductible_applied": 100.00,
+      "covered_amount": 400.00
+    }
+  },
+  "insurance_providers": {
+    "provider_id": {
+      "name": "InsuranceCorp",
+      "contact_details": {
+        "phone": "555-6789",
+        "email": "support@insurancecorp.com"
+      },
+      "endpoint": "https://api.insurancecorp.com"
+    }
+  },
+  "system_configuration": {
+    "last_update": "2023-04-18",
+    "backup_frequency": "daily",
+    "data_encryption_key": "encrypted_key_value"
+  },
+  "logs": {
+    "log_id": {
+      "timestamp": "2023-04-18T12:34:56",
+      "event_type": "error",
+      "description": "Failed to connect to insurance API",
+      "related_claim_id": "claim_id"
+    }
+  },
+   "billing_queue": {
+   "patient_id": "claim_id"
+    },
+   "submitted_837p_batches": {
+   "batch_id": {
+      "timestamp": "2023-04-20T09:00:00",
+      "patients": ["patient_id1", "patient_id2", ...],
+      "endpoint": "clearinghouse_endpoint",
+      "status": "submitted"
+   }
+  }
+}

medicafe-0.240419.2/MediLink/MediLink_StatusCheck.py

@@ -0,0 +1,4 @@
+"""
+Checks and updates the status of submitted medical claims using API endpoints.
+Integrates with MediLink_Down and MediPost to retrieve and process ERAs and other relevant response data from insurance providers.
+"""

medicafe-0.240419.2/MediLink/MediLink_UI.py

@@ -0,0 +1,116 @@
+import datetime
+import sys
+
+"""
+Development Tasks for User Interface (UI) Enhancement in MediSoft Claims Submittal (MediLink) Script:
+
+Streamline user interaction for endpoint selection and patient adjustments with automated endpoint validation.
+Strengthen error handling in file conversion, transmission, and user inputs with actionable user feedback.
+Expand logging levels and develop a user notification system for process milestones and errors.
+Focus workflow on patient details for endpoint adjustments, facilitating patient-centric file submissions.
+Implement internet connectivity checks with retry options for submissions and offer pause/resume capabilities.
+Include final review and confirmation steps before submission, allowing for endpoint adjustments per patient.
+"""
+
+def display_welcome():
+    print("\n" + "-" * 60)
+    print("\n          *~^~*:    Welcome to MediLink!    :*~^~*\n")
+    print("-" * 60 + "\n")
+
+def display_menu(options):
+    print("Menu Options:")
+    for i, option in enumerate(options):
+        print("{0}. {1}".format(i+1, option))
+
+def get_user_choice():
+    return input("Enter your choice: ").strip()
+
+def display_exit_message():
+    print("\nExiting MediLink.")
+
+def display_invalid_choice():
+    print("Invalid choice. Please select a valid option.")
+
+def display_patient_options(detailed_patient_data):
+    """
+    Displays a list of patients with their current suggested endpoints, prompting for selections to adjust.
+    """
+    print("\nPlease select the patients you want to adjust by entering their numbers separated by commas (e.g., 1,3,5):")
+    # Can disable this extra print for now because the px list would already be on-screen.
+    #for i, data in enumerate(detailed_patient_data, start=1):
+    #    patient_info = "{0} ({1}) - {2}".format(data['patient_name'], data['patient_id'], data['surgery_date'])
+    #    endpoint = data.get('suggested_endpoint', 'N/A')
+    #    print("{:<3}. {:<30} Current Endpoint: {}".format(i, patient_info, endpoint))
+
+def get_selected_indices(patient_count):
+    """
+    Collects user input for selected indices to adjust endpoints.
+    """
+    selected_indices_input = input("> ")
+    selected_indices = [int(index.strip()) - 1 for index in selected_indices_input.split(',') if index.strip().isdigit() and 0 <= int(index.strip()) - 1 < patient_count]
+    return selected_indices
+
+def display_patient_for_adjustment(patient_name, suggested_endpoint):
+    """
+    Displays the current endpoint for a selected patient and prompts for a change.
+    """
+    print("\n- {0} | Current Endpoint: {1}".format(patient_name, suggested_endpoint))
+
+def get_endpoint_decision():
+    """
+    Asks the user if they want to change the endpoint.
+    """
+    return input("Change endpoint? (Y/N): ").strip().lower()
+
+def display_endpoint_options(endpoint_mapping):
+    """
+    Displays the endpoint options to the user based on the provided mapping.
+
+    Args:
+        endpoint_mapping (dict): A dictionary mapping option numbers to endpoint names.
+                                  Example: {'1': 'Availity', '2': 'OptumEDI', ...}
+
+    Returns:
+        None
+    """
+    print("Select the new endpoint for the patient:")
+    for option, endpoint_name in endpoint_mapping.items():
+        print("{0}. {1}".format(option, endpoint_name))
+
+def get_new_endpoint_choice():
+    """
+    Gets the user's choice for a new endpoint.
+    """
+    return input("Select new endpoint (1, 2, or 3): ").strip()
+
+def display_patient_summaries(detailed_patient_data):
+    """
+    Displays summaries of all patients and their suggested endpoints.
+    """
+    print("\nSummary of patient details and suggested endpoint:")
+    for index, summary in enumerate(detailed_patient_data, start=1):
+        try:
+            display_file_summary(index, summary)
+        except KeyError as e:
+            print("Summary at index {} is missing key: {}".format(index, e))
+
+def ask_for_proceeding_with_endpoints():
+    """
+    Asks the user if they want to proceed with all suggested endpoints.
+    """
+    proceed = input("\nDo you want to proceed with all suggested endpoints? (Y/N): ").strip().lower()
+    return proceed == 'y'
+
+def display_file_summary(index, summary):
+    # Ensure surgery_date is converted to a datetime object
+    surgery_date = datetime.datetime.strptime(summary['surgery_date'], "%m-%d-%y")
+
+    # Displays the summary of a file.
+    print("{:02d}. {:5} (ID: {:<8}) {:20} {:15} Suggested Endpoint: {}".format(
+        index,
+        surgery_date.strftime("%m-%d"),
+        summary['patient_id'],
+        summary['patient_name'][:20],
+        summary['primary_insurance'][:15],
+        summary['suggested_endpoint'])
+    )

medicafe-0.240419.2/MediLink/MediLink_Up.py

@@ -0,0 +1,117 @@
+import os
+import subprocess
+import logging
+import MediLink_837p_encoder
+from MediLink_837p_encoder_library import log
+from tqdm import tqdm
+from MediLink_DataMgmt import operate_winscp
+
+"""
+Handles the transmission of files to endpoints and related tasks for the MediLink script.
+
+Functions:
+- check_internet_connection(): Checks for an active internet connection.
+- UPDATE THIS: transmit_files_to_endpoint(converted_files, endpoint_config, local_storage_path): Transmits files to a specified endpoint using WinSCP.
+- handle_transmission_result(transmission_result): Handles the result of the file transmission process.
+- submit_claims(detailed_patient_data_grouped_by_endpoint, config): Submits claims to respective endpoints based on patient data and configuration.
+- confirm_transmission(detailed_patient_data_grouped_by_endpoint): Displays patient data ready for transmission and asks for confirmation.
+
+This module provides functionality for transmitting files, confirming transmissions, and ensuring connectivity for the MediLink script.
+"""
+
+# Internet Connectivity Check
+def check_internet_connection():
+    """
+    Checks if there is an active internet connection.
+    Returns: Boolean indicating internet connectivity status.
+    """
+    try:
+        # Run a ping command to a reliable external server (e.g., Google's DNS server)
+        ping_process = subprocess.Popen(["ping", "-n", "1", "8.8.8.8"], stdout=subprocess.PIPE, stderr=subprocess.PIPE)
+        ping_output, ping_error = ping_process.communicate()
+
+        # Check if the ping was successful
+        if "Reply from" in ping_output.decode("utf-8"):
+            return True
+        else:
+            return False
+    except Exception as e:
+        print("An error occurred while checking internet connectivity:", e)
+        return False
+        
+def handle_transmission_result(transmission_result):
+    """
+    Handles the result of the file transmission process. Logs the outcome and provides user feedback.
+
+    :param transmission_result: The result of the file transmission process.
+    """
+    #if transmission_result:
+        #logging.info("Transmission successful")
+        # TODO This needs to do an actual check in the WinSCP log to make sure this is actually true.
+        #print("Files have been successfully transmitted.")
+    #else:
+        #logging.error("Transmission failed")
+        # TODO This needs to do a pull from the WinSCP log to show the user what happened.
+        #print("There was an issue with the file transmission.")
+
+def submit_claims(detailed_patient_data_grouped_by_endpoint, config):
+    if not detailed_patient_data_grouped_by_endpoint:
+        print("No new files detected for submission.")
+        return
+
+    # Wrap the iteration with tqdm for a progress bar
+    for endpoint, patients_data in tqdm(detailed_patient_data_grouped_by_endpoint.items(), desc="Progress", unit="endpoint"):
+        if not patients_data:  # Skip if no patient data for the endpoint
+            continue
+
+        # Confirm transmission to each endpoint with detailed overview
+        if True: #confirm_transmission({endpoint: patients_data}):
+            if check_internet_connection():
+                # Process and transmit files per endpoint
+                converted_files = MediLink_837p_encoder.convert_files_for_submission(patients_data, config)
+                if converted_files:  # Check if files were successfully converted
+                    # BUG DISABLE TRANSMISSION FOR TESTING
+                    # transmission_result = operate_winscp("upload", converted_files, config['MediLink_Config']['endpoints'][endpoint], config['MediLink_Config']['local_claims_path'])
+                    print("Would have uploaded here!") # DEBUG
+                    
+                    # handle_transmission_result(transmission_result)
+                    # This doesn't really do much
+                    # BUG This has to fail better. If one endpoint is unreachable, it should still try the next endpoint.
+                    # BUG handle_transmission_result is wrong.
+                else:
+                    print("No files were converted for transmission to {0}.".format(endpoint))
+            else:
+                print("No internet connection detected.")
+                try_again = input("Do you want to try again? (Y/N): ").strip().lower()
+                if try_again != 'y':
+                    print("Exiting transmission process. Please try again later.")
+                    return  # Exiting the function if the user decides not to retry
+        else:
+            print("Transmission canceled for endpoint {0}.".format(endpoint))
+
+    print("Claim submission completed.\n")
+
+# Secure File Transmission
+def confirm_transmission(detailed_patient_data_grouped_by_endpoint):
+    """
+    Displays detailed patient data ready for transmission and their endpoints, 
+    asking for user confirmation before proceeding.
+
+    :param detailed_patient_data_grouped_by_endpoint: Dictionary with endpoints as keys and 
+            lists of detailed patient data as values.
+    :param config: Configuration settings loaded from a JSON file.
+    """ 
+    print("\nReview of patient data ready for transmission:")
+    for endpoint, patient_data_list in detailed_patient_data_grouped_by_endpoint.items():
+        print("\nEndpoint: {0}".format(endpoint))
+        for patient_data in patient_data_list:
+            patient_info = "({1}) {0}".format(patient_data['patient_name'], patient_data['patient_id'])
+            print("- {:<35} | {:<5}, ${:<6}, Primary: {}".format(
+                patient_info, patient_data['surgery_date'][:5], patient_data['amount'], patient_data['primary_insurance']))
+    
+    confirmation = input("\nProceed with transmission to all endpoints? (Y/N): ").strip().lower()
+    return confirmation == 'y'
+
+# Entry point if this script is run directly. Probably needs to be handled better.
+if __name__ == "__main__":
+    print("Please run MediLink directly.")

medicafe-0.240419.2/MediLink/MediLink_batch.bat

@@ -0,0 +1,7 @@
+@echo off
+
+:: Execute the Python script
+py F:\TEST-MEDIBOT\MediLink.py
+
+:end_script
+pause

medicafe-0.240419.2/MediLink/Soumit_api.py

@@ -0,0 +1,22 @@
+import os
+import requests
+from icecream import ic
+from dotenv import load_dotenv
+
+load_dotenv()
+
+url = "https://api.availity.com/availity/development-partner/v1/token"
+
+data = {
+    'grant_type': 'client_credentials',
+    'client_id': os.getenv("CLIENT_ID"),
+    'client_secret': os.getenv("CLIENT_SECRET"),
+    'scope': 'hipaa'
+}
+
+headers = {
+    'Content-Type': 'application/x-www-form-urlencoded'
+}
+
+resp = requests.post(url, headers = headers, data = data)
+ic(resp.json())

medicafe-0.240419.2/PKG-INFO

@@ -0,0 +1,11 @@
+Metadata-Version: 1.0
+Name: medicafe
+Version: 0.240419.2
+Summary: MediCafe
+Home-page: https://github.com/katanada2
+Author: Daniel Vidaud
+Author-email: daniel@personalizedtransformation.com
+License: MIT
+Description: This module ensures that MediCafe remains up-to-date by performing version checks for its dependencies on startup. It utilizes PyPI, the official repository for Python packages, to retrieve information about the latest available versions of the required packages. When an internet connection is available, MediUpdate automatically installs any available updates using pip, the package installer for Python.
+Keywords: medicafe python34 medibot medilink
+Platform: UNKNOWN

medicafe-0.240419.2/README.md

@@ -0,0 +1,28 @@
+## MediLink and MediBot Utilities
+
+This repository contains utility functions and wrappers for MediLink and MediBot systems as part of MediCafe.
+
+### Developer Info:
+- Name: Daniel Vidaud
+- GitHub: [\[Your GitHub Profile\]](https://github.com/katanada2)
+- Email: daniel@personalizedtransformations.com
+- LinkedIn: [\[Your LinkedIn Profile\]](https://www.linkedin.com/in/dvidaud/)
+
+### Features:
+- **medi_link.py**: Contains functions for interacting with the MediLink system.
+- **medi_bot.py**: Provides utilities for managing interactions with the MediBot system.
+
+### Missing Features:
+- [ ] Comprehensive test automation and GitHub workflow setup.
+
+### Known Bugs:
+- The MediBot system may have limitations.
+
+### Usage Documentation:
+No usage documentation.
+
+### Contribution Guideline:
+Contributions to the codebase are not welcome for now except by one other person.
+
+### Disclaimer:
+This repository is maintained independently and is not affiliated with anyone.

medicafe-0.240419.2/medicafe.egg-info/PKG-INFO

@@ -0,0 +1,11 @@
+Metadata-Version: 1.0
+Name: medicafe
+Version: 0.240419.2
+Summary: MediCafe
+Home-page: https://github.com/katanada2
+Author: Daniel Vidaud
+Author-email: daniel@personalizedtransformation.com
+License: MIT
+Description: This module ensures that MediCafe remains up-to-date by performing version checks for its dependencies on startup. It utilizes PyPI, the official repository for Python packages, to retrieve information about the latest available versions of the required packages. When an internet connection is available, MediUpdate automatically installs any available updates using pip, the package installer for Python.
+Keywords: medicafe python34 medibot medilink
+Platform: UNKNOWN

medicafe-0.240419.2/medicafe.egg-info/SOURCES.txt

@@ -0,0 +1,37 @@
+LICENSE
+MANIFEST.in
+README.md
+setup.py
+MediBot/MediBot.bat
+MediBot/MediBot.py
+MediBot/MediBot_Charges.py
+MediBot/MediBot_Preprocessor.py
+MediBot/MediBot_UI.py
+MediBot/MediBot_dataformat_library.py
+MediBot/MediPost.py
+MediBot/PDF_to_CSV_Cleaner.py
+MediBot/__init__.py
+MediBot/update_json.py
+MediBot/update_medicafe.py
+MediLink/MediLink.py
+MediLink/MediLink_277_decoder.py
+MediLink/MediLink_837p_encoder.py
+MediLink/MediLink_837p_encoder_library.py
+MediLink/MediLink_ConfigLoader.py
+MediLink/MediLink_DataMgmt.py
+MediLink/MediLink_Down.py
+MediLink/MediLink_ERA_decoder.py
+MediLink/MediLink_Gmail.py
+MediLink/MediLink_Scheduler.py
+MediLink/MediLink_StatusCheck.py
+MediLink/MediLink_UI.py
+MediLink/MediLink_Up.py
+MediLink/MediLink_batch.bat
+MediLink/Soumit_api.py
+MediLink/__init__.py
+medicafe.egg-info/PKG-INFO
+medicafe.egg-info/SOURCES.txt
+medicafe.egg-info/dependency_links.txt
+medicafe.egg-info/not-zip-safe
+medicafe.egg-info/requires.txt
+medicafe.egg-info/top_level.txt

medicafe-0.240419.2/medicafe.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

medicafe-0.240419.2/medicafe.egg-info/not-zip-safe

@@ -0,0 +1 @@
+

medicafe-0.240419.2/medicafe.egg-info/requires.txt

@@ -0,0 +1,5 @@
+requests
+argparse
+numpy==1.11.3
+pandas==0.20.0
+tqdm==4.14.0

medicafe-0.240419.2/medicafe.egg-info/top_level.txt

@@ -0,0 +1,2 @@
+MediBot
+MediLink

medicafe-0.240419.2/setup.cfg

@@ -0,0 +1,5 @@
+[egg_info]
+tag_svn_revision = 0
+tag_date = 0
+tag_build = 
+

medicafe-0.240419.2/setup.py

@@ -0,0 +1,28 @@
+from setuptools import setup, find_packages
+
+setup(
+    name='medicafe',
+    version='0.240419.2',
+    description='MediCafe',
+    long_description='This module ensures that MediCafe remains up-to-date by performing version checks for its dependencies on startup. It utilizes PyPI, the official repository for Python packages, to retrieve information about the latest available versions of the required packages. When an internet connection is available, MediUpdate automatically installs any available updates using pip, the package installer for Python.',
+    long_description_content_type='text/markdown',
+    keywords = 'medicafe python34 medibot medilink',
+    url='https://github.com/katanada2',
+    author='Daniel Vidaud',
+    author_email='daniel@personalizedtransformation.com',
+    license='MIT',
+    packages=find_packages(),
+    include_package_data=True,
+    package_data={
+        'MediBot': ['MediBot.bat'],
+        'MediLink': ['MediLink_batch.bat']
+    },
+    install_requires=[
+        'requests',
+        'argparse',
+        'numpy==1.11.3',
+        'pandas==0.20.0',
+        'tqdm==4.14.0'
+    ],
+    zip_safe=False
+)