Legacy Classic ASP Patient Notes – Development Specification / Request for Quote

@rajat07me

The real issue here is not just storing notes differently, it’s preventing a legacy save flow from ever being able to overwrite years of patient history again. I’d approach this by isolating the current editable note from the read-only legacy history, changing autosave to target only the active note record, and adding protection against stale AJAX saves writing over newer content. I’ve worked on older server-rendered systems where the safest result came from making a focused change inside the existing application rather than forcing a rewrite. Classic ASP, SQL-backed forms, legacy editors, and “append everything back into one field” behavior all need careful handling because one small save-path mistake can damage historical data or create hidden regressions. A small revision trail for edits to new notes would make sense here and can usually be kept lightweight. - Is the current autosave endpoint already separate from the main notes page post, or is it sharing the same save logic now? - Do users ever need to edit older new-format notes inline, or would opening one note at a time be acceptable? - Would you like the quote split into review/design first and implementation/testing second?

@webbookstudio

Hi there, We understand you're looking to redesign the Patient Notes saving process in your legacy Classic ASP application to prevent historical notes from being overwritten when a new note is entered. Our team at Webbook Studio has experience with similar projects, including complex database integrations and custom functionality development in Classic ASP, such as a learning platform website for children and a website for an electric bike company, both utilizing PHP, WordPress, and custom design. We'll deliver a redesigned Patient Notes functionality that stores new notes independently, making only the current note editable and keeping historical notes intact and read-only. Can you please clarify if there are any specific database schema or TinyMCE integration requirements we should be aware of during the redesign process? Feel free to message us to discuss the details! — Webbook Studio

@a4logic

Hello, With over 15 years of experience including legacy maintenance, I am well-versed in modernizing and refining systems, even those developed two decades ago. I have a deep understanding of both classic ASP and its supporting technologies like HTML, JavaScript, and Microsoft SQL Server. Known for my high-quality problem-solving skills, it would be my honor to resolve your application's flawed note-saving system. Regarding your approach, preserving the historical notes is paramount to me; I'll craft a comprehensive strategy that doesn't require migration or manipulation unless technically necessary. By creating new tables and store new notes independently while keeping existing ones read-only, we can maintain a clear distinction between historical records and new entries. Alongside that, I'll dedicate myself to ensuring only the current/new note is editable while retaining a continuous chronological history for users. Furthermore, I'm passionate about maintaining familiar user interfaces where possible. So, even though this is a legacy application, I promise to keep the transition as smooth as possible for your users while enhancing the overall integrity. Lastly, given your concerns about opening notes triggering unnecessary save events and multiple blank entries, I will address these issues by using inventive approaches that guarantee clean Thanks!

@ykarora26

With over 10 years of experience in legacy system maintenance, I understand the critical need to redesign the Patient Notes functionality in your Classic ASP application. My previous work on similar projects involved database optimization and data restructuring to prevent data loss incidents like the one you've experienced. Could you provide access to the current codebase and database schema for a preliminary assessment of the existing system architecture? Regards, Yogesh Kumar

@diektech

Hi — Elias here from Miami. I see you’re looking to enhance a legacy Classic ASP application. Maintaining and evolving such a system comes with unique challenges, particularly around scalability and future-proofing. What usually matters most here is ensuring the application can handle increased usage without compromising performance. A common issue in systems like this is outdated permissions and workflow complexities that can complicate updates. The tricky part is usually making sure that any new features integrate smoothly without disrupting the existing functionality. My approach would involve a thorough assessment of the current architecture, prioritizing maintainability and stability. I would recommend structuring the system to allow for modular updates, which will simplify future expansions. I’ve worked on similar legacy systems before, focusing on gradual modernization while keeping core functionalities intact. A few questions to better understand the scope: Q1 – What user roles are currently defined, and how do you envision them evolving? Q2 – Are there specific integrations with other systems that need to be prioritized? Q3 – What are your expectations for scaling the application in the next few years? Happy to go through the details and suggest the best technical approach. Looking forward to hearing from you.

@starttechno

I would start by tracing the Classic ASP/TinyMCE change and autosave path, including why opening Patient Notes creates a dated blank entry. I’ll review the relevant SQL schema and recommend a safe cutover that leaves the existing accumulated field untouched, displays it read-only, and stores future notes as indexed records by ProfileID and CreatedDate. After your approval of the review, I’ll implement the targeted change: only the current TinyMCE note is saved, viewing does not trigger a save, and autosave uses a version/modified-time check so an older overlapping request cannot overwrite newer text. You’ll receive the technical recommendation, compatibility risks, effort estimate, approved implementation, and focused testing within 4 days; no changes will be made before approval. Can the existing historical notes remain exactly as they are in the current field, with separate records beginning at cutover? Muhammad Saad

@ahsansaleemnaz

Hi, The separate-record approach is the right direction. I would leave the legacy notes untouched/read-only and introduce a PatientNotes table for all notes after cutover, indexed by ProfileID + CreatedDate. TinyMCE would edit only the current note while history is rendered separately, so a failed save can never overwrite historical content. I have 20+ years in software development with extensive ASP/ASP.NET, SQL Server and legacy application/database work. I would first audit the existing Classic ASP/TinyMCE save path, database schema and autosave JavaScript before proposing any changes. I would also add optimistic concurrency/version checking to autosave so a delayed request cannot overwrite a newer save. A lightweight revision table can preserve previous versions without introducing a full versioning system.

@nikhilgarg96

Hello Greetings, After reviewing your project description, I feel confident and excited to work on this project for you. But I have some crucial questions to clarify. Please leave a message in the chat so we can discuss this, and I can share my recent work similar to your requirements. Thanks for your time! I look forward to hearing from you soon. Best Regards.

@Nirmal2006

With over 24 year of sound experience and about a decade of experience specifically in classic ASP development and JavaScript proficiency, choosing me for your project would be the best decision. I am experienced in tackling complex legacy systems, like yours, that demand thoughtful approaches. I understand the importance of preserving historical data while simultaneously implementing necessary changes without compromising on the system's functionality. I always prefer to engage in detailed discussions with my clients before starting any project, which allows me to offer suggestions and improvements aligned with your goals. Moreover, my past clients attest to my problem-solving abilities, quick response times and timely deliveries. You can expect the same level of professionalism and commitment from me with this project. I will have to review your existing ASP code first before providing any type of recommendations or suggestions. Additionally, my goal is to translate your requirements into reliable code enhancing the usability and stability of your application. Your project aligns perfectly with my skills and I am confident we can create a new saving process for patient notes change without transmitting the entire historical record. With regular communication throughout our engagement, we will ensure a smooth delivery while exceeding your expectations. Let's turn this mitigation into a permanent solution. Let's start right now, thank you...

@sabaehsan

Greetings, You've outlined a clear need to improve the Patient Notes functionality in your legacy Classic ASP application. The goal is to redesign how patient notes are stored and managed, ensuring that new entries don’t overwrite historical data while also making the interface user-friendly. To tackle this, I suggest implementing a new table for individual notes while keeping historical notes intact and read-only. This will allow for separate saving of new entries without affecting the existing records. I can also ensure that viewing notes doesn't trigger unnecessary saves and that autosave is limited to just the current note. My experience in Classic ASP and SQL Server will help me navigate the existing code efficiently, ensuring a seamless integration without disrupting the overall application. I look forward to providing a detailed technical implementation plan once I review the existing setup. Best regards, Saba Ehsan

@WebTechDesignBG

Hello, I see you're looking to improve the Patient Notes functionality of your legacy Classic ASP application. The goal is to redesign how notes are saved, ensuring the historical notes remain intact, while allowing new notes to be stored separately. This makes sense, especially given the issues you've faced with data loss. With 7+ years of experience in Classic ASP and SQL databases, I can help implement a solution that preserves existing data and enhances performance. I'll focus on making historical notes read-only, allowing new notes to be saved independently, and ensuring the interface remains user-friendly. I can also address the autosave feature to prevent unnecessary overwrites. One question I have is about how you envision the transition for users from the current to the new notes system. Are there specific user scenarios you'd like to prioritize during the redesign? Best regards, Ivan Mandinski

@marjanahmed13

Hi! My name is Marjan and I'm here to offer you my services as a skilled applicant with over a decade of experience working on Freelancer.com. I believe I am the best fit candidate for this project due to my extensive experience; I would like to have a discussion to get to know that we both are on the same page. Once the scope will be locked, I will start working on it right away.

@AITSoft

Hi, I understand you need a focused redesign of the Patient Notes feature in your legacy Classic ASP application, without rewriting the wider system. I would first review the current ASP pages, database structure, TinyMCE setup, autosave flow, and how historical notes are displayed. Then I would recommend a safe plan using separate note records for new entries, while keeping existing history intact and read-only. The new note would save only its own content, and opening or closing notes would not create blank entries or trigger saves. I would also check concurrent autosave requests, database indexes, error handling, and a practical way to show older notes without slowing the page. After the review, I would provide the implementation plan, risks, estimated hours, and testing steps for approval before making changes. My work with Java, JavaScript, HTML, and AJAX can support the client-side note editing and autosave behavior alongside the existing Classic ASP and SQL code. Can you provide the relevant Classic ASP notes pages, database schema, and current TinyMCE/autosave code for the initial review? I can keep the change targeted, protect the existing patient history, and make the new workflow simple for users.

@sufyanasmat38

Hi, we can review and redesign the Patient Notes functionality within your existing Classic ASP/TinyMCE application without rewriting the wider system. We’ll assess the current ASP/AJAX flow and SQL structure, then recommend a safe separate-note record design with read-only historical notes, current-note autosave, proper indexing, and protection against concurrent saves or accidental overwrites. We’ll first provide the technical approach, risks, estimated hours, and testing plan for approval before making any changes.

@mxpertz

Hello** Your current issue is caused by treating the entire patient history as one editable record. I can first review the existing Classic ASP notes workflow, database structure, TinyMCE integration, and autosave logic, then propose a safe separate-record design that protects historical notes and saves only the current note. I’ll focus on a targeted change rather than rewriting the legacy application. I am experienced in maintaining and modifying existing Classic ASP applications with SQL databases, including working carefully around legacy code where backward compatibility and data safety are critical. I can also review the TinyMCE implementation and concurrent autosave behavior before recommending the final approach. Review & Scope Audit existing Notes code and database Review TinyMCE and autosave implementation Design separate patient-note records Define read-only history/current-note workflow Provide risks, hours, and implementation plan Questions Which SQL database/version is the application using? Can you provide the relevant Classic ASP notes files for review? Is the current notes field stored as SQL TEXT, NTEXT, or another type? I can start with the requested technical review and provide a clear implementation plan and fixed scope before making any production changes. Best Regards, Meera

@naminghn

Hi there, I can start by redesigning the Patient Notes functionality to operate independently of the accumulated notes. To maintain existing historical notes, I’ll ensure they are read-only and implement a separate database record structure for new notes, along with autosave features that align with your specifications. Moreover, I'll review the current Classic ASP code to refine the interface for user familiarity while ensuring that data integrity is preserved during note entries. This targeted approach will enhance performance without compromising the existing application structure. Happy to discuss further details to refine the technical approach. Regards, Ali

@hirenksanghvi

Hi, Greetings from the team at Syndell! We understand your Classic ASP patient notes system needs restructuring so new clinical entries save independently without transmitting and overwriting the entire historical record each time. The data integrity risks you've faced make this redesign urgent. We'd restructure the data layer to separate note inserts from history preservation, building on your existing ASP and SQL Server stack. Our team specializes in legacy system optimization where data loss risks demand careful, methodical work. Would the discovery phase include database schema documentation, or should we plan for that? We hold 5-star reviews on Clutch and GoodFirms and rank among the top-rated companies for our services on Freelancer.com. We are keen to connect, answer any questions you may have, and share relevant examples from our portfolio once we are engaged. Excited about the possibilities ahead. Thanks! PS: The final time and cost may be subject to change based on our discussion.

@ravichedwal

As a seasoned Full Stack Developer with expertise in PHP and more specifically, classic ASP language, I am uniquely skilled to tackle your Legacy Classic ASP Patient Notes issue. With over 8 years of experience and having successfully delivered 145+ projects, I have demonstrated my ability to deliver high-quality and scalable solutions across various technologies. In regards to your project's recommended approach, I can effectively preserve, safeguard, and ensure accessibility to your existing historical notes, without the need for major data manipulation or migration. Additionally, I'll make sure the new notes are stored independently as separate database records to avoid overwriting or truncating the existing ones.

@Web1devloper

As an experienced developer with comprehensive knowledge in crafting dynamic web solutions, I'm confident that I can successfully tackle the challenges your legacy Classic ASP application presents. Over my 8-year career, I've built a strong proficiency in languages such as HTML, CSS, JavaScript, and more which will be essential to redesigning your Patient Notes. One crucial element in this project is preserving existing historical notes, ensuring users' valuable data remains accessible. I fully understand this and will make sure not to manipulate the historical content unless absolutely necessary. My proven competence with databases like MySQL will come in handy to store new notes independently, separated from the large notes field. Most importantly, I'm not just technically proficient, but also a creative thinker. I understand the value of maintaining a familiar interface for users while addressing technical complexities like eliminating unnecessary saves and multiple blank entries. Leveraging on my knack for problem-solving and desire to simplify things, I'll ensure only the new note is editable while still offering a clear, chronological history for users with previous notes displayed as read-only. Finally, your project's objective aligns perfectly with my DNA of delivering robust and sustainable solutions. Let's join forces for an enhanced legacy Classic ASP application!