[{"data":1,"prerenderedAt":3038},["ShallowReactive",2],{"article_list_modernization_":3},[4,1614],{"_path":5,"_dir":6,"_draft":7,"_partial":7,"_locale":8,"title":9,"description":10,"publishDate":6,"image":11,"author":12,"tags":15,"excerpt":10,"body":23,"_type":1608,"_id":1609,"_source":1610,"_file":1611,"_stem":1612,"_extension":1613},"/cperez/2026-07-21/building-digital-health-platforms-beyond-samd","2026-07-21",false,"","Beyond SaMD: Building a Digital Health Platform That Can Evolve","A medical application can work exactly as designed and still fall short of what the organization needs next.","/cperez/2026-07-21/img/building-digital-health-platforms-beyond-samd.jpg",{"name":13,"user":14},"Carlos Perez","cperez",[16,17,18,19,20,21,22],"samd","legacy","modernization","biomedical","healthcare","xamarin",".net maui",{"type":24,"children":25,"toc":1574},"root",[26,33,38,43,48,53,58,63,70,75,80,85,91,126,132,148,153,158,211,216,221,232,237,242,247,252,257,262,267,272,277,283,288,300,305,310,315,320,325,330,335,344,349,357,362,367,372,378,383,388,393,426,431,436,441,446,451,462,475,480,485,490,495,501,506,511,516,559,572,584,589,594,599,605,610,615,620,625,630,635,640,645,650,655,660,665,670,675,713,718,723,729,734,747,752,757,762,767,772,777,825,830,838,842,850,862,867,872,878,883,888,893,898,903,908,913,918,923,928,939,944,949,954,960,965,970,975,980,1018,1023,1028,1040,1045,1050,1055,1060,1065,1070,1075,1086,1091,1102,1107,1112,1118,1123,1128,1166,1171,1176,1181,1186,1191,1196,1207,1219,1224,1229,1235,1240,1247,1275,1281,1304,1310,1333,1339,1362,1368,1391,1397,1425,1430,1435,1441,1446,1451,1456,1461,1472,1477,1482,1488,1494,1499,1504,1509,1515,1520,1526,1531,1537,1542,1548,1553,1558,1563,1569],{"type":27,"tag":28,"props":29,"children":30},"element","p",{},[31],{"type":32,"value":10},"text",{"type":27,"tag":28,"props":34,"children":35},{},[36],{"type":32,"value":37},"It may deliver a diagnostic result, guide a clinician through a decision, help a patient manage a condition, or connect to a medical device.",{"type":27,"tag":28,"props":39,"children":40},{},[41],{"type":32,"value":42},"But then the questions get bigger.",{"type":27,"tag":28,"props":44,"children":45},{},[46],{"type":32,"value":47},"How does its data reach the rest of the care team?",{"type":27,"tag":28,"props":49,"children":50},{},[51],{"type":32,"value":52},"Can the software support a new clinical workflow without creating a new compliance problem?",{"type":27,"tag":28,"props":54,"children":55},{},[56],{"type":32,"value":57},"What happens when a framework, operating system, integration, or security requirement changes?",{"type":27,"tag":28,"props":59,"children":60},{},[61],{"type":32,"value":62},"And can the product evolve without forcing the organization to rebuild it every few years?",{"type":27,"tag":64,"props":65,"children":67},"h3",{"id":66},"what-does-it-take-to-build-a-modern-digital-health-platform",[68],{"type":32,"value":69},"What does it take to build a modern digital health platform?",{"type":27,"tag":28,"props":71,"children":72},{},[73],{"type":32,"value":74},"A modern digital health platform needs more than a functioning Software as a Medical Device application. It must connect regulated clinical functionality with patient and clinician experiences, healthcare data, security controls, interoperability, validation, and a plan for ongoing change.",{"type":27,"tag":28,"props":76,"children":77},{},[78],{"type":32,"value":79},"That means SaMD development, compliance, cybersecurity, UX, integrations, and software modernization cannot be treated as separate projects.",{"type":27,"tag":28,"props":81,"children":82},{},[83],{"type":32,"value":84},"They are parts of the same product strategy.",{"type":27,"tag":64,"props":86,"children":88},{"id":87},"key-takeaways",[89],{"type":32,"value":90},"Key takeaways",{"type":27,"tag":92,"props":93,"children":94},"ul",{},[95,101,106,111,116,121],{"type":27,"tag":96,"props":97,"children":98},"li",{},[99],{"type":32,"value":100},"SaMD may be the clinical core of a product, but it often operates inside a larger digital health platform.",{"type":27,"tag":96,"props":102,"children":103},{},[104],{"type":32,"value":105},"Intended use should shape product boundaries, risk analysis, architecture, validation, and regulatory planning from the beginning.",{"type":27,"tag":96,"props":107,"children":108},{},[109],{"type":32,"value":110},"Compliance is usually faster when traceability and validation are built into development rather than reconstructed afterward.",{"type":27,"tag":96,"props":112,"children":113},{},[114],{"type":32,"value":115},"Fast Heathcare Interoperability Resources (FHIR) and other interoperability standards help systems exchange data, but they do not guarantee that the information will be complete, understandable, or clinically useful.",{"type":27,"tag":96,"props":117,"children":118},{},[119],{"type":32,"value":120},"AI can accelerate bounded development and modernization tasks, but experienced people still need to define correct behavior and validate the result.",{"type":27,"tag":96,"props":122,"children":123},{},[124],{"type":32,"value":125},"Existing medical software does not always need a complete rewrite. A phased modernization may preserve critical functionality while reducing technical and operational risk.",{"type":27,"tag":64,"props":127,"children":129},{"id":128},"what-is-the-difference-between-samd-and-a-digital-health-platform",[130],{"type":32,"value":131},"What is the difference between SaMD and a digital health platform?",{"type":27,"tag":28,"props":133,"children":134},{},[135,137,146],{"type":32,"value":136},"Software as a Medical Device, or SaMD, is software that performs a medical function independently of a traditional physical medical device. Examples may include software used for diagnosis, monitoring, treatment recommendations, or patient support. (",{"type":27,"tag":138,"props":139,"children":143},"a",{"href":140,"rel":141},"https://artandlogic.com/newsletters/from-samd-to-digital-health-platforms-the-next-frontier-in-care/",[142],"nofollow",[144],{"type":32,"value":145},"Art+Logic",{"type":32,"value":147},")",{"type":27,"tag":28,"props":149,"children":150},{},[151],{"type":32,"value":152},"A digital health platform is the broader system around that function.",{"type":27,"tag":28,"props":154,"children":155},{},[156],{"type":32,"value":157},"It may include:",{"type":27,"tag":92,"props":159,"children":160},{},[161,166,171,176,181,186,191,196,201,206],{"type":27,"tag":96,"props":162,"children":163},{},[164],{"type":32,"value":165},"A patient-facing mobile application",{"type":27,"tag":96,"props":167,"children":168},{},[169],{"type":32,"value":170},"A clinician dashboard",{"type":27,"tag":96,"props":172,"children":173},{},[174],{"type":32,"value":175},"A regulated diagnostic or therapeutic function",{"type":27,"tag":96,"props":177,"children":178},{},[179],{"type":32,"value":180},"Connected-device integrations",{"type":27,"tag":96,"props":182,"children":183},{},[184],{"type":32,"value":185},"Healthcare data exchange",{"type":27,"tag":96,"props":187,"children":188},{},[189],{"type":32,"value":190},"Identity and access management",{"type":27,"tag":96,"props":192,"children":193},{},[194],{"type":32,"value":195},"Analytics and reporting",{"type":27,"tag":96,"props":197,"children":198},{},[199],{"type":32,"value":200},"Notifications and engagement tools",{"type":27,"tag":96,"props":202,"children":203},{},[204],{"type":32,"value":205},"Licensing and account administration",{"type":27,"tag":96,"props":207,"children":208},{},[209],{"type":32,"value":210},"Cloud infrastructure and operational systems",{"type":27,"tag":28,"props":212,"children":213},{},[214],{"type":32,"value":215},"SaMD describes the medical function and its regulatory significance.",{"type":27,"tag":28,"props":217,"children":218},{},[219],{"type":32,"value":220},"The platform describes how that function connects to the rest of the product, the organization, and the care environment.",{"type":27,"tag":28,"props":222,"children":223},{},[224,226,231],{"type":32,"value":225},"That distinction is becoming more important as healthcare software moves beyond standalone tools. Digital health platforms increasingly aggregate information from multiple sources, coordinate care across users, support longitudinal insights, and connect clinician workflows with patient applications and backend analytics. (",{"type":27,"tag":138,"props":227,"children":229},{"href":140,"rel":228},[142],[230],{"type":32,"value":145},{"type":32,"value":147},{"type":27,"tag":28,"props":233,"children":234},{},[235],{"type":32,"value":236},"Each connection creates value.",{"type":27,"tag":28,"props":238,"children":239},{},[240],{"type":32,"value":241},"It also creates responsibility.",{"type":27,"tag":28,"props":243,"children":244},{},[245],{"type":32,"value":246},"A new integration may eliminate duplicate data entry.",{"type":27,"tag":28,"props":248,"children":249},{},[250],{"type":32,"value":251},"It may also create another security boundary.",{"type":27,"tag":28,"props":253,"children":254},{},[255],{"type":32,"value":256},"A patient application may make care easier to access.",{"type":27,"tag":28,"props":258,"children":259},{},[260],{"type":32,"value":261},"It may also introduce questions about identity, consent, accessibility, connectivity, and data ownership.",{"type":27,"tag":28,"props":263,"children":264},{},[265],{"type":32,"value":266},"An analytics feature may help clinicians identify a meaningful pattern.",{"type":27,"tag":28,"props":268,"children":269},{},[270],{"type":32,"value":271},"It may also change how the product influences a clinical decision.",{"type":27,"tag":28,"props":273,"children":274},{},[275],{"type":32,"value":276},"The hard part isn’t adding more features, it’s understanding how those features change the behavior and risk of the whole system.",{"type":27,"tag":64,"props":278,"children":280},{"id":279},"why-should-intended-use-come-before-architecture",[281],{"type":32,"value":282},"Why should intended use come before architecture?",{"type":27,"tag":28,"props":284,"children":285},{},[286],{"type":32,"value":287},"Intended use defines what the software is supposed to do, who it is designed for, and how its output will affect care.",{"type":27,"tag":28,"props":289,"children":290},{},[291,293,299],{"type":32,"value":292},"Those answers influence risk classification, regulatory strategy, product requirements, architecture, testing, validation, and the evidence needed to support performance claims. Art+Logic’s SaMD guidance recommends defining intended use early rather than treating compliance as something to address after development. (",{"type":27,"tag":138,"props":294,"children":297},{"href":295,"rel":296},"https://artandlogic.com/newsletters/how-to-build-secure-compliant-samd-software-without-slowing-down-innovation/",[142],[298],{"type":32,"value":145},{"type":32,"value":147},{"type":27,"tag":28,"props":301,"children":302},{},[303],{"type":32,"value":304},"This sounds straightforward.",{"type":27,"tag":28,"props":306,"children":307},{},[308],{"type":32,"value":309},"It often isn’t.",{"type":27,"tag":28,"props":311,"children":312},{},[313],{"type":32,"value":314},"Suppose a feature displays information that a clinician will consider. Does it simply organize existing data, or does it recommend a course of treatment?",{"type":27,"tag":28,"props":316,"children":317},{},[318],{"type":32,"value":319},"Does an algorithm help prioritize cases, or does it determine which patients receive an intervention?",{"type":27,"tag":28,"props":321,"children":322},{},[323],{"type":32,"value":324},"Is a reminder a general engagement feature, or is it part of a therapeutic protocol?",{"type":27,"tag":28,"props":326,"children":327},{},[328],{"type":32,"value":329},"The answers can affect what belongs inside the regulated product boundary and how the feature should be evaluated.",{"type":27,"tag":28,"props":331,"children":332},{},[333],{"type":32,"value":334},"A useful early question is not merely:",{"type":27,"tag":28,"props":336,"children":337},{},[338],{"type":27,"tag":339,"props":340,"children":341},"strong",{},[342],{"type":32,"value":343},"What should the application do?",{"type":27,"tag":28,"props":345,"children":346},{},[347],{"type":32,"value":348},"It is:",{"type":27,"tag":28,"props":350,"children":351},{},[352],{"type":27,"tag":339,"props":353,"children":354},{},[355],{"type":32,"value":356},"What decision will someone make because of what the application does?",{"type":27,"tag":28,"props":358,"children":359},{},[360],{"type":32,"value":361},"That question brings engineering, product, clinical, security, quality, and regulatory stakeholders into the same conversation.",{"type":27,"tag":28,"props":363,"children":364},{},[365],{"type":32,"value":366},"It also gives developers something more useful than a feature list.",{"type":27,"tag":28,"props":368,"children":369},{},[370],{"type":32,"value":371},"It tells them what must not fail.",{"type":27,"tag":64,"props":373,"children":375},{"id":374},"how-can-compliance-support-faster-product-development",[376],{"type":32,"value":377},"How can compliance support faster product development?",{"type":27,"tag":28,"props":379,"children":380},{},[381],{"type":32,"value":382},"Compliance supports speed when it creates a clear, traceable relationship between intended use, requirements, risks, implementation, testing, and evidence.",{"type":27,"tag":28,"props":384,"children":385},{},[386],{"type":32,"value":387},"It slows teams down when those relationships have to be reconstructed near the end of a project.",{"type":27,"tag":28,"props":389,"children":390},{},[391],{"type":32,"value":392},"A team may reach what appears to be the final stage of development and discover that it cannot show:",{"type":27,"tag":92,"props":394,"children":395},{},[396,401,406,411,416,421],{"type":27,"tag":96,"props":397,"children":398},{},[399],{"type":32,"value":400},"Why a requirement exists",{"type":27,"tag":96,"props":402,"children":403},{},[404],{"type":32,"value":405},"Which identified risk it addresses",{"type":27,"tag":96,"props":407,"children":408},{},[409],{"type":32,"value":410},"How the requirement affected the design",{"type":27,"tag":96,"props":412,"children":413},{},[414],{"type":32,"value":415},"Where it was implemented",{"type":27,"tag":96,"props":417,"children":418},{},[419],{"type":32,"value":420},"How the behavior was tested",{"type":27,"tag":96,"props":422,"children":423},{},[424],{"type":32,"value":425},"Whether a later change altered the risk",{"type":27,"tag":28,"props":427,"children":428},{},[429],{"type":32,"value":430},"Then the documentation has to be rebuilt.",{"type":27,"tag":28,"props":432,"children":433},{},[434],{"type":32,"value":435},"Testing may need to be repeated.",{"type":27,"tag":28,"props":437,"children":438},{},[439],{"type":32,"value":440},"Architecture may have to change.",{"type":27,"tag":28,"props":442,"children":443},{},[444],{"type":32,"value":445},"A nearly complete feature may need to be reconsidered because no one clearly defined what it was supposed to prove.",{"type":27,"tag":28,"props":447,"children":448},{},[449],{"type":32,"value":450},"A better approach is to make traceability and validation normal outputs of development.",{"type":27,"tag":28,"props":452,"children":453},{},[454,456,461],{"type":32,"value":455},"Art+Logic’s guidance recommends using a traceable Secure Software Development Life Cycle, defining intended use early, integrating validation during development, working in small validated increments, and designing modular boundaries between regulated and nonregulated functionality where appropriate. (",{"type":27,"tag":138,"props":457,"children":459},{"href":295,"rel":458},[142],[460],{"type":32,"value":145},{"type":32,"value":147},{"type":27,"tag":28,"props":463,"children":464},{},[465,467,474],{"type":32,"value":466},"The regulatory framework also continues to evolve. The FDA’s Quality Management System Regulation became effective on February 2, 2026. It amended 21 CFR Part 820 and incorporated ISO 13485:2016 by reference, along with additional FDA requirements. (",{"type":27,"tag":138,"props":468,"children":471},{"href":469,"rel":470},"https://www.fda.gov/medical-devices/postmarket-requirements-devices/quality-management-system-regulation-qmsr",[142],[472],{"type":32,"value":473},"U.S. Food and Drug Administration",{"type":32,"value":147},{"type":27,"tag":28,"props":476,"children":477},{},[478],{"type":32,"value":479},"That change reinforces a larger point.",{"type":27,"tag":28,"props":481,"children":482},{},[483],{"type":32,"value":484},"A medical product may remain in use for years. The organization needs a development process that can accommodate new features, vulnerabilities, integrations, regulatory expectations, and platform changes while preserving control over product behavior.",{"type":27,"tag":28,"props":486,"children":487},{},[488],{"type":32,"value":489},"Good compliance work doesn’t remove uncertainty.",{"type":27,"tag":28,"props":491,"children":492},{},[493],{"type":32,"value":494},"It gives the team a disciplined way to manage it.",{"type":27,"tag":64,"props":496,"children":498},{"id":497},"why-is-cybersecurity-part-of-product-behavior",[499],{"type":32,"value":500},"Why is cybersecurity part of product behavior?",{"type":27,"tag":28,"props":502,"children":503},{},[504],{"type":32,"value":505},"Cybersecurity is not only an infrastructure concern. It affects who can use the product, what information they can access, what actions they can take, and what happens when the system is misused or compromised.",{"type":27,"tag":28,"props":507,"children":508},{},[509],{"type":32,"value":510},"Encryption, firewalls, and penetration testing may all matter.",{"type":27,"tag":28,"props":512,"children":513},{},[514],{"type":32,"value":515},"But so do questions such as:",{"type":27,"tag":92,"props":517,"children":518},{},[519,524,529,534,539,544,549,554],{"type":27,"tag":96,"props":520,"children":521},{},[522],{"type":32,"value":523},"Who can see a particular result?",{"type":27,"tag":96,"props":525,"children":526},{},[527],{"type":32,"value":528},"What happens when a clinician changes roles?",{"type":27,"tag":96,"props":530,"children":531},{},[532],{"type":32,"value":533},"Can access be revoked promptly?",{"type":27,"tag":96,"props":535,"children":536},{},[537],{"type":32,"value":538},"Which actions are recorded in the audit trail?",{"type":27,"tag":96,"props":540,"children":541},{},[542],{"type":32,"value":543},"What information appears in logs or analytics systems?",{"type":27,"tag":96,"props":545,"children":546},{},[547],{"type":32,"value":548},"How are third-party services evaluated?",{"type":27,"tag":96,"props":550,"children":551},{},[552],{"type":32,"value":553},"How does the organization respond to a vulnerable dependency?",{"type":27,"tag":96,"props":555,"children":556},{},[557],{"type":32,"value":558},"What should happen when unusual behavior is detected?",{"type":27,"tag":28,"props":560,"children":561},{},[562,564,571],{"type":32,"value":563},"The HIPAA Security Rule requires covered entities and business associates to use appropriate administrative, physical, and technical safeguards to protect the confidentiality, integrity, and availability of electronic protected health information. Whether HIPAA applies to a particular product depends on the parties involved and the role the product plays in creating, receiving, maintaining, or transmitting protected information. (",{"type":27,"tag":138,"props":565,"children":568},{"href":566,"rel":567},"https://www.hhs.gov/hipaa/for-professionals/security/index.html",[142],[569],{"type":32,"value":570},"HHS.gov",{"type":32,"value":147},{"type":27,"tag":28,"props":573,"children":574},{},[575,577,583],{"type":32,"value":576},"Medical device cybersecurity has additional product-lifecycle implications. FDA guidance addresses cybersecurity considerations in device design, quality systems, and premarket submissions. (",{"type":27,"tag":138,"props":578,"children":581},{"href":579,"rel":580},"https://www.fda.gov/medical-devices/digital-health-center-excellence/cybersecurity",[142],[582],{"type":32,"value":473},{"type":32,"value":147},{"type":27,"tag":28,"props":585,"children":586},{},[587],{"type":32,"value":588},"The practical point is simple:",{"type":27,"tag":28,"props":590,"children":591},{},[592],{"type":32,"value":593},"Security decisions belong in product planning, architecture, development, testing, deployment, monitoring, and maintenance.",{"type":27,"tag":28,"props":595,"children":596},{},[597],{"type":32,"value":598},"They do not belong in a final checklist.",{"type":27,"tag":64,"props":600,"children":602},{"id":601},"how-should-teams-define-the-boundaries-of-a-digital-health-platform",[603],{"type":32,"value":604},"How should teams define the boundaries of a digital health platform?",{"type":27,"tag":28,"props":606,"children":607},{},[608],{"type":32,"value":609},"A useful product boundary separates components that have meaningfully different risks, responsibilities, rates of change, owners, or validation needs.",{"type":27,"tag":28,"props":611,"children":612},{},[613],{"type":32,"value":614},"Not every function in a digital health platform needs to be managed in exactly the same way.",{"type":27,"tag":28,"props":616,"children":617},{},[618],{"type":32,"value":619},"A clinical calculation may sit inside the regulated medical-device boundary.",{"type":27,"tag":28,"props":621,"children":622},{},[623],{"type":32,"value":624},"A general content-management system probably should not.",{"type":27,"tag":28,"props":626,"children":627},{},[628],{"type":32,"value":629},"A patient’s medical history may require strict access controls and auditability.",{"type":27,"tag":28,"props":631,"children":632},{},[633],{"type":32,"value":634},"Public educational content does not need the same treatment.",{"type":27,"tag":28,"props":636,"children":637},{},[638],{"type":32,"value":639},"A clinician-facing workflow may need to function under poor network conditions.",{"type":27,"tag":28,"props":641,"children":642},{},[643],{"type":32,"value":644},"An internal reporting dashboard may not.",{"type":27,"tag":28,"props":646,"children":647},{},[648],{"type":32,"value":649},"Separating these concerns can make a platform easier to understand, secure, test, validate, and change. It may also prevent an ordinary operational feature from becoming unnecessarily entangled with the most highly regulated part of the product.",{"type":27,"tag":28,"props":651,"children":652},{},[653],{"type":32,"value":654},"Modular design can help.",{"type":27,"tag":28,"props":656,"children":657},{},[658],{"type":32,"value":659},"But modularity does not simply mean creating more services, APIs, or repositories.",{"type":27,"tag":28,"props":661,"children":662},{},[663],{"type":32,"value":664},"A good boundary allows something important to change independently.",{"type":27,"tag":28,"props":666,"children":667},{},[668],{"type":32,"value":669},"A bad boundary just moves complexity somewhere else.",{"type":27,"tag":28,"props":671,"children":672},{},[673],{"type":32,"value":674},"Useful questions include:",{"type":27,"tag":92,"props":676,"children":677},{},[678,683,688,693,698,703,708],{"type":27,"tag":96,"props":679,"children":680},{},[681],{"type":32,"value":682},"Which components perform or directly support the medical function?",{"type":27,"tag":96,"props":684,"children":685},{},[686],{"type":32,"value":687},"Which features can change without changing the clinical behavior?",{"type":27,"tag":96,"props":689,"children":690},{},[691],{"type":32,"value":692},"Which information requires the strongest security controls?",{"type":27,"tag":96,"props":694,"children":695},{},[696],{"type":32,"value":697},"Which components need independent validation?",{"type":27,"tag":96,"props":699,"children":700},{},[701],{"type":32,"value":702},"Which integrations are likely to change frequently?",{"type":27,"tag":96,"props":704,"children":705},{},[706],{"type":32,"value":707},"Which services must remain available during an outage?",{"type":27,"tag":96,"props":709,"children":710},{},[711],{"type":32,"value":712},"Which parts of the product have different release schedules?",{"type":27,"tag":28,"props":714,"children":715},{},[716],{"type":32,"value":717},"The answers will vary by product.",{"type":27,"tag":28,"props":719,"children":720},{},[721],{"type":32,"value":722},"What matters is making the decisions intentionally.",{"type":27,"tag":64,"props":724,"children":726},{"id":725},"does-using-fhir-fast-heathcare-interoperability-resources-make-a-digital-health-product-interoperable",[727],{"type":32,"value":728},"Does using FHIR (Fast Heathcare Interoperability Resources) make a digital health product interoperable?",{"type":27,"tag":28,"props":730,"children":731},{},[732],{"type":32,"value":733},"FHIR makes structured healthcare information exchange easier, but using FHIR does not automatically make two systems operationally or clinically interoperable.",{"type":27,"tag":28,"props":735,"children":736},{},[737,739,746],{"type":32,"value":738},"FHIR is an HL7 standard for exchanging healthcare information electronically. (",{"type":27,"tag":138,"props":740,"children":743},{"href":741,"rel":742},"https://www.hl7.org/fhir/overview.html",[142],[744],{"type":32,"value":745},"HL7",{"type":32,"value":147},{"type":27,"tag":28,"props":748,"children":749},{},[750],{"type":32,"value":751},"It provides a shared structure for representing and exchanging information.",{"type":27,"tag":28,"props":753,"children":754},{},[755],{"type":32,"value":756},"That is necessary.",{"type":27,"tag":28,"props":758,"children":759},{},[760],{"type":32,"value":761},"It is not always sufficient.",{"type":27,"tag":28,"props":763,"children":764},{},[765],{"type":32,"value":766},"Two systems may use the same standard and still interpret a field differently.",{"type":27,"tag":28,"props":768,"children":769},{},[770],{"type":32,"value":771},"An integration may transmit data correctly without providing enough context for the recipient to understand it.",{"type":27,"tag":28,"props":773,"children":774},{},[775],{"type":32,"value":776},"A workflow may need to account for:",{"type":27,"tag":92,"props":778,"children":779},{},[780,785,790,795,800,805,810,815,820],{"type":27,"tag":96,"props":781,"children":782},{},[783],{"type":32,"value":784},"Duplicate patient records",{"type":27,"tag":96,"props":786,"children":787},{},[788],{"type":32,"value":789},"Delayed or partial updates",{"type":27,"tag":96,"props":791,"children":792},{},[793],{"type":32,"value":794},"Unit conversions",{"type":27,"tag":96,"props":796,"children":797},{},[798],{"type":32,"value":799},"Conflicting sources",{"type":27,"tag":96,"props":801,"children":802},{},[803],{"type":32,"value":804},"Changing identifiers",{"type":27,"tag":96,"props":806,"children":807},{},[808],{"type":32,"value":809},"Missing clinical context",{"type":27,"tag":96,"props":811,"children":812},{},[813],{"type":32,"value":814},"Differences in terminology",{"type":27,"tag":96,"props":816,"children":817},{},[818],{"type":32,"value":819},"Failed or repeated messages",{"type":27,"tag":96,"props":821,"children":822},{},[823],{"type":32,"value":824},"Authorization and consent rules",{"type":27,"tag":28,"props":826,"children":827},{},[828],{"type":32,"value":829},"The useful question is not merely:",{"type":27,"tag":28,"props":831,"children":832},{},[833],{"type":27,"tag":339,"props":834,"children":835},{},[836],{"type":32,"value":837},"Can the systems exchange data?",{"type":27,"tag":28,"props":839,"children":840},{},[841],{"type":32,"value":348},{"type":27,"tag":28,"props":843,"children":844},{},[845],{"type":27,"tag":339,"props":846,"children":847},{},[848],{"type":32,"value":849},"Can the right person understand and act on that data after it arrives?",{"type":27,"tag":28,"props":851,"children":852},{},[853,855,861],{"type":32,"value":854},"Art+Logic’s biomedical software work includes medical-data consolidation, secure organizational workflows, and interoperability involving FHIR, HL7, and DICOM. The company also works with connected medical devices, cloud platforms, mobile diagnostics, clinical support tools, and patient-facing applications. (",{"type":27,"tag":138,"props":856,"children":859},{"href":857,"rel":858},"https://artandlogic.com/biomedical-software/",[142],[860],{"type":32,"value":145},{"type":32,"value":147},{"type":27,"tag":28,"props":863,"children":864},{},[865],{"type":32,"value":866},"Those capabilities belong together because interoperability is not simply a connector at the edge of a product.",{"type":27,"tag":28,"props":868,"children":869},{},[870],{"type":32,"value":871},"It is part of how the product works.",{"type":27,"tag":64,"props":873,"children":875},{"id":874},"why-is-clinical-usability-a-safety-concern",[876],{"type":32,"value":877},"Why is clinical usability a safety concern?",{"type":27,"tag":28,"props":879,"children":880},{},[881],{"type":32,"value":882},"Clinical usability affects whether people can interpret information, complete important actions, and recover from mistakes under real working conditions.",{"type":27,"tag":28,"props":884,"children":885},{},[886],{"type":32,"value":887},"A technically correct interface may still be difficult to use.",{"type":27,"tag":28,"props":889,"children":890},{},[891],{"type":32,"value":892},"That becomes more consequential when the user is working in an emergency department, an intensive care unit, a clinic, or another time-sensitive environment.",{"type":27,"tag":28,"props":894,"children":895},{},[896],{"type":32,"value":897},"The application may contain the correct information.",{"type":27,"tag":28,"props":899,"children":900},{},[901],{"type":32,"value":902},"But can someone find it quickly?",{"type":27,"tag":28,"props":904,"children":905},{},[906],{"type":32,"value":907},"Does the interface make important distinctions visible?",{"type":27,"tag":28,"props":909,"children":910},{},[911],{"type":32,"value":912},"Does it use language that matches the user’s clinical context?",{"type":27,"tag":28,"props":914,"children":915},{},[916],{"type":32,"value":917},"Can someone recognize and correct an error?",{"type":27,"tag":28,"props":919,"children":920},{},[921],{"type":32,"value":922},"Does it behave predictably when the network is unreliable?",{"type":27,"tag":28,"props":924,"children":925},{},[926],{"type":32,"value":927},"Does it show the right amount of information for the decision being made?",{"type":27,"tag":28,"props":929,"children":930},{},[931,933,938],{"type":32,"value":932},"Art+Logic worked with the Emergency Medicine Residents’ Association on its PressorDex application. A physician involved with the product emphasized that applications used in high-intensity clinical environments need content that is clear, reliable, and easy to use. (",{"type":27,"tag":138,"props":934,"children":936},{"href":857,"rel":935},[142],[937],{"type":32,"value":145},{"type":32,"value":147},{"type":27,"tag":28,"props":940,"children":941},{},[942],{"type":32,"value":943},"That principle applies beyond a single application.",{"type":27,"tag":28,"props":945,"children":946},{},[947],{"type":32,"value":948},"Usability is not the decorative layer added after the difficult engineering work is finished.",{"type":27,"tag":28,"props":950,"children":951},{},[952],{"type":32,"value":953},"In medical software, it is part of whether the system works.",{"type":27,"tag":64,"props":955,"children":957},{"id":956},"should-legacy-medical-software-be-rebuilt-from-scratch",[958],{"type":32,"value":959},"Should legacy medical software be rebuilt from scratch?",{"type":27,"tag":28,"props":961,"children":962},{},[963],{"type":32,"value":964},"Not necessarily.",{"type":27,"tag":28,"props":966,"children":967},{},[968],{"type":32,"value":969},"The appropriate strategy may be to repair a fragile area, update an unsupported dependency, replace selected components, improve testing, redesign a critical workflow, or migrate the application in phases.",{"type":27,"tag":28,"props":971,"children":972},{},[973],{"type":32,"value":974},"Existing medical software often contains more than old code.",{"type":27,"tag":28,"props":976,"children":977},{},[978],{"type":32,"value":979},"It may also contain:",{"type":27,"tag":92,"props":981,"children":982},{},[983,988,993,998,1003,1008,1013],{"type":27,"tag":96,"props":984,"children":985},{},[986],{"type":32,"value":987},"Validated clinical behavior",{"type":27,"tag":96,"props":989,"children":990},{},[991],{"type":32,"value":992},"Specialized workflows",{"type":27,"tag":96,"props":994,"children":995},{},[996],{"type":32,"value":997},"Regulatory documentation",{"type":27,"tag":96,"props":999,"children":1000},{},[1001],{"type":32,"value":1002},"Device or EHR integrations",{"type":27,"tag":96,"props":1004,"children":1005},{},[1006],{"type":32,"value":1007},"Years of edge-case knowledge",{"type":27,"tag":96,"props":1009,"children":1010},{},[1011],{"type":32,"value":1012},"Familiar interactions that users depend on",{"type":27,"tag":96,"props":1014,"children":1015},{},[1016],{"type":32,"value":1017},"Institutional knowledge held by a small number of people",{"type":27,"tag":28,"props":1019,"children":1020},{},[1021],{"type":32,"value":1022},"Rebuilding everything may remove technical debt.",{"type":27,"tag":28,"props":1024,"children":1025},{},[1026],{"type":32,"value":1027},"It may also recreate years of risk.",{"type":27,"tag":28,"props":1029,"children":1030},{},[1031,1033,1039],{"type":32,"value":1032},"Art+Logic recently modernized a healthcare-focused mobile application used by medical professionals to access critical treatment information. The application was built on Xamarin, and the platform’s deprecation created growing continuity, maintenance, and architectural risks. A complete rewrite would have been prohibitively expensive. (",{"type":27,"tag":138,"props":1034,"children":1037},{"href":1035,"rel":1036},"https://artandlogic.com/ai-assisted-modernization/",[142],[1038],{"type":32,"value":145},{"type":32,"value":147},{"type":27,"tag":28,"props":1041,"children":1042},{},[1043],{"type":32,"value":1044},"Earlier attempts had used generative AI to convert the application in a large automated pass.",{"type":27,"tag":28,"props":1046,"children":1047},{},[1048],{"type":32,"value":1049},"The result compiled.",{"type":27,"tag":28,"props":1051,"children":1052},{},[1053],{"type":32,"value":1054},"It also removed or disabled important functionality.",{"type":27,"tag":28,"props":1056,"children":1057},{},[1058],{"type":32,"value":1059},"That is a dangerous kind of success.",{"type":27,"tag":28,"props":1061,"children":1062},{},[1063],{"type":32,"value":1064},"The build passes.",{"type":27,"tag":28,"props":1066,"children":1067},{},[1068],{"type":32,"value":1069},"The newer framework is present.",{"type":27,"tag":28,"props":1071,"children":1072},{},[1073],{"type":32,"value":1074},"But the software no longer does everything its users depend on.",{"type":27,"tag":28,"props":1076,"children":1077},{},[1078,1080,1085],{"type":32,"value":1079},"Art+Logic took a phased approach instead. Engineers migrated the application incrementally and used AI for repetitive, pattern-based implementation tasks. Architecture, review, testing, and validation remained under experienced human control. (",{"type":27,"tag":138,"props":1081,"children":1083},{"href":1035,"rel":1082},[142],[1084],{"type":32,"value":145},{"type":32,"value":147},{"type":27,"tag":28,"props":1087,"children":1088},{},[1089],{"type":32,"value":1090},"The project did more than move code from Xamarin to .NET MAUI.",{"type":27,"tag":28,"props":1092,"children":1093},{},[1094,1096,1101],{"type":32,"value":1095},"The team also redesigned clinical workflows, improved a complex medical reference tool, resolved known legacy bugs, and introduced new licensing and account-management capabilities. The work was delivered hundreds of development hours under budget. (",{"type":27,"tag":138,"props":1097,"children":1099},{"href":1035,"rel":1098},[142],[1100],{"type":32,"value":145},{"type":32,"value":147},{"type":27,"tag":28,"props":1103,"children":1104},{},[1105],{"type":32,"value":1106},"The important lesson isn’t that every healthcare modernization project should use AI.",{"type":27,"tag":28,"props":1108,"children":1109},{},[1110],{"type":32,"value":1111},"It is that modernization should preserve what matters while creating room for what comes next.",{"type":27,"tag":64,"props":1113,"children":1115},{"id":1114},"where-does-ai-fit-in-medical-software-development",[1116],{"type":32,"value":1117},"Where does AI fit in medical software development?",{"type":27,"tag":28,"props":1119,"children":1120},{},[1121],{"type":32,"value":1122},"AI is most useful when the task is bounded, the expected result is understandable, and qualified people can review and validate the output.",{"type":27,"tag":28,"props":1124,"children":1125},{},[1126],{"type":32,"value":1127},"It may help teams:",{"type":27,"tag":92,"props":1129,"children":1130},{},[1131,1136,1141,1146,1151,1156,1161],{"type":27,"tag":96,"props":1132,"children":1133},{},[1134],{"type":32,"value":1135},"Transform repetitive code patterns",{"type":27,"tag":96,"props":1137,"children":1138},{},[1139],{"type":32,"value":1140},"Generate test scenarios",{"type":27,"tag":96,"props":1142,"children":1143},{},[1144],{"type":32,"value":1145},"Explore an unfamiliar codebase",{"type":27,"tag":96,"props":1147,"children":1148},{},[1149],{"type":32,"value":1150},"Draft routine implementation",{"type":27,"tag":96,"props":1152,"children":1153},{},[1154],{"type":32,"value":1155},"Compare existing and migrated behavior",{"type":27,"tag":96,"props":1157,"children":1158},{},[1159],{"type":32,"value":1160},"Accelerate documentation work",{"type":27,"tag":96,"props":1162,"children":1163},{},[1164],{"type":32,"value":1165},"Identify patterns across large technical artifacts",{"type":27,"tag":28,"props":1167,"children":1168},{},[1169],{"type":32,"value":1170},"But speed is only useful when the team knows what must remain true.",{"type":27,"tag":28,"props":1172,"children":1173},{},[1174],{"type":32,"value":1175},"Does the migrated calculation produce the same result?",{"type":27,"tag":28,"props":1177,"children":1178},{},[1179],{"type":32,"value":1180},"Does the workflow still account for the same clinical conditions?",{"type":27,"tag":28,"props":1182,"children":1183},{},[1184],{"type":32,"value":1185},"Has generated code introduced an unsupported dependency?",{"type":27,"tag":28,"props":1187,"children":1188},{},[1189],{"type":32,"value":1190},"Does the new implementation expose sensitive information?",{"type":27,"tag":28,"props":1192,"children":1193},{},[1194],{"type":32,"value":1195},"Can the team explain how the resulting behavior was tested?",{"type":27,"tag":28,"props":1197,"children":1198},{},[1199,1201,1206],{"type":32,"value":1200},"In Art+Logic’s modernization project, AI worked well when it was assigned repetitive, constrained work and experienced developers reviewed the result. It failed when it was treated as an autonomous replacement for understanding the application. (",{"type":27,"tag":138,"props":1202,"children":1204},{"href":1035,"rel":1203},[142],[1205],{"type":32,"value":145},{"type":32,"value":147},{"type":27,"tag":28,"props":1208,"children":1209},{},[1210,1212,1218],{"type":32,"value":1211},"AI-enabled medical device functions create another layer of lifecycle responsibility. The FDA’s current draft guidance for AI-enabled device software functions recommends a total-product-lifecycle approach to risk management and marketing-submission information. (",{"type":27,"tag":138,"props":1213,"children":1216},{"href":1214,"rel":1215},"https://www.fda.gov/medical-devices/software-medical-device-samd/artificial-intelligence-software-medical-device",[142],[1217],{"type":32,"value":473},{"type":32,"value":147},{"type":27,"tag":28,"props":1220,"children":1221},{},[1222],{"type":32,"value":1223},"AI may help a team move faster.",{"type":27,"tag":28,"props":1225,"children":1226},{},[1227],{"type":32,"value":1228},"It does not get to decide what safe, correct, or clinically useful means.",{"type":27,"tag":64,"props":1230,"children":1232},{"id":1231},"what-should-teams-ask-before-building-a-digital-health-platform",[1233],{"type":32,"value":1234},"What should teams ask before building a digital health platform?",{"type":27,"tag":28,"props":1236,"children":1237},{},[1238],{"type":32,"value":1239},"Before choosing a framework, cloud provider, AI model, or integration vendor, teams should be able to answer a set of product and lifecycle questions.",{"type":27,"tag":1241,"props":1242,"children":1244},"h4",{"id":1243},"intended-use-and-clinical-behavior",[1245],{"type":32,"value":1246},"Intended use and clinical behavior",{"type":27,"tag":92,"props":1248,"children":1249},{},[1250,1255,1260,1265,1270],{"type":27,"tag":96,"props":1251,"children":1252},{},[1253],{"type":32,"value":1254},"What is the product’s intended medical purpose?",{"type":27,"tag":96,"props":1256,"children":1257},{},[1258],{"type":32,"value":1259},"Who will use it?",{"type":27,"tag":96,"props":1261,"children":1262},{},[1263],{"type":32,"value":1264},"Which decisions will depend on its output?",{"type":27,"tag":96,"props":1266,"children":1267},{},[1268],{"type":32,"value":1269},"What would happen if the software produced the wrong result?",{"type":27,"tag":96,"props":1271,"children":1272},{},[1273],{"type":32,"value":1274},"Which functions belong inside the regulated product boundary?",{"type":27,"tag":1241,"props":1276,"children":1278},{"id":1277},"data-and-interoperability",[1279],{"type":32,"value":1280},"Data and interoperability",{"type":27,"tag":92,"props":1282,"children":1283},{},[1284,1289,1294,1299],{"type":27,"tag":96,"props":1285,"children":1286},{},[1287],{"type":32,"value":1288},"What information will the product create, receive, transform, and share?",{"type":27,"tag":96,"props":1290,"children":1291},{},[1292],{"type":32,"value":1293},"Which external systems must it connect to?",{"type":27,"tag":96,"props":1295,"children":1296},{},[1297],{"type":32,"value":1298},"How will the team handle incomplete, late, duplicated, or conflicting data?",{"type":27,"tag":96,"props":1300,"children":1301},{},[1302],{"type":32,"value":1303},"What context will users need to interpret exchanged information safely?",{"type":27,"tag":1241,"props":1305,"children":1307},{"id":1306},"security-and-privacy",[1308],{"type":32,"value":1309},"Security and privacy",{"type":27,"tag":92,"props":1311,"children":1312},{},[1313,1318,1323,1328],{"type":27,"tag":96,"props":1314,"children":1315},{},[1316],{"type":32,"value":1317},"Which parties will create, receive, maintain, or transmit sensitive information?",{"type":27,"tag":96,"props":1319,"children":1320},{},[1321],{"type":32,"value":1322},"Who should be allowed to access each type of data?",{"type":27,"tag":96,"props":1324,"children":1325},{},[1326],{"type":32,"value":1327},"How will identity, authorization, logging, monitoring, and incident response work?",{"type":27,"tag":96,"props":1329,"children":1330},{},[1331],{"type":32,"value":1332},"How will third-party dependencies and services be evaluated over time?",{"type":27,"tag":1241,"props":1334,"children":1336},{"id":1335},"development-and-validation",[1337],{"type":32,"value":1338},"Development and validation",{"type":27,"tag":92,"props":1340,"children":1341},{},[1342,1347,1352,1357],{"type":27,"tag":96,"props":1343,"children":1344},{},[1345],{"type":32,"value":1346},"How will requirements, risks, implementation, testing, and evidence remain traceable?",{"type":27,"tag":96,"props":1348,"children":1349},{},[1350],{"type":32,"value":1351},"Which components can be tested or released independently?",{"type":27,"tag":96,"props":1353,"children":1354},{},[1355],{"type":32,"value":1356},"How will the team evaluate the effect of a change?",{"type":27,"tag":96,"props":1358,"children":1359},{},[1360],{"type":32,"value":1361},"What records will be needed for regulatory review or future maintenance?",{"type":27,"tag":1241,"props":1363,"children":1365},{"id":1364},"usability-and-operations",[1366],{"type":32,"value":1367},"Usability and operations",{"type":27,"tag":92,"props":1369,"children":1370},{},[1371,1376,1381,1386],{"type":27,"tag":96,"props":1372,"children":1373},{},[1374],{"type":32,"value":1375},"Which workflows are time-sensitive or safety-critical?",{"type":27,"tag":96,"props":1377,"children":1378},{},[1379],{"type":32,"value":1380},"What happens when the network, an integration, or a device is unavailable?",{"type":27,"tag":96,"props":1382,"children":1383},{},[1384],{"type":32,"value":1385},"How will users recognize errors or incomplete information?",{"type":27,"tag":96,"props":1387,"children":1388},{},[1389],{"type":32,"value":1390},"How will the organization support the product after launch?",{"type":27,"tag":1241,"props":1392,"children":1394},{"id":1393},"modernization-and-maintainability",[1395],{"type":32,"value":1396},"Modernization and maintainability",{"type":27,"tag":92,"props":1398,"children":1399},{},[1400,1405,1410,1415,1420],{"type":27,"tag":96,"props":1401,"children":1402},{},[1403],{"type":32,"value":1404},"Which technologies are approaching end of support?",{"type":27,"tag":96,"props":1406,"children":1407},{},[1408],{"type":32,"value":1409},"Where is institutional knowledge concentrated?",{"type":27,"tag":96,"props":1411,"children":1412},{},[1413],{"type":32,"value":1414},"Which areas are difficult or dangerous to change?",{"type":27,"tag":96,"props":1416,"children":1417},{},[1418],{"type":32,"value":1419},"What business or clinical capabilities must be preserved during modernization?",{"type":27,"tag":96,"props":1421,"children":1422},{},[1423],{"type":32,"value":1424},"What does the organization need the platform to make possible next?",{"type":27,"tag":28,"props":1426,"children":1427},{},[1428],{"type":32,"value":1429},"These questions are not separate from software development.",{"type":27,"tag":28,"props":1431,"children":1432},{},[1433],{"type":32,"value":1434},"They are what make good software development possible.",{"type":27,"tag":64,"props":1436,"children":1438},{"id":1437},"the-platform-is-the-product",[1439],{"type":32,"value":1440},"The platform is the product",{"type":27,"tag":28,"props":1442,"children":1443},{},[1444],{"type":32,"value":1445},"SaMD established that software can perform meaningful medical functions independently of traditional device hardware.",{"type":27,"tag":28,"props":1447,"children":1448},{},[1449],{"type":32,"value":1450},"The next challenge is connecting those functions to the people, information, devices, and systems involved in care—without making the product less secure, less understandable, or harder to change.",{"type":27,"tag":28,"props":1452,"children":1453},{},[1454],{"type":32,"value":1455},"That work requires more than technical implementation.",{"type":27,"tag":28,"props":1457,"children":1458},{},[1459],{"type":32,"value":1460},"It requires product strategy, healthcare domain knowledge, secure architecture, regulatory awareness, interoperability, UX design, validation, and a realistic plan for the full software lifecycle.",{"type":27,"tag":28,"props":1462,"children":1463},{},[1464,1466,1471],{"type":32,"value":1465},"Art+Logic designs and develops medical software ranging from SaMD and clinical support tools to connected-device applications, patient experiences, cloud platforms, and healthcare-data systems. The company also helps organizations update or recover existing products when aging technology, difficult architecture, or incomplete implementation is standing in the way. (",{"type":27,"tag":138,"props":1467,"children":1469},{"href":857,"rel":1468},[142],[1470],{"type":32,"value":145},{"type":32,"value":147},{"type":27,"tag":28,"props":1473,"children":1474},{},[1475],{"type":32,"value":1476},"Because in digital health, releasing the application is not the finish line.",{"type":27,"tag":28,"props":1478,"children":1479},{},[1480],{"type":32,"value":1481},"It is the beginning of a system the organization will need to understand, trust, secure, and improve for years.",{"type":27,"tag":64,"props":1483,"children":1485},{"id":1484},"faqs",[1486],{"type":32,"value":1487},"FAQs",{"type":27,"tag":1241,"props":1489,"children":1491},{"id":1490},"what-is-software-as-a-medical-device",[1492],{"type":32,"value":1493},"What is Software as a Medical Device?",{"type":27,"tag":28,"props":1495,"children":1496},{},[1497],{"type":32,"value":1498},"Software as a Medical Device, or SaMD, is software that performs a medical function independently of a traditional physical medical device. Depending on its intended use, it may support diagnosis, monitoring, treatment, clinical decision-making, or patient care.",{"type":27,"tag":1241,"props":1500,"children":1502},{"id":1501},"what-is-the-difference-between-samd-and-a-digital-health-platform-1",[1503],{"type":32,"value":131},{"type":27,"tag":28,"props":1505,"children":1506},{},[1507],{"type":32,"value":1508},"SaMD describes a software-based medical function. A digital health platform is the larger system that may connect that function with patient applications, clinician tools, device data, identity services, analytics, administration, and other healthcare systems.",{"type":27,"tag":1241,"props":1510,"children":1512},{"id":1511},"how-do-you-build-compliant-samd-software-without-slowing-development",[1513],{"type":32,"value":1514},"How do you build compliant SaMD software without slowing development?",{"type":27,"tag":28,"props":1516,"children":1517},{},[1518],{"type":32,"value":1519},"Define intended use and regulatory boundaries early, use a traceable development lifecycle, connect requirements to risks and tests, validate features incrementally, and produce documentation as part of development. This reduces the late rework caused by reconstructing evidence after the software is built.",{"type":27,"tag":1241,"props":1521,"children":1523},{"id":1522},"is-every-digital-health-application-subject-to-hipaa",[1524],{"type":32,"value":1525},"Is every digital health application subject to HIPAA?",{"type":27,"tag":28,"props":1527,"children":1528},{},[1529],{"type":32,"value":1530},"No. HIPAA generally applies to covered entities, business associates, and protected health information handled within those relationships. A product may still be subject to other privacy, medical-device, cybersecurity, consumer-protection, or state requirements.",{"type":27,"tag":1241,"props":1532,"children":1534},{"id":1533},"does-using-fhir-make-an-application-interoperable",[1535],{"type":32,"value":1536},"Does using FHIR make an application interoperable?",{"type":27,"tag":28,"props":1538,"children":1539},{},[1540],{"type":32,"value":1541},"Not by itself. FHIR provides a standard structure for exchanging healthcare information, but teams must still align terminology, identifiers, context, authorization, error handling, workflows, and the meaning of exchanged data.",{"type":27,"tag":1241,"props":1543,"children":1545},{"id":1544},"can-ai-be-used-to-develop-or-modernize-medical-software",[1546],{"type":32,"value":1547},"Can AI be used to develop or modernize medical software?",{"type":27,"tag":28,"props":1549,"children":1550},{},[1551],{"type":32,"value":1552},"Yes. AI can accelerate repetitive implementation, analysis, testing, and documentation tasks. Experienced professionals should still control architecture, clinical behavior, security, code review, testing, validation, and regulatory evidence.",{"type":27,"tag":1241,"props":1554,"children":1556},{"id":1555},"should-legacy-medical-software-be-rebuilt-from-scratch-1",[1557],{"type":32,"value":959},{"type":27,"tag":28,"props":1559,"children":1560},{},[1561],{"type":32,"value":1562},"Not always. A phased modernization may be safer and more economical when the existing product contains valuable workflows, integrations, validated behavior, and institutional knowledge. The right approach depends on platform risk, maintainability, product goals, and the cost of preserving or recreating existing functionality.",{"type":27,"tag":1241,"props":1564,"children":1566},{"id":1565},"why-is-usability-important-in-clinical-software",[1567],{"type":32,"value":1568},"Why is usability important in clinical software?",{"type":27,"tag":28,"props":1570,"children":1571},{},[1572],{"type":32,"value":1573},"Clinical software is often used under time pressure and in high-consequence environments. Clear information, predictable behavior, efficient workflows, accessible design, and effective error recovery can affect whether users understand and act on the software’s output correctly.",{"title":8,"searchDepth":1575,"depth":1575,"links":1576},3,[1577,1578,1579,1580,1581,1582,1583,1584,1585,1586,1587,1588,1597,1598],{"id":66,"depth":1575,"text":69},{"id":87,"depth":1575,"text":90},{"id":128,"depth":1575,"text":131},{"id":279,"depth":1575,"text":282},{"id":374,"depth":1575,"text":377},{"id":497,"depth":1575,"text":500},{"id":601,"depth":1575,"text":604},{"id":725,"depth":1575,"text":728},{"id":874,"depth":1575,"text":877},{"id":956,"depth":1575,"text":959},{"id":1114,"depth":1575,"text":1117},{"id":1231,"depth":1575,"text":1234,"children":1589},[1590,1592,1593,1594,1595,1596],{"id":1243,"depth":1591,"text":1246},4,{"id":1277,"depth":1591,"text":1280},{"id":1306,"depth":1591,"text":1309},{"id":1335,"depth":1591,"text":1338},{"id":1364,"depth":1591,"text":1367},{"id":1393,"depth":1591,"text":1396},{"id":1437,"depth":1575,"text":1440},{"id":1484,"depth":1575,"text":1487,"children":1599},[1600,1601,1602,1603,1604,1605,1606,1607],{"id":1490,"depth":1591,"text":1493},{"id":1501,"depth":1591,"text":131},{"id":1511,"depth":1591,"text":1514},{"id":1522,"depth":1591,"text":1525},{"id":1533,"depth":1591,"text":1536},{"id":1544,"depth":1591,"text":1547},{"id":1555,"depth":1591,"text":959},{"id":1565,"depth":1591,"text":1568},"markdown","content:cperez:2026-07-21:building-digital-health-platforms-beyond-samd.md","content","cperez/2026-07-21/building-digital-health-platforms-beyond-samd.md","cperez/2026-07-21/building-digital-health-platforms-beyond-samd","md",{"_path":1615,"_dir":1616,"_draft":7,"_partial":7,"_locale":8,"title":1617,"description":1618,"publishDate":1616,"image":1619,"author":1620,"tags":1621,"excerpt":1618,"body":1626,"_type":1608,"_id":3035,"_source":1610,"_file":3036,"_stem":3037,"_extension":1613},"/cperez/2026-07-16/rebuild-vs-modernize-software-cfo-guide","2026-07-16","Rebuild or Modernize? A Guide to Making the Right Software Investment","Every aging software system eventually reaches a financial decision point.","/cperez/2026-07-16/img/rebuild-vs-modernize-software-cfo-guide.jpg",{"name":13,"user":14},[18,1622,1623,1624,1625],"legacy migration","tech debt","application modernization","legacy software",{"type":24,"children":1627,"toc":2991},[1628,1632,1637,1642,1650,1655,1660,1665,1670,1676,1688,1699,1704,1712,1717,1722,1726,1734,1740,1745,1750,1762,1767,1772,1777,1788,1793,1799,1804,1809,1814,1833,1838,1844,1849,1854,1859,1865,1870,1875,1880,1885,1890,1896,1907,1912,1917,1923,1928,1933,1938,1944,1949,1954,1966,1971,1976,1981,1986,1991,1996,2001,2007,2012,2017,2023,2028,2033,2038,2043,2049,2054,2059,2064,2070,2075,2080,2085,2090,2096,2101,2106,2112,2117,2122,2127,2133,2138,2143,2149,2154,2159,2164,2175,2181,2186,2191,2196,2202,2207,2212,2223,2229,2234,2239,2244,2250,2255,2266,2271,2277,2282,2287,2293,2298,2303,2308,2313,2318,2323,2328,2333,2339,2344,2349,2354,2359,2365,2370,2375,2380,2418,2423,2429,2434,2439,2468,2473,2478,2484,2489,2494,2499,2504,2509,2515,2520,2525,2530,2535,2540,2546,2551,2556,2561,2566,2571,2576,2581,2587,2592,2597,2602,2607,2612,2617,2623,2628,2666,2671,2709,2714,2742,2747,2753,2758,2763,2768,2811,2816,2821,2827,2832,2837,2842,2847,2852,2863,2869,2874,2879,2884,2889,2897,2902,2907,2912,2916,2920,2926,2931,2937,2942,2948,2953,2959,2964,2970,2975,2981,2986],{"type":27,"tag":28,"props":1629,"children":1630},{},[1631],{"type":32,"value":1618},{"type":27,"tag":28,"props":1633,"children":1634},{},[1635],{"type":32,"value":1636},"The business depends on it. Teams complain about it. Customers may never see it directly, but they feel its limits in slower service, delayed releases, clunky workflows, inconsistent data, or rising support costs. Engineering says the architecture is holding the company back. Operations says the system is too important to disrupt. Finance sees the maintenance spend growing, but also knows that “let’s rebuild it from scratch” can become an expensive, open-ended bet.",{"type":27,"tag":28,"props":1638,"children":1639},{},[1640],{"type":32,"value":1641},"For CFOs, the core dilemma comes down to this:",{"type":27,"tag":28,"props":1643,"children":1644},{},[1645],{"type":27,"tag":339,"props":1646,"children":1647},{},[1648],{"type":32,"value":1649},"Should we rebuild this software, or modernize what we already have?",{"type":27,"tag":28,"props":1651,"children":1652},{},[1653],{"type":32,"value":1654},"The answer is rarely obvious. A full rebuild can sound clean and decisive, but it also carries serious cost, timeline concerns, and adoption risk. Modernization can preserve valuable business logic and reduce disruption, but it may not go far enough if the foundation no longer supports where the business needs to go.",{"type":27,"tag":28,"props":1656,"children":1657},{},[1658],{"type":32,"value":1659},"This isn’t just a technology decision; it’s a capital allocation decision.",{"type":27,"tag":28,"props":1661,"children":1662},{},[1663],{"type":32,"value":1664},"AI is also changing the economics of this decision. The early work of modernization, understanding legacy code, surfacing undocumented business logic, identifying dependencies, and mapping a phased path forward, has historically required a lot of manual analysis. Modern AI tools can accelerate parts of that work, giving teams a faster and clearer view of what they are dealing with. That does not replace experienced engineers, especially when business context, architecture, security, and tradeoffs matter. But it can change the financial equation. For CFOs evaluating whether to rebuild or modernize, AI may reduce discovery time, improve visibility into hidden complexity, and make phased modernization a more practical option than it would have been a few years ago.",{"type":27,"tag":28,"props":1666,"children":1667},{},[1668],{"type":32,"value":1669},"For CFOs, the goal is to understand which path creates the best risk-adjusted return: lower operating costs, faster delivery, stronger security, better reporting, improved customer experience, and more flexibility for future growth.",{"type":27,"tag":64,"props":1671,"children":1673},{"id":1672},"rebuild-vs-modernize-whats-the-difference",[1674],{"type":32,"value":1675},"Rebuild vs. Modernize: What’s the Difference?",{"type":27,"tag":28,"props":1677,"children":1678},{},[1679,1681,1686],{"type":32,"value":1680},"A ",{"type":27,"tag":339,"props":1682,"children":1683},{},[1684],{"type":32,"value":1685},"software rebuild",{"type":32,"value":1687}," means replacing an existing application with a new system, usually built from the ground up. The team may reuse requirements, workflows, data models, or integrations, but the core application is recreated on a new technical foundation.",{"type":27,"tag":28,"props":1689,"children":1690},{},[1691,1692,1697],{"type":32,"value":1680},{"type":27,"tag":339,"props":1693,"children":1694},{},[1695],{"type":32,"value":1696},"software modernization",{"type":32,"value":1698}," effort improves the existing system without replacing everything at once. That can include refactoring code, updating infrastructure, improving security, moving selected workloads to the cloud, replacing outdated components, exposing APIs, improving observability, redesigning workflows, or gradually separating a monolithic system into more flexible services.",{"type":27,"tag":28,"props":1700,"children":1701},{},[1702],{"type":32,"value":1703},"Put simply:",{"type":27,"tag":28,"props":1705,"children":1706},{},[1707],{"type":27,"tag":339,"props":1708,"children":1709},{},[1710],{"type":32,"value":1711},"Rebuilding replaces the system. Modernizing evolves the system.",{"type":27,"tag":28,"props":1713,"children":1714},{},[1715],{"type":32,"value":1716},"But in practice, the line is not always clean. Many successful software investments are hybrids. A company may modernize the parts of a system that still work while rebuilding the pieces that create the most cost, risk, or strategic constraint.",{"type":27,"tag":28,"props":1718,"children":1719},{},[1720],{"type":32,"value":1721},"For CFOs, the better question is not “Which option is more modern?”",{"type":27,"tag":28,"props":1723,"children":1724},{},[1725],{"type":32,"value":348},{"type":27,"tag":28,"props":1727,"children":1728},{},[1729],{"type":27,"tag":339,"props":1730,"children":1731},{},[1732],{"type":32,"value":1733},"Which investment path produces measurable business value without creating unnecessary operational risk?",{"type":27,"tag":64,"props":1735,"children":1737},{"id":1736},"why-legacy-systems-survive-so-long",[1738],{"type":32,"value":1739},"Why Legacy Systems Survive So Long",{"type":27,"tag":28,"props":1741,"children":1742},{},[1743],{"type":32,"value":1744},"It is easy to assume legacy systems stick around because organizations are resistant to change.",{"type":27,"tag":28,"props":1746,"children":1747},{},[1748],{"type":32,"value":1749},"More often, they survive because they are doing something important.",{"type":27,"tag":28,"props":1751,"children":1752},{},[1753,1755,1761],{"type":32,"value":1754},"Legacy systems often support critical business operations, contain years of accumulated business logic, and encode workflows that may not be documented anywhere else. Teams rely on them every day. Customers may interact with them directly or depend on processes they enable behind the scenes. The longer a system has been running, the more deeply it tends to connect with the organization around it. (",{"type":27,"tag":138,"props":1756,"children":1759},{"href":1757,"rel":1758},"https://artandlogic.com/newsletters/what-modernizing-legacy-systems-actually-means-in-practice/",[142],[1760],{"type":32,"value":145},{"type":32,"value":147},{"type":27,"tag":28,"props":1763,"children":1764},{},[1765],{"type":32,"value":1766},"That is what makes the rebuild-versus-modernize decision difficult.",{"type":27,"tag":28,"props":1768,"children":1769},{},[1770],{"type":32,"value":1771},"You are rarely replacing “just software.” You are changing a network of assumptions, workflows, reporting habits, integrations, exceptions, and institutional knowledge that has evolved.",{"type":27,"tag":28,"props":1773,"children":1774},{},[1775],{"type":32,"value":1776},"That is also why a rebuild can fail even when the new technology is better.",{"type":27,"tag":28,"props":1778,"children":1779},{},[1780,1782,1787],{"type":32,"value":1781},"If the project underestimates the business knowledge embedded in the existing system, teams may discover undocumented workflows, edge cases, reporting requirements, and integrations after development is already underway. As a result, costs increase, timelines stretch, and confidence erodes. (",{"type":27,"tag":138,"props":1783,"children":1785},{"href":1757,"rel":1784},[142],[1786],{"type":32,"value":145},{"type":32,"value":147},{"type":27,"tag":28,"props":1789,"children":1790},{},[1791],{"type":32,"value":1792},"For CFOs, the lesson is simple: before funding a rebuild, make sure the organization understands what the current system actually does.",{"type":27,"tag":64,"props":1794,"children":1796},{"id":1795},"the-hidden-cost-of-keeping-it-running",[1797],{"type":32,"value":1798},"The Hidden Cost of “Keeping It Running”",{"type":27,"tag":28,"props":1800,"children":1801},{},[1802],{"type":32,"value":1803},"Legacy software often looks cheaper than it is.",{"type":27,"tag":28,"props":1805,"children":1806},{},[1807],{"type":32,"value":1808},"On paper, the system is already built. The original investment is behind you. The team knows how to operate it. Customers are using it. Replacing it looks expensive.",{"type":27,"tag":28,"props":1810,"children":1811},{},[1812],{"type":32,"value":1813},"But maintaining an aging system can create a compounding drag on the business.",{"type":27,"tag":28,"props":1815,"children":1816},{},[1817,1819,1824,1826,1832],{"type":32,"value":1818},"Art+Logic has described this as a ",{"type":27,"tag":339,"props":1820,"children":1821},{},[1822],{"type":32,"value":1823},"velocity tax",{"type":32,"value":1825},": when small changes take too long, QA cycles drag, deployments are slow, and teams spend more time working around the system than improving it. (",{"type":27,"tag":138,"props":1827,"children":1830},{"href":1828,"rel":1829},"https://artandlogic.com/newsletters/is-your-legacy-system-holding-you-back/",[142],[1831],{"type":32,"value":145},{"type":32,"value":147},{"type":27,"tag":28,"props":1834,"children":1835},{},[1836],{"type":32,"value":1837},"For a CFO, that tax shows up in several ways.",{"type":27,"tag":1241,"props":1839,"children":1841},{"id":1840},"maintenance-cost",[1842],{"type":32,"value":1843},"Maintenance Cost",{"type":27,"tag":28,"props":1845,"children":1846},{},[1847],{"type":32,"value":1848},"Older systems often require more effort for routine changes. Engineers spend time understanding fragile code, avoiding side effects, patching outdated dependencies, or working around architectural constraints.",{"type":27,"tag":28,"props":1850,"children":1851},{},[1852],{"type":32,"value":1853},"That effort may be classified as a normal development expense, but financially it behaves more like debt service.",{"type":27,"tag":28,"props":1855,"children":1856},{},[1857],{"type":32,"value":1858},"The business keeps paying interest on past decisions.",{"type":27,"tag":1241,"props":1860,"children":1862},{"id":1861},"opportunity-cost",[1863],{"type":32,"value":1864},"Opportunity Cost",{"type":27,"tag":28,"props":1866,"children":1867},{},[1868],{"type":32,"value":1869},"When every product improvement takes too long, the company loses speed.",{"type":27,"tag":28,"props":1871,"children":1872},{},[1873],{"type":32,"value":1874},"New pricing models, customer features, integrations, automation initiatives, compliance updates, and reporting improvements may all be delayed because the software cannot support change efficiently.",{"type":27,"tag":28,"props":1876,"children":1877},{},[1878],{"type":32,"value":1879},"This is where legacy systems become a growth constraint.",{"type":27,"tag":28,"props":1881,"children":1882},{},[1883],{"type":32,"value":1884},"The issue is not only what the system costs.",{"type":27,"tag":28,"props":1886,"children":1887},{},[1888],{"type":32,"value":1889},"It is what the system prevents.",{"type":27,"tag":1241,"props":1891,"children":1893},{"id":1892},"talent-cost",[1894],{"type":32,"value":1895},"Talent Cost",{"type":27,"tag":28,"props":1897,"children":1898},{},[1899,1901,1906],{"type":32,"value":1900},"Outdated systems can make it harder to hire and retain strong technical talent. Developers generally want modern tooling, healthy development practices, and systems where they can make meaningful progress. If the stack feels brittle or dated, the company may narrow its talent pool and increase retention risk. (",{"type":27,"tag":138,"props":1902,"children":1904},{"href":1828,"rel":1903},[142],[1905],{"type":32,"value":145},{"type":32,"value":147},{"type":27,"tag":28,"props":1908,"children":1909},{},[1910],{"type":32,"value":1911},"Even when the current team is excellent, institutional knowledge can become concentrated in a few people.",{"type":27,"tag":28,"props":1913,"children":1914},{},[1915],{"type":32,"value":1916},"That creates key-person risk.",{"type":27,"tag":1241,"props":1918,"children":1920},{"id":1919},"risk-cost",[1921],{"type":32,"value":1922},"Risk Cost",{"type":27,"tag":28,"props":1924,"children":1925},{},[1926],{"type":32,"value":1927},"Aging software can carry security, compliance, availability, and data integrity risks. Outdated frameworks, fragile integrations, limited automated testing, and poor observability can increase the likelihood and impact of incidents.",{"type":27,"tag":28,"props":1929,"children":1930},{},[1931],{"type":32,"value":1932},"The cost of a system failure is not just remediation.",{"type":27,"tag":28,"props":1934,"children":1935},{},[1936],{"type":32,"value":1937},"It can include lost revenue, SLA penalties, customer churn, operational disruption, audit exposure, reputational damage, and executive distraction.",{"type":27,"tag":64,"props":1939,"children":1941},{"id":1940},"technical-debt-is-a-business-discipline",[1942],{"type":32,"value":1943},"Technical Debt Is a Business Discipline",{"type":27,"tag":28,"props":1945,"children":1946},{},[1947],{"type":32,"value":1948},"Technical debt is often discussed as an engineering issue: messy code, rushed patches, outdated frameworks, or brittle architecture.",{"type":27,"tag":28,"props":1950,"children":1951},{},[1952],{"type":32,"value":1953},"But debt in software rarely lives only in the codebase.",{"type":27,"tag":28,"props":1955,"children":1956},{},[1957,1959,1965],{"type":32,"value":1958},"It also accumulates in product decisions, design shortcuts, release processes, documentation gaps, and team culture. Product debt can create bloated features that do not serve real user needs. Design debt can create fragmented workflows and adoption friction. Process debt can turn small fixes into weeks of untangling. Cultural debt can normalize short-term wins at the expense of long-term stability. (",{"type":27,"tag":138,"props":1960,"children":1963},{"href":1961,"rel":1962},"https://artandlogic.com/newsletters/tech-debt-isnt-just-technical/",[142],[1964],{"type":32,"value":145},{"type":32,"value":147},{"type":27,"tag":28,"props":1967,"children":1968},{},[1969],{"type":32,"value":1970},"That matters for CFOs because software debt behaves a lot like financial debt.",{"type":27,"tag":28,"props":1972,"children":1973},{},[1974],{"type":32,"value":1975},"Some debt is intentional and useful. A company may take a shortcut to reach the market faster, validate demand, or satisfy an urgent customer need. That can be a rational tradeoff.",{"type":27,"tag":28,"props":1977,"children":1978},{},[1979],{"type":32,"value":1980},"The problem is unmanaged debt.",{"type":27,"tag":28,"props":1982,"children":1983},{},[1984],{"type":32,"value":1985},"If the business keeps deferring repayment, the cost compounds. Teams move slower. Customer experience suffers. Support costs rise. Reporting becomes less trustworthy. Investors and stakeholders lose confidence in the company’s ability to adapt.",{"type":27,"tag":28,"props":1987,"children":1988},{},[1989],{"type":32,"value":1990},"The goal is not to eliminate all technical debt.",{"type":27,"tag":28,"props":1992,"children":1993},{},[1994],{"type":32,"value":1995},"The goal is to know which debt you are carrying, what it is costing, and when it needs to be paid down.",{"type":27,"tag":28,"props":1997,"children":1998},{},[1999],{"type":32,"value":2000},"That makes rebuilds and modernization efforts easier to evaluate. They are not abstract “technology upgrades.” They are debt management strategies.",{"type":27,"tag":64,"props":2002,"children":2004},{"id":2003},"when-a-rebuild-makes-financial-sense",[2005],{"type":32,"value":2006},"When a Rebuild Makes Financial Sense",{"type":27,"tag":28,"props":2008,"children":2009},{},[2010],{"type":32,"value":2011},"A full rebuild is not automatically wrong. In some situations, it is the responsible choice.",{"type":27,"tag":28,"props":2013,"children":2014},{},[2015],{"type":32,"value":2016},"A rebuild may make sense when the existing system no longer matches the business model, customer expectations, operational needs, or strategic direction of the company.",{"type":27,"tag":64,"props":2018,"children":2020},{"id":2019},"_1-the-current-system-cannot-support-the-future-business",[2021],{"type":32,"value":2022},"1. The Current System Cannot Support the Future Business",{"type":27,"tag":28,"props":2024,"children":2025},{},[2026],{"type":32,"value":2027},"If the company is entering new markets, changing pricing models, scaling transaction volume, adding digital services, preparing for M&A, or shifting from internal tooling to customer-facing software, the old architecture may not be fit for purpose.",{"type":27,"tag":28,"props":2029,"children":2030},{},[2031],{"type":32,"value":2032},"A system designed for one stage of the business can become a liability in the next.",{"type":27,"tag":28,"props":2034,"children":2035},{},[2036],{"type":32,"value":2037},"For example, software built for a small internal operations team may not support a high-volume self-service customer platform. A system built for one region may not support global compliance, localization, or multi-entity reporting. A product built around manual configuration may not support enterprise-scale automation.",{"type":27,"tag":28,"props":2039,"children":2040},{},[2041],{"type":32,"value":2042},"When the gap between the system’s design and the company’s strategy is too large, modernization may only delay the inevitable.",{"type":27,"tag":64,"props":2044,"children":2046},{"id":2045},"_2-incremental-fixes-keep-failing",[2047],{"type":32,"value":2048},"2. Incremental Fixes Keep Failing",{"type":27,"tag":28,"props":2050,"children":2051},{},[2052],{"type":32,"value":2053},"CFOs should be especially alert to recurring “temporary” fixes.",{"type":27,"tag":28,"props":2055,"children":2056},{},[2057],{"type":32,"value":2058},"If the company has funded multiple rounds of patches, partial rewrites, upgrades, manual workarounds, and emergency stabilization efforts without improving the overall economics of the system, it may be time to stop financing the debt and invest in a new asset.",{"type":27,"tag":28,"props":2060,"children":2061},{},[2062],{"type":32,"value":2063},"A rebuild can be justified when incremental spending no longer produces durable value.",{"type":27,"tag":64,"props":2065,"children":2067},{"id":2066},"_3-the-existing-codebase-is-too-fragile-to-change-safely",[2068],{"type":32,"value":2069},"3. The Existing Codebase Is Too Fragile to Change Safely",{"type":27,"tag":28,"props":2071,"children":2072},{},[2073],{"type":32,"value":2074},"If small changes regularly break unrelated features, estimates are unreliable, test coverage is weak, documentation is limited, and only a few people understand critical behavior, the system may be too risky to keep extending.",{"type":27,"tag":28,"props":2076,"children":2077},{},[2078],{"type":32,"value":2079},"That does not always mean the entire platform should be rebuilt.",{"type":27,"tag":28,"props":2081,"children":2082},{},[2083],{"type":32,"value":2084},"But if the company cannot safely modify a system it depends on, the business has limited control over a critical asset.",{"type":27,"tag":28,"props":2086,"children":2087},{},[2088],{"type":32,"value":2089},"That is a financial risk, not just a technical inconvenience.",{"type":27,"tag":64,"props":2091,"children":2093},{"id":2092},"_4-the-technology-stack-is-a-dead-end",[2094],{"type":32,"value":2095},"4. The Technology Stack Is a Dead End",{"type":27,"tag":28,"props":2097,"children":2098},{},[2099],{"type":32,"value":2100},"Some systems are built on languages, frameworks, libraries, or platforms that are difficult to support. Vendor support may be ending. Security patches may be unavailable. Hiring talent may be expensive. Integration options may be limited.",{"type":27,"tag":28,"props":2102,"children":2103},{},[2104],{"type":32,"value":2105},"If the stack itself is constraining the business, modernization may require so much replacement that a rebuild becomes the clearer investment.",{"type":27,"tag":64,"props":2107,"children":2109},{"id":2108},"_5-the-user-experience-needs-a-fundamental-redesign",[2110],{"type":32,"value":2111},"5. The User Experience Needs a Fundamental Redesign",{"type":27,"tag":28,"props":2113,"children":2114},{},[2115],{"type":32,"value":2116},"Sometimes the problem is not only the backend. The workflow itself may be wrong.",{"type":27,"tag":28,"props":2118,"children":2119},{},[2120],{"type":32,"value":2121},"If employees or customers rely on spreadsheets, duplicate data entry, manual approvals, offline processes, or support tickets because the software does not match how work actually happens, a rebuild may be necessary to redesign the experience around the business process.",{"type":27,"tag":28,"props":2123,"children":2124},{},[2125],{"type":32,"value":2126},"A modern interface placed on top of a flawed workflow may not deliver the operational improvement the company needs.",{"type":27,"tag":64,"props":2128,"children":2130},{"id":2129},"when-modernization-is-the-better-investment",[2131],{"type":32,"value":2132},"When Modernization Is the Better Investment",{"type":27,"tag":28,"props":2134,"children":2135},{},[2136],{"type":32,"value":2137},"Modernization is often the more financially disciplined path, especially when the existing system still contains valuable business logic and supports critical operations.",{"type":27,"tag":28,"props":2139,"children":2140},{},[2141],{"type":32,"value":2142},"A modernization strategy can reduce risk by improving the system in phases instead of replacing it all at once.",{"type":27,"tag":64,"props":2144,"children":2146},{"id":2145},"_1-the-core-business-logic-still-works",[2147],{"type":32,"value":2148},"1. The Core Business Logic Still Works",{"type":27,"tag":28,"props":2150,"children":2151},{},[2152],{"type":32,"value":2153},"Many legacy systems look outdated but contain years of valuable domain knowledge.",{"type":27,"tag":28,"props":2155,"children":2156},{},[2157],{"type":32,"value":2158},"Pricing rules, approval workflows, operational edge cases, compliance logic, reporting calculations, and customer-specific requirements may all be embedded in the software.",{"type":27,"tag":28,"props":2160,"children":2161},{},[2162],{"type":32,"value":2163},"Throwing that away can be expensive and risky.",{"type":27,"tag":28,"props":2165,"children":2166},{},[2167,2169,2174],{"type":32,"value":2168},"Modernization allows the company to preserve what works while improving the technical foundation around it. As Art+Logic has put it, the goal is not to preserve every technical decision; it is to preserve the value those decisions created. (",{"type":27,"tag":138,"props":2170,"children":2172},{"href":1757,"rel":2171},[142],[2173],{"type":32,"value":145},{"type":32,"value":147},{"type":27,"tag":64,"props":2176,"children":2178},{"id":2177},"_2-the-business-cannot-tolerate-big-bang-disruption",[2179],{"type":32,"value":2180},"2. The Business Cannot Tolerate Big-Bang Disruption",{"type":27,"tag":28,"props":2182,"children":2183},{},[2184],{"type":32,"value":2185},"A full replacement can introduce operational risk, especially if the system supports revenue, fulfillment, logistics, billing, customer service, or compliance.",{"type":27,"tag":28,"props":2187,"children":2188},{},[2189],{"type":32,"value":2190},"Modernization can be phased around business priorities. The team can improve performance, security, integrations, reporting, and user experience while the existing system continues to operate.",{"type":27,"tag":28,"props":2192,"children":2193},{},[2194],{"type":32,"value":2195},"For finance leaders, this matters because phased modernization can make spend more predictable and outcomes easier to validate.",{"type":27,"tag":64,"props":2197,"children":2199},{"id":2198},"_3-the-main-problems-are-isolated",[2200],{"type":32,"value":2201},"3. The Main Problems Are Isolated",{"type":27,"tag":28,"props":2203,"children":2204},{},[2205],{"type":32,"value":2206},"Not every legacy system is broken everywhere.",{"type":27,"tag":28,"props":2208,"children":2209},{},[2210],{"type":32,"value":2211},"The application may have a slow reporting module, an unreliable integration layer, an outdated interface, a manual deployment process, or a scaling bottleneck. If the pain is concentrated in specific areas, a targeted modernization effort may produce better ROI than a full rebuild.",{"type":27,"tag":28,"props":2213,"children":2214},{},[2215,2217,2222],{"type":32,"value":2216},"This is where “start with the pain, not the platform” becomes an important principle. Moving to the cloud or rewriting in a new framework is not inherently valuable. Solving the friction that is slowing development, operations, reporting, or customer experience is. (",{"type":27,"tag":138,"props":2218,"children":2220},{"href":1828,"rel":2219},[142],[2221],{"type":32,"value":145},{"type":32,"value":147},{"type":27,"tag":64,"props":2224,"children":2226},{"id":2225},"_4-the-company-needs-value-sooner",[2227],{"type":32,"value":2228},"4. The Company Needs Value Sooner",{"type":27,"tag":28,"props":2230,"children":2231},{},[2232],{"type":32,"value":2233},"Rebuilds often require a long investment period before the business sees a meaningful return.",{"type":27,"tag":28,"props":2235,"children":2236},{},[2237],{"type":32,"value":2238},"Modernization can produce near-term wins: faster workflows, improved reporting, reduced support burden, better performance, stronger security, easier deployments, or lower infrastructure costs.",{"type":27,"tag":28,"props":2240,"children":2241},{},[2242],{"type":32,"value":2243},"That matters when budgets are tight, when the business needs evidence before approving a larger transformation, or when leadership wants to reduce risk through measurable checkpoints.",{"type":27,"tag":64,"props":2245,"children":2247},{"id":2246},"_5-the-existing-system-can-be-gradually-untangled",[2248],{"type":32,"value":2249},"5. The Existing System Can Be Gradually Untangled",{"type":27,"tag":28,"props":2251,"children":2252},{},[2253],{"type":32,"value":2254},"Some legacy systems can be improved through a phased approach: isolate high-friction modules, build modern replacements alongside the current system, shift workloads gradually, and retire old components as the replacement proves itself.",{"type":27,"tag":28,"props":2256,"children":2257},{},[2258,2260,2265],{"type":32,"value":2259},"Art+Logic has described this as decoupling rather than demolishing. Many legacy systems can be modernized one piece at a time, especially when the team creates parallel paths that let the current system keep running while modern capabilities gradually take over. (",{"type":27,"tag":138,"props":2261,"children":2263},{"href":1828,"rel":2262},[142],[2264],{"type":32,"value":145},{"type":32,"value":147},{"type":27,"tag":28,"props":2267,"children":2268},{},[2269],{"type":32,"value":2270},"This can combine the strategic benefits of replacement with the financial control of staged investment.",{"type":27,"tag":64,"props":2272,"children":2274},{"id":2273},"the-cfos-evaluation-framework",[2275],{"type":32,"value":2276},"The CFO’s Evaluation Framework",{"type":27,"tag":28,"props":2278,"children":2279},{},[2280],{"type":32,"value":2281},"The rebuild-versus-modernize decision should be made through business, financial, and technical analysis.",{"type":27,"tag":28,"props":2283,"children":2284},{},[2285],{"type":32,"value":2286},"Here are the questions CFOs should ask before approving either path.",{"type":27,"tag":64,"props":2288,"children":2290},{"id":2289},"_1-what-business-outcome-are-we-buying",[2291],{"type":32,"value":2292},"1. What Business Outcome Are We Buying?",{"type":27,"tag":28,"props":2294,"children":2295},{},[2296],{"type":32,"value":2297},"Do not begin with the architecture; instead, begin with the business result.",{"type":27,"tag":28,"props":2299,"children":2300},{},[2301],{"type":32,"value":2302},"Are you trying to reduce operating costs? Increase engineering velocity? Improve customer retention? Launch a new product line? Reduce cybersecurity risk? Improve reporting and forecasting? Support more transaction volume? Eliminate manual work? Improve compliance? Prepare for acquisition, investment, or audit?",{"type":27,"tag":28,"props":2304,"children":2305},{},[2306],{"type":32,"value":2307},"A rebuild or modernization effort should be tied to specific outcomes. Without that clarity, the project can become a broad technical improvement program with unclear ROI.",{"type":27,"tag":28,"props":2309,"children":2310},{},[2311],{"type":32,"value":2312},"A useful test is whether the investment can be explained in business language:",{"type":27,"tag":28,"props":2314,"children":2315},{},[2316],{"type":32,"value":2317},"“We are modernizing this platform so we can reduce manual order processing.”",{"type":27,"tag":28,"props":2319,"children":2320},{},[2321],{"type":32,"value":2322},"“We are replacing this architecture because it cannot support the transaction volume required for our growth plan.”",{"type":27,"tag":28,"props":2324,"children":2325},{},[2326],{"type":32,"value":2327},"“We are improving deployment and testing so product teams can release safely and more often.”",{"type":27,"tag":28,"props":2329,"children":2330},{},[2331],{"type":32,"value":2332},"The more specific the outcome, the easier it is to evaluate the right path.",{"type":27,"tag":64,"props":2334,"children":2336},{"id":2335},"_2-what-is-the-true-cost-of-the-current-system",[2337],{"type":32,"value":2338},"2. What Is the True Cost of the Current System?",{"type":27,"tag":28,"props":2340,"children":2341},{},[2342],{"type":32,"value":2343},"CFOs should look beyond hosting bills and engineering headcount.",{"type":27,"tag":28,"props":2345,"children":2346},{},[2347],{"type":32,"value":2348},"The total cost of ownership may include maintenance labor, incident response, downtime, manual operations, customer support volume, delayed revenue initiatives, compliance gaps, security remediation, vendor fees, data reconciliation, reporting inefficiencies, onboarding time, and recruiting challenges.",{"type":27,"tag":28,"props":2350,"children":2351},{},[2352],{"type":32,"value":2353},"A legacy platform may appear inexpensive because many costs are scattered across departments.",{"type":27,"tag":28,"props":2355,"children":2356},{},[2357],{"type":32,"value":2358},"Pulling those costs together often changes the investment conversation.",{"type":27,"tag":64,"props":2360,"children":2362},{"id":2361},"_3-what-risks-are-we-carrying-today",[2363],{"type":32,"value":2364},"3. What Risks Are We Carrying Today?",{"type":27,"tag":28,"props":2366,"children":2367},{},[2368],{"type":32,"value":2369},"Modernization and rebuild projects carry delivery risk.",{"type":27,"tag":28,"props":2371,"children":2372},{},[2373],{"type":32,"value":2374},"But doing nothing also carries risk.",{"type":27,"tag":28,"props":2376,"children":2377},{},[2378],{"type":32,"value":2379},"CFOs should ask:",{"type":27,"tag":92,"props":2381,"children":2382},{},[2383,2388,2393,2398,2403,2408,2413],{"type":27,"tag":96,"props":2384,"children":2385},{},[2386],{"type":32,"value":2387},"What happens if a key developer leaves?",{"type":27,"tag":96,"props":2389,"children":2390},{},[2391],{"type":32,"value":2392},"What happens if transaction volume doubles?",{"type":27,"tag":96,"props":2394,"children":2395},{},[2396],{"type":32,"value":2397},"What happens if a vendor discontinues support?",{"type":27,"tag":96,"props":2399,"children":2400},{},[2401],{"type":32,"value":2402},"What happens if a major customer requests an integration we cannot support?",{"type":27,"tag":96,"props":2404,"children":2405},{},[2406],{"type":32,"value":2407},"What happens if we need to pass a stricter security review?",{"type":27,"tag":96,"props":2409,"children":2410},{},[2411],{"type":32,"value":2412},"What happens if the system goes down during a peak period?",{"type":27,"tag":96,"props":2414,"children":2415},{},[2416],{"type":32,"value":2417},"What happens if reporting remains unreliable?",{"type":27,"tag":28,"props":2419,"children":2420},{},[2421],{"type":32,"value":2422},"The decision should compare the risk of change against the risk of inaction.",{"type":27,"tag":64,"props":2424,"children":2426},{"id":2425},"_4-can-we-fund-this-in-stages",[2427],{"type":32,"value":2428},"4. Can We Fund This in Stages?",{"type":27,"tag":28,"props":2430,"children":2431},{},[2432],{"type":32,"value":2433},"Large software projects become more manageable when they are broken into funded phases with measurable checkpoints.",{"type":27,"tag":28,"props":2435,"children":2436},{},[2437],{"type":32,"value":2438},"Rather than approving an open-ended rebuild, CFOs can ask for a staged plan:",{"type":27,"tag":2440,"props":2441,"children":2442},"ol",{},[2443,2448,2453,2458,2463],{"type":27,"tag":96,"props":2444,"children":2445},{},[2446],{"type":32,"value":2447},"Assessment and discovery",{"type":27,"tag":96,"props":2449,"children":2450},{},[2451],{"type":32,"value":2452},"Architecture and roadmap",{"type":27,"tag":96,"props":2454,"children":2455},{},[2456],{"type":32,"value":2457},"Highest-risk component replacement",{"type":27,"tag":96,"props":2459,"children":2460},{},[2461],{"type":32,"value":2462},"First measurable business outcome",{"type":27,"tag":96,"props":2464,"children":2465},{},[2466],{"type":32,"value":2467},"Expansion based on validated results",{"type":27,"tag":28,"props":2469,"children":2470},{},[2471],{"type":32,"value":2472},"This structure helps avoid the common trap of committing to a large technical vision before the business has evidence that the approach works.",{"type":27,"tag":28,"props":2474,"children":2475},{},[2476],{"type":32,"value":2477},"It also creates opportunities to stop, adjust, or accelerate based on results.",{"type":27,"tag":64,"props":2479,"children":2481},{"id":2480},"_5-what-should-we-not-rebuild",[2482],{"type":32,"value":2483},"5. What Should We Not Rebuild?",{"type":27,"tag":28,"props":2485,"children":2486},{},[2487],{"type":32,"value":2488},"One of the biggest mistakes in software replacement projects is assuming the new system must recreate every feature in the old system.",{"type":27,"tag":28,"props":2490,"children":2491},{},[2492],{"type":32,"value":2493},"Legacy software often contains features that are unused, redundant, confusing, or tied to outdated processes. Rebuilding everything can waste budget and preserve complexity.",{"type":27,"tag":28,"props":2495,"children":2496},{},[2497],{"type":32,"value":2498},"Before approving a rebuild, CFOs should insist on a serious feature and workflow review.",{"type":27,"tag":28,"props":2500,"children":2501},{},[2502],{"type":32,"value":2503},"The goal is not to copy the old system.",{"type":27,"tag":28,"props":2505,"children":2506},{},[2507],{"type":32,"value":2508},"The goal is to build the system the business actually needs now.",{"type":27,"tag":64,"props":2510,"children":2512},{"id":2511},"_6-how-will-we-measure-roi",[2513],{"type":32,"value":2514},"6. How Will We Measure ROI?",{"type":27,"tag":28,"props":2516,"children":2517},{},[2518],{"type":32,"value":2519},"Software ROI is not always immediate, but it should be measurable.",{"type":27,"tag":28,"props":2521,"children":2522},{},[2523],{"type":32,"value":2524},"Potential metrics include lower maintenance spend, reduced manual labor, faster release cycles, fewer incidents, lower support volume, faster onboarding, improved conversion, higher retention, increased transaction capacity, reduced infrastructure cost, better reporting accuracy, shorter cycle times, improved customer satisfaction, and reduced compliance exposure.",{"type":27,"tag":28,"props":2526,"children":2527},{},[2528],{"type":32,"value":2529},"The right metrics depend on the system.",{"type":27,"tag":28,"props":2531,"children":2532},{},[2533],{"type":32,"value":2534},"An internal operations platform may justify investment through labor savings and process efficiency. A customer-facing product may justify investment through retention, expansion revenue, and faster feature delivery.",{"type":27,"tag":28,"props":2536,"children":2537},{},[2538],{"type":32,"value":2539},"The important point is to define success before the work begins.",{"type":27,"tag":64,"props":2541,"children":2543},{"id":2542},"the-common-failure-mode-rebuilding-without-reducing-complexity",[2544],{"type":32,"value":2545},"The Common Failure Mode: Rebuilding Without Reducing Complexity",{"type":27,"tag":28,"props":2547,"children":2548},{},[2549],{"type":32,"value":2550},"A software rebuild can fail even when the new technology is better.",{"type":27,"tag":28,"props":2552,"children":2553},{},[2554],{"type":32,"value":2555},"That usually happens when the project recreates old complexity instead of solving it.",{"type":27,"tag":28,"props":2557,"children":2558},{},[2559],{"type":32,"value":2560},"The team copies every screen, every field, every exception, every report, every workflow, and every edge case into a new system. The result is a more expensive version of the same problem.",{"type":27,"tag":28,"props":2562,"children":2563},{},[2564],{"type":32,"value":2565},"For CFOs, this is a governance issue.",{"type":27,"tag":28,"props":2567,"children":2568},{},[2569],{"type":32,"value":2570},"A rebuild should not be treated as a technical translation exercise. It should be treated as a business redesign opportunity.",{"type":27,"tag":28,"props":2572,"children":2573},{},[2574],{"type":32,"value":2575},"Which workflows can be simplified? Which approvals can be automated? Which reports are no longer useful? Which integrations can be standardized? Which customer exceptions are actually margin-eroding customizations?",{"type":27,"tag":28,"props":2577,"children":2578},{},[2579],{"type":32,"value":2580},"The value of a rebuild comes from improving how the business operates, not just changing the code.",{"type":27,"tag":64,"props":2582,"children":2584},{"id":2583},"the-other-failure-mode-modernizing-without-a-strategy",[2585],{"type":32,"value":2586},"The Other Failure Mode: Modernizing Without a Strategy",{"type":27,"tag":28,"props":2588,"children":2589},{},[2590],{"type":32,"value":2591},"Modernization can also fail when it becomes a series of disconnected technical upgrades.",{"type":27,"tag":28,"props":2593,"children":2594},{},[2595],{"type":32,"value":2596},"A team updates a framework, moves hosting environments, rewrites a few services, improves deployment pipelines, and cleans up code. Each activity may be reasonable, but the business impact is unclear.",{"type":27,"tag":28,"props":2598,"children":2599},{},[2600],{"type":32,"value":2601},"The result is modernization activity without financial momentum.",{"type":27,"tag":28,"props":2603,"children":2604},{},[2605],{"type":32,"value":2606},"A strong modernization roadmap should connect technical work to business outcomes.",{"type":27,"tag":28,"props":2608,"children":2609},{},[2610],{"type":32,"value":2611},"API work should support integrations, partnerships, automation, or customer self-service. Cloud migration should support scalability, resilience, cost visibility, or deployment speed. Refactoring should reduce change failure rates, maintenance cost, or release bottlenecks. Data modernization should improve reporting, forecasting, compliance, or operational decision-making. UX improvements should reduce training time, support volume, or task completion time.",{"type":27,"tag":28,"props":2613,"children":2614},{},[2615],{"type":32,"value":2616},"Modernization is most valuable when every technical improvement has a business reason behind it.",{"type":27,"tag":64,"props":2618,"children":2620},{"id":2619},"a-practical-decision-matrix-for-cfos",[2621],{"type":32,"value":2622},"A Practical Decision Matrix for CFOs",{"type":27,"tag":28,"props":2624,"children":2625},{},[2626],{"type":32,"value":2627},"Consider rebuilding when:",{"type":27,"tag":92,"props":2629,"children":2630},{},[2631,2636,2641,2646,2651,2656,2661],{"type":27,"tag":96,"props":2632,"children":2633},{},[2634],{"type":32,"value":2635},"The current system cannot support the future business model.",{"type":27,"tag":96,"props":2637,"children":2638},{},[2639],{"type":32,"value":2640},"The architecture is fundamentally misaligned with strategic goals.",{"type":27,"tag":96,"props":2642,"children":2643},{},[2644],{"type":32,"value":2645},"The codebase is too fragile or poorly understood to change safely.",{"type":27,"tag":96,"props":2647,"children":2648},{},[2649],{"type":32,"value":2650},"The technology stack is obsolete or difficult to staff.",{"type":27,"tag":96,"props":2652,"children":2653},{},[2654],{"type":32,"value":2655},"The user experience requires a fundamental workflow redesign.",{"type":27,"tag":96,"props":2657,"children":2658},{},[2659],{"type":32,"value":2660},"Incremental fixes have repeatedly failed to improve the economics.",{"type":27,"tag":96,"props":2662,"children":2663},{},[2664],{"type":32,"value":2665},"The cost of preserving the old system is higher than that of replacing it.",{"type":27,"tag":28,"props":2667,"children":2668},{},[2669],{"type":32,"value":2670},"Consider modernizing when:",{"type":27,"tag":92,"props":2672,"children":2673},{},[2674,2679,2684,2689,2694,2699,2704],{"type":27,"tag":96,"props":2675,"children":2676},{},[2677],{"type":32,"value":2678},"The system still contains valuable business logic.",{"type":27,"tag":96,"props":2680,"children":2681},{},[2682],{"type":32,"value":2683},"The main problems are specific and addressable.",{"type":27,"tag":96,"props":2685,"children":2686},{},[2687],{"type":32,"value":2688},"The business needs continuity during improvement.",{"type":27,"tag":96,"props":2690,"children":2691},{},[2692],{"type":32,"value":2693},"You need to reduce risk through phased delivery.",{"type":27,"tag":96,"props":2695,"children":2696},{},[2697],{"type":32,"value":2698},"The platform can be gradually refactored or decomposed.",{"type":27,"tag":96,"props":2700,"children":2701},{},[2702],{"type":32,"value":2703},"Near-term ROI matters.",{"type":27,"tag":96,"props":2705,"children":2706},{},[2707],{"type":32,"value":2708},"The organization is not ready for full replacement.",{"type":27,"tag":28,"props":2710,"children":2711},{},[2712],{"type":32,"value":2713},"Consider a hybrid approach when:",{"type":27,"tag":92,"props":2715,"children":2716},{},[2717,2722,2727,2732,2737],{"type":27,"tag":96,"props":2718,"children":2719},{},[2720],{"type":32,"value":2721},"Some components are salvageable, and others are not.",{"type":27,"tag":96,"props":2723,"children":2724},{},[2725],{"type":32,"value":2726},"The business needs both continuity and strategic change.",{"type":27,"tag":96,"props":2728,"children":2729},{},[2730],{"type":32,"value":2731},"You can replace high-risk areas first while preserving stable functions.",{"type":27,"tag":96,"props":2733,"children":2734},{},[2735],{"type":32,"value":2736},"A phased roadmap can deliver measurable value before full replacement.",{"type":27,"tag":96,"props":2738,"children":2739},{},[2740],{"type":32,"value":2741},"The system is too important for a big-bang cutover.",{"type":27,"tag":28,"props":2743,"children":2744},{},[2745],{"type":32,"value":2746},"In many cases, the hybrid path is the most financially responsible option.",{"type":27,"tag":64,"props":2748,"children":2750},{"id":2749},"why-an-independent-technical-assessment-helps",[2751],{"type":32,"value":2752},"Why an Independent Technical Assessment Helps",{"type":27,"tag":28,"props":2754,"children":2755},{},[2756],{"type":32,"value":2757},"Finance leaders do not need to become software architects.",{"type":27,"tag":28,"props":2759,"children":2760},{},[2761],{"type":32,"value":2762},"But they do need enough objective information to make a sound investment decision.",{"type":27,"tag":28,"props":2764,"children":2765},{},[2766],{"type":32,"value":2767},"An independent technical assessment can help answer:",{"type":27,"tag":92,"props":2769,"children":2770},{},[2771,2776,2781,2786,2791,2796,2801,2806],{"type":27,"tag":96,"props":2772,"children":2773},{},[2774],{"type":32,"value":2775},"What is the current state of the system?",{"type":27,"tag":96,"props":2777,"children":2778},{},[2779],{"type":32,"value":2780},"Where are the highest costs and risks?",{"type":27,"tag":96,"props":2782,"children":2783},{},[2784],{"type":32,"value":2785},"Which parts are worth preserving?",{"type":27,"tag":96,"props":2787,"children":2788},{},[2789],{"type":32,"value":2790},"Which parts should be replaced?",{"type":27,"tag":96,"props":2792,"children":2793},{},[2794],{"type":32,"value":2795},"What are the realistic options?",{"type":27,"tag":96,"props":2797,"children":2798},{},[2799],{"type":32,"value":2800},"What are the tradeoffs in cost, timeline, risk, and business impact?",{"type":27,"tag":96,"props":2802,"children":2803},{},[2804],{"type":32,"value":2805},"What should be done first?",{"type":27,"tag":96,"props":2807,"children":2808},{},[2809],{"type":32,"value":2810},"What outcomes can be measured?",{"type":27,"tag":28,"props":2812,"children":2813},{},[2814],{"type":32,"value":2815},"This step is especially valuable when internal stakeholders disagree.",{"type":27,"tag":28,"props":2817,"children":2818},{},[2819],{"type":32,"value":2820},"Engineers may see the pain of the current system every day. Business teams may fear disruption. Executives may want speed. Finance may need predictability. An assessment creates a shared fact base for the decision.",{"type":27,"tag":64,"props":2822,"children":2824},{"id":2823},"the-best-answer-is-often-sequenced-not-binary",[2825],{"type":32,"value":2826},"The Best Answer Is Often Sequenced, Not Binary",{"type":27,"tag":28,"props":2828,"children":2829},{},[2830],{"type":32,"value":2831},"The rebuild-versus-modernize debate is often framed as an either/or decision.",{"type":27,"tag":28,"props":2833,"children":2834},{},[2835],{"type":32,"value":2836},"In reality, the best strategy may be sequenced.",{"type":27,"tag":28,"props":2838,"children":2839},{},[2840],{"type":32,"value":2841},"Start by understanding what the current system actually does. Identify the highest-cost and highest-risk areas. Stabilize what needs to keep running. Improve visibility, security, deployment processes, and test coverage. Replace high-friction workflows one at a time. Build new capabilities around the legacy core. Migrate users gradually. Retire old components when the replacement has proven itself.",{"type":27,"tag":28,"props":2843,"children":2844},{},[2845],{"type":32,"value":2846},"This kind of phased approach gives CFOs more control.",{"type":27,"tag":28,"props":2848,"children":2849},{},[2850],{"type":32,"value":2851},"It reduces the risk of a large sunk-cost project. It creates measurable checkpoints. It allows the business to learn as it invests. And it can deliver value before the entire transformation is complete.",{"type":27,"tag":28,"props":2853,"children":2854},{},[2855,2857,2862],{"type":32,"value":2856},"Modernization is not about replacing the past for its own sake. It is about creating a foundation that can support the future. (",{"type":27,"tag":138,"props":2858,"children":2860},{"href":1757,"rel":2859},[142],[2861],{"type":32,"value":145},{"type":32,"value":147},{"type":27,"tag":64,"props":2864,"children":2866},{"id":2865},"final-takeaway-dont-pay-twice-for-the-same-complexity",[2867],{"type":32,"value":2868},"Final Takeaway: Don’t Pay Twice for the Same Complexity",{"type":27,"tag":28,"props":2870,"children":2871},{},[2872],{"type":32,"value":2873},"Rebuilding and modernizing software can both be smart investments.",{"type":27,"tag":28,"props":2875,"children":2876},{},[2877],{"type":32,"value":2878},"They can also both waste money if the business case is vague.",{"type":27,"tag":28,"props":2880,"children":2881},{},[2882],{"type":32,"value":2883},"A rebuild is justified when the current system cannot support where the company is going. Modernization is often better when the existing system still has value and the business needs a lower-risk path to improvement. A hybrid approach may offer the best balance: preserve what works, replace what limits growth, and fund the work in stages.",{"type":27,"tag":28,"props":2885,"children":2886},{},[2887],{"type":32,"value":2888},"For CFOs, the decision should come down to this:",{"type":27,"tag":28,"props":2890,"children":2891},{},[2892],{"type":27,"tag":339,"props":2893,"children":2894},{},[2895],{"type":32,"value":2896},"Which path gives the company the strongest future capability for the lowest acceptable risk?",{"type":27,"tag":28,"props":2898,"children":2899},{},[2900],{"type":32,"value":2901},"The answer requires technical insight, but it should be evaluated through financial discipline.",{"type":27,"tag":28,"props":2903,"children":2904},{},[2905],{"type":32,"value":2906},"The goal is not to own newer software.",{"type":27,"tag":28,"props":2908,"children":2909},{},[2910],{"type":32,"value":2911},"The goal is to invest in a platform that helps the business move faster, operate with less friction, reduce risk, and create durable value.",{"type":27,"tag":2913,"props":2914,"children":2915},"hr",{},[],{"type":27,"tag":64,"props":2917,"children":2918},{"id":1484},[2919],{"type":32,"value":1487},{"type":27,"tag":1241,"props":2921,"children":2923},{"id":2922},"what-is-the-difference-between-rebuilding-and-modernizing-software",[2924],{"type":32,"value":2925},"What is the difference between rebuilding and modernizing software?",{"type":27,"tag":28,"props":2927,"children":2928},{},[2929],{"type":32,"value":2930},"Rebuilding software means replacing an existing system with a new one, usually built from the ground up. Modernizing software means improving the existing system through targeted updates such as refactoring, cloud migration, security improvements, new integrations, observability, or user experience enhancements.",{"type":27,"tag":1241,"props":2932,"children":2934},{"id":2933},"is-it-cheaper-to-modernize-software-than-to-rebuild-it",[2935],{"type":32,"value":2936},"Is it cheaper to modernize software than to rebuild it?",{"type":27,"tag":28,"props":2938,"children":2939},{},[2940],{"type":32,"value":2941},"Modernization is often less expensive upfront because it can be done in phases and may preserve valuable parts of the existing system. However, if the current architecture is fundamentally flawed or no longer supports the business model, repeated modernization efforts can become more expensive than rebuilding.",{"type":27,"tag":1241,"props":2943,"children":2945},{"id":2944},"when-should-a-company-rebuild-legacy-software",[2946],{"type":32,"value":2947},"When should a company rebuild legacy software?",{"type":27,"tag":28,"props":2949,"children":2950},{},[2951],{"type":32,"value":2952},"A rebuild may make sense when the existing system cannot support future growth, relies on obsolete technology, creates significant operational risk, or requires so many fixes that replacement becomes the more financially responsible option.",{"type":27,"tag":1241,"props":2954,"children":2956},{"id":2955},"when-is-software-modernization-the-better-choice",[2957],{"type":32,"value":2958},"When is software modernization the better choice?",{"type":27,"tag":28,"props":2960,"children":2961},{},[2962],{"type":32,"value":2963},"Modernization is usually better when the core system still works, contains valuable business logic, and can be improved incrementally. It is also a good option when the business needs continuity and wants to reduce delivery risk through phased investment.",{"type":27,"tag":1241,"props":2965,"children":2967},{"id":2966},"what-should-cfos-evaluate-before-approving-a-software-rebuild",[2968],{"type":32,"value":2969},"What should CFOs evaluate before approving a software rebuild?",{"type":27,"tag":28,"props":2971,"children":2972},{},[2973],{"type":32,"value":2974},"CFOs should evaluate the total cost of ownership, current system risks, business outcomes, delivery timeline, data migration complexity, change management needs, and measurable ROI. They should also ask whether the project is simplifying business complexity or simply recreating it in a new system.",{"type":27,"tag":1241,"props":2976,"children":2978},{"id":2977},"can-a-company-rebuild-and-modernize-at-the-same-time",[2979],{"type":32,"value":2980},"Can a company rebuild and modernize at the same time?",{"type":27,"tag":28,"props":2982,"children":2983},{},[2984],{"type":32,"value":2985},"Yes. Many successful projects use a hybrid strategy. The company may modernize stable parts of the system while rebuilding high-risk or high-value components. This can reduce disruption while still moving the business toward a better long-term architecture.",{"type":27,"tag":28,"props":2987,"children":2988},{},[2989],{"type":32,"value":2990},"This version now has a clearer connection to the earlier Art+Logic newsletter content while still standing on its own as a CFO-focused blog post.",{"title":8,"searchDepth":1575,"depth":1575,"links":2992},[2993,2994,2995,3001,3002,3003,3004,3005,3006,3007,3008,3009,3010,3011,3012,3013,3014,3015,3016,3017,3018,3019,3020,3021,3022,3023,3024,3025,3026,3027],{"id":1672,"depth":1575,"text":1675},{"id":1736,"depth":1575,"text":1739},{"id":1795,"depth":1575,"text":1798,"children":2996},[2997,2998,2999,3000],{"id":1840,"depth":1591,"text":1843},{"id":1861,"depth":1591,"text":1864},{"id":1892,"depth":1591,"text":1895},{"id":1919,"depth":1591,"text":1922},{"id":1940,"depth":1575,"text":1943},{"id":2003,"depth":1575,"text":2006},{"id":2019,"depth":1575,"text":2022},{"id":2045,"depth":1575,"text":2048},{"id":2066,"depth":1575,"text":2069},{"id":2092,"depth":1575,"text":2095},{"id":2108,"depth":1575,"text":2111},{"id":2129,"depth":1575,"text":2132},{"id":2145,"depth":1575,"text":2148},{"id":2177,"depth":1575,"text":2180},{"id":2198,"depth":1575,"text":2201},{"id":2225,"depth":1575,"text":2228},{"id":2246,"depth":1575,"text":2249},{"id":2273,"depth":1575,"text":2276},{"id":2289,"depth":1575,"text":2292},{"id":2335,"depth":1575,"text":2338},{"id":2361,"depth":1575,"text":2364},{"id":2425,"depth":1575,"text":2428},{"id":2480,"depth":1575,"text":2483},{"id":2511,"depth":1575,"text":2514},{"id":2542,"depth":1575,"text":2545},{"id":2583,"depth":1575,"text":2586},{"id":2619,"depth":1575,"text":2622},{"id":2749,"depth":1575,"text":2752},{"id":2823,"depth":1575,"text":2826},{"id":2865,"depth":1575,"text":2868},{"id":1484,"depth":1575,"text":1487,"children":3028},[3029,3030,3031,3032,3033,3034],{"id":2922,"depth":1591,"text":2925},{"id":2933,"depth":1591,"text":2936},{"id":2944,"depth":1591,"text":2947},{"id":2955,"depth":1591,"text":2958},{"id":2966,"depth":1591,"text":2969},{"id":2977,"depth":1591,"text":2980},"content:cperez:2026-07-16:rebuild-vs-modernize-software-cfo-guide.md","cperez/2026-07-16/rebuild-vs-modernize-software-cfo-guide.md","cperez/2026-07-16/rebuild-vs-modernize-software-cfo-guide",1784782372652]