<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Santeware | Engineering Healthcare Data</title>
	<atom:link href="https://santeware.com/feed/" rel="self" type="application/rss+xml" />
	<link>https://santeware.com</link>
	<description>&#124; Meeting Requirements &#124; Exceeding Expectations</description>
	<lastBuildDate>Wed, 01 Apr 2026 08:30:32 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://santeware.com/wp-content/uploads/2021/02/fav_icon.png</url>
	<title>Santeware | Engineering Healthcare Data</title>
	<link>https://santeware.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>AI Architecture in Healthcare: Vector Database vs SQL, REST vs gRPC, and System Design Choices That Scale</title>
		<link>https://santeware.com/ai-architecture-in-healthcare-vector-database-vs-sql-rest-vs-grpc-and-system-design-choices-that-scale/</link>
					<comments>https://santeware.com/ai-architecture-in-healthcare-vector-database-vs-sql-rest-vs-grpc-and-system-design-choices-that-scale/#respond</comments>
		
		<dc:creator><![CDATA[superadmin]]></dc:creator>
		<pubDate>Thu, 05 Mar 2026 06:55:56 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[#AIHealthcare]]></category>
		<category><![CDATA[#BackendEngineering]]></category>
		<category><![CDATA[#DataEngineering]]></category>
		<category><![CDATA[#DigitalHealth]]></category>
		<category><![CDATA[#HealthcareInnovation]]></category>
		<category><![CDATA[#MachineLearning]]></category>
		<category><![CDATA[#ScalableSystems]]></category>
		<category><![CDATA[#SoftwareArchitecture]]></category>
		<category><![CDATA[#SystemDesign]]></category>
		<category><![CDATA[AI Architecture Healthcare]]></category>
		<category><![CDATA[AI in Healthcare]]></category>
		<category><![CDATA[AI Pipelines]]></category>
		<category><![CDATA[AI System Design]]></category>
		<category><![CDATA[API Architecture]]></category>
		<category><![CDATA[Backend Engineering]]></category>
		<category><![CDATA[Clinical Data Systems]]></category>
		<category><![CDATA[Data Architecture]]></category>
		<category><![CDATA[Digital Health]]></category>
		<category><![CDATA[Distributed Systems]]></category>
		<category><![CDATA[EHR Architecture]]></category>
		<category><![CDATA[Embeddings]]></category>
		<category><![CDATA[EMR Systems]]></category>
		<category><![CDATA[FHIR Standards]]></category>
		<category><![CDATA[Future of Healthcare]]></category>
		<category><![CDATA[gRPC]]></category>
		<category><![CDATA[Healthcare AI Systems]]></category>
		<category><![CDATA[Healthcare Data Platforms]]></category>
		<category><![CDATA[Healthcare Innovation]]></category>
		<category><![CDATA[Healthcare Technology]]></category>
		<category><![CDATA[HealthTech]]></category>
		<category><![CDATA[HealthTech Engineering]]></category>
		<category><![CDATA[HealthTech Startups]]></category>
		<category><![CDATA[High Performance Systems]]></category>
		<category><![CDATA[HL7 Integration]]></category>
		<category><![CDATA[Low Latency Systems]]></category>
		<category><![CDATA[Machine Learning Infrastructure]]></category>
		<category><![CDATA[Medical Data Engineering]]></category>
		<category><![CDATA[Microservices]]></category>
		<category><![CDATA[Modular Monolith]]></category>
		<category><![CDATA[REST API]]></category>
		<category><![CDATA[Retrieval Systems]]></category>
		<category><![CDATA[Scalable Systems]]></category>
		<category><![CDATA[Semantic Search]]></category>
		<category><![CDATA[Software Architecture]]></category>
		<category><![CDATA[SQL vs Vector Database]]></category>
		<category><![CDATA[System Design]]></category>
		<category><![CDATA[Unstructured Data]]></category>
		<category><![CDATA[Vector Database]]></category>
		<guid isPermaLink="false">https://santeware.com/?p=21466</guid>

					<description><![CDATA[Introduction Most healthcare systems were not designed for AI. They were built for structured data, predictable workflows, and stable interfaces. For years, architectural decisions—databases, APIs, and system design—remained unchanged once implemented. That assumption is now invalid. At Santeware Healthcare Solutions, we are seeing a clear shift: AI architecture in healthcare systems is evolving faster than [&#8230;]]]></description>
		
					<wfw:commentRss>https://santeware.com/ai-architecture-in-healthcare-vector-database-vs-sql-rest-vs-grpc-and-system-design-choices-that-scale/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Designing an AI Assistant Inside the EMR to Reduce Clinical Documentation Burden</title>
		<link>https://santeware.com/ai-assistant/</link>
					<comments>https://santeware.com/ai-assistant/#respond</comments>
		
		<dc:creator><![CDATA[superadmin]]></dc:creator>
		<pubDate>Thu, 05 Feb 2026 06:10:01 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[AI Assistant in EMR]]></category>
		<category><![CDATA[AI Clinical Assistant]]></category>
		<category><![CDATA[AI for Medical Documentation]]></category>
		<category><![CDATA[AI in Clinical Systems]]></category>
		<category><![CDATA[AI in Healthcare EMR]]></category>
		<category><![CDATA[AI-Powered EMR]]></category>
		<category><![CDATA[Clinical Automation Tools]]></category>
		<category><![CDATA[Clinical Documentation Automation]]></category>
		<category><![CDATA[Clinical Documentation Burden]]></category>
		<category><![CDATA[Clinical Productivity AI]]></category>
		<category><![CDATA[Digital Health AI]]></category>
		<category><![CDATA[EMR AI Integration]]></category>
		<category><![CDATA[EMR Embedded AI Assistant]]></category>
		<category><![CDATA[EMR Workflow Automation]]></category>
		<category><![CDATA[EMR Workflow Optimization]]></category>
		<category><![CDATA[GPT in Healthcare]]></category>
		<category><![CDATA[Healthcare AI Solutions]]></category>
		<category><![CDATA[Healthcare IT Modernization]]></category>
		<category><![CDATA[Healthcare System Integration]]></category>
		<category><![CDATA[Healthcare Workflow Automation]]></category>
		<category><![CDATA[HIPAA Compliant AI]]></category>
		<category><![CDATA[Human-in-the-Loop AI Healthcare]]></category>
		<category><![CDATA[Intelligent EMR Integration]]></category>
		<category><![CDATA[Medical AI Implementation]]></category>
		<category><![CDATA[SOAP Note Automation]]></category>
		<guid isPermaLink="false">https://santeware.com/?p=19020</guid>

					<description><![CDATA[Introduction Most healthcare organizations recognize the promise of AI in clinical workflows. But very few manage to operationalize it in a way that actually reduces clinician workload without creating new systems, new screens, or new cognitive overhead. At Santeware Healthcare Solutions, we were engaged by a healthcare organization to explore a practical use of AI: [&#8230;]]]></description>
		
					<wfw:commentRss>https://santeware.com/ai-assistant/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Building a Scalable Quality Assurance Unit for Complex Healthcare IT Project Delivery — Without Buying New Tools</title>
		<link>https://santeware.com/building-a-scalable-quality-assurance-unit-for-complex-healthcare-it-project-delivery-without-buying-new-tools/</link>
					<comments>https://santeware.com/building-a-scalable-quality-assurance-unit-for-complex-healthcare-it-project-delivery-without-buying-new-tools/#respond</comments>
		
		<dc:creator><![CDATA[superadmin]]></dc:creator>
		<pubDate>Mon, 05 Jan 2026 02:43:17 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Analytics Engineering]]></category>
		<category><![CDATA[Clinical Systems]]></category>
		<category><![CDATA[Compliance Driven Development]]></category>
		<category><![CDATA[Cost Efficient IT]]></category>
		<category><![CDATA[Data Migration]]></category>
		<category><![CDATA[Delivery Governance]]></category>
		<category><![CDATA[DevOps]]></category>
		<category><![CDATA[DevOps Culture]]></category>
		<category><![CDATA[EHR Systems]]></category>
		<category><![CDATA[EMR integration]]></category>
		<category><![CDATA[Engineering Excellence]]></category>
		<category><![CDATA[Enterprise Software]]></category>
		<category><![CDATA[FHIR]]></category>
		<category><![CDATA[Healthcare Data]]></category>
		<category><![CDATA[Healthcare IT]]></category>
		<category><![CDATA[Healthcare Software]]></category>
		<category><![CDATA[HealthTech]]></category>
		<category><![CDATA[HIPAA Compliance]]></category>
		<category><![CDATA[HL7]]></category>
		<category><![CDATA[IT Project Management]]></category>
		<category><![CDATA[Open Source Tools]]></category>
		<category><![CDATA[Operational Excellence]]></category>
		<category><![CDATA[Process Architecture]]></category>
		<category><![CDATA[QA Automation]]></category>
		<category><![CDATA[Quality Assurance]]></category>
		<category><![CDATA[Quality Engineering]]></category>
		<category><![CDATA[Regression Testing]]></category>
		<category><![CDATA[Scalable Systems]]></category>
		<category><![CDATA[Software Testing]]></category>
		<category><![CDATA[SRE]]></category>
		<category><![CDATA[System Design]]></category>
		<category><![CDATA[Test Management]]></category>
		<category><![CDATA[Tooling Strategy]]></category>
		<guid isPermaLink="false">https://santeware.com/?p=17198</guid>

					<description><![CDATA[Introduction Most software teams start with good intentions around quality in software life cycle. Developers write unit tests. Bugs are tracked somewhere. Releases go out on time—until scale exposes the cracks. At Santeware Healthcare Solutions, we reached that inflection point while managing QA across nearly ten active healthcare projects at a time. Quality issues were [&#8230;]]]></description>
		
					<wfw:commentRss>https://santeware.com/building-a-scalable-quality-assurance-unit-for-complex-healthcare-it-project-delivery-without-buying-new-tools/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Building a Real-Time Aneurysm Decision Support System (DSS) Leveraging FHIR R4 from Epic and Athenahealth</title>
		<link>https://santeware.com/building-a-real-time-aneurysm-decision-support-system-dss-leveraging-fhir-r4-from-epic-and-athenahealth/</link>
					<comments>https://santeware.com/building-a-real-time-aneurysm-decision-support-system-dss-leveraging-fhir-r4-from-epic-and-athenahealth/#respond</comments>
		
		<dc:creator><![CDATA[superadmin]]></dc:creator>
		<pubDate>Fri, 21 Mar 2025 06:34:34 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[#HealthcareIT #FHIR #EHRIntegration #SMARTonFHIR #ClinicalDecisionSupport #MirthConnect #SSO #DigitalHealth]]></category>
		<category><![CDATA[Aneurysm Decision Support System]]></category>
		<category><![CDATA[Athenahealth API integration]]></category>
		<category><![CDATA[FHIR R4 Epic integration]]></category>
		<category><![CDATA[HL7 FHIR data transformation with Mirth Connect]]></category>
		<category><![CDATA[real-time clinical DSS]]></category>
		<category><![CDATA[SMART on FHIR apps]]></category>
		<category><![CDATA[SSO for EHR]]></category>
		<guid isPermaLink="false">https://santeware.com/?p=15666</guid>

					<description><![CDATA[Introduction Aneurysms are life-threatening conditions that often go undetected until it is too late. According to the Centers for Disease Control and Prevention (CDC), over 50,000 deaths annually in the United States are attributed to aortic and brain aneurysms. In response to this clinical challenge, a global data science and analytics company embarked on a [&#8230;]]]></description>
		
					<wfw:commentRss>https://santeware.com/building-a-real-time-aneurysm-decision-support-system-dss-leveraging-fhir-r4-from-epic-and-athenahealth/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Seamless Integration of Biopsy LIS with Epic, eClinicalWorks, and Modernizing Medicine EHR Systems Using Mirth Connect</title>
		<link>https://santeware.com/seamless-integration-of-biopsy-lis-with-epic-eclinicalworks-and-modernizing-medicine-ehr-systems-using-mirth-connect/</link>
					<comments>https://santeware.com/seamless-integration-of-biopsy-lis-with-epic-eclinicalworks-and-modernizing-medicine-ehr-systems-using-mirth-connect/#respond</comments>
		
		<dc:creator><![CDATA[superadmin]]></dc:creator>
		<pubDate>Sun, 23 Feb 2025 13:51:23 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[#BiopsyLISIntegration]]></category>
		<category><![CDATA[#ClinicalDataExchange]]></category>
		<category><![CDATA[#eClinicalWorksIntegration]]></category>
		<category><![CDATA[#EHRIntegrationSolutions]]></category>
		<category><![CDATA[#EHRLISInterface]]></category>
		<category><![CDATA[#EpicLISIntegration]]></category>
		<category><![CDATA[#HealthcareDataIntegration]]></category>
		<category><![CDATA[#HL7v2Messaging]]></category>
		<category><![CDATA[#LabInformationSystemIntegration]]></category>
		<category><![CDATA[#LISEHRInteroperability]]></category>
		<category><![CDATA[#LIStoEHRWorkflow]]></category>
		<category><![CDATA[#MirthConnectHL7Integration]]></category>
		<category><![CDATA[#ModernizingMedicineInterface]]></category>
		<category><![CDATA[#PathologySystemIntegration]]></category>
		<guid isPermaLink="false">https://santeware.com/?p=15596</guid>

					<description><![CDATA[Introduction: Enabling Interoperability in Diagnostic Workflows In today’s digital healthcare landscape, seamless integration between Laboratory Information Systems (LIS) and Electronic Health Record (EHR) platforms is critical for accelerating clinical workflows and improving patient outcomes. At the forefront of this transformation is the integration of Biopsy LIS with leading EHR systems—Epic, eClinicalWorks (eCW), and Modernizing Medicine [&#8230;]]]></description>
		
					<wfw:commentRss>https://santeware.com/seamless-integration-of-biopsy-lis-with-epic-eclinicalworks-and-modernizing-medicine-ehr-systems-using-mirth-connect/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Revolutionizing Organ Transplant Data Archiving: A Santeware Success Story</title>
		<link>https://santeware.com/revolutionizing-organ-transplant-data-archiving-a-santeware-success-story/</link>
					<comments>https://santeware.com/revolutionizing-organ-transplant-data-archiving-a-santeware-success-story/#respond</comments>
		
		<dc:creator><![CDATA[superadmin]]></dc:creator>
		<pubDate>Sat, 25 Jan 2025 11:13:05 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[#ClinicalDataArchiving]]></category>
		<category><![CDATA[#DonorRecipientSummaries]]></category>
		<category><![CDATA[#EMRtoPDFConversion]]></category>
		<category><![CDATA[#HealthcareCompliance]]></category>
		<category><![CDATA[#HTMLtoPDFMedicalRecords]]></category>
		<category><![CDATA[#LegacyEMRMigration]]></category>
		<category><![CDATA[#OrganTransplantDataArchiving]]></category>
		<category><![CDATA[#TeleresultsEMRExtraction]]></category>
		<category><![CDATA[#TransplantCenterDataSolutions]]></category>
		<guid isPermaLink="false">https://santeware.com/?p=15502</guid>

					<description><![CDATA[Introduction: Raising the Bar in Healthcare Data Management In the age of digital healthcare, comprehensive data accessibility, regulatory compliance, and clinical accuracy are not just desirable—they’re essential. At Santeware Healthcare Solutions, we specialize in high-stakes, high-impact data transformation projects. One such endeavor involved partnering with a renowned Organ Transplant Center to preserve and future-proof one [&#8230;]]]></description>
		
					<wfw:commentRss>https://santeware.com/revolutionizing-organ-transplant-data-archiving-a-santeware-success-story/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Streamlining Healthcare Data: Manage Your Data Warehouses With Santeware</title>
		<link>https://santeware.com/streamlining-healthcare-data-manage-your-data-warehouses-with-santeware/</link>
					<comments>https://santeware.com/streamlining-healthcare-data-manage-your-data-warehouses-with-santeware/#respond</comments>
		
		<dc:creator><![CDATA[superadmin]]></dc:creator>
		<pubDate>Mon, 22 Jul 2024 14:11:12 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[#HealthcareData #DataManagement #Santeware #DataWarehousing #HealthTech #StreamlineData #DataSolutions #HealthcareInnovation #MedicalData #HealthDataWarehousing]]></category>
		<guid isPermaLink="false">https://santeware.com/?p=12644</guid>

					<description><![CDATA[Introduction In the ever-evolving landscape of healthcare IT, data migration stands as a critical process for organizations aiming to harness the power of centralized data management. Santeware, a leading provider of healthcare IT solutions, recently undertook a monumental data migration project for one of its clients, seamlessly transitioning data from disparate sources into a unified [&#8230;]]]></description>
		
					<wfw:commentRss>https://santeware.com/streamlining-healthcare-data-manage-your-data-warehouses-with-santeware/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Key differences in between a data Scientist and a Data Engineer</title>
		<link>https://santeware.com/key-differences-in-between-a-data-scientist-and-a-data-engineer/</link>
					<comments>https://santeware.com/key-differences-in-between-a-data-scientist-and-a-data-engineer/#respond</comments>
		
		<dc:creator><![CDATA[superadmin]]></dc:creator>
		<pubDate>Tue, 04 Jun 2024 09:08:10 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Artificial intelligence]]></category>
		<category><![CDATA[business analytics]]></category>
		<category><![CDATA[data analysis]]></category>
		<category><![CDATA[data engineering]]></category>
		<category><![CDATA[data pipelines]]></category>
		<category><![CDATA[data science]]></category>
		<guid isPermaLink="false">https://santeware.com/?p=12139</guid>

					<description><![CDATA[Introduction In every industry include Healthcare, Datascientists and data engineers are both crucial roles within the realm ofdata-driven decision-making, but they focus on different aspects of the datalifecycle and require distinct skill sets.  Data Scientist Role and Responsibility:  Data scientists are primarily responsible for extracting insights and knowledge from data through analysis, interpretation, and modelling. [&#8230;]]]></description>
		
					<wfw:commentRss>https://santeware.com/key-differences-in-between-a-data-scientist-and-a-data-engineer/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Comparing HL7 v2 vs FHIR data models &#8211; Which one improves implementer usability healthcare interoperability?</title>
		<link>https://santeware.com/comparing-hl7-v2-vs-fhir-data-models-which-one-improves-implementer-usability-healthcare-interoperability/</link>
					<comments>https://santeware.com/comparing-hl7-v2-vs-fhir-data-models-which-one-improves-implementer-usability-healthcare-interoperability/#respond</comments>
		
		<dc:creator><![CDATA[superadmin]]></dc:creator>
		<pubDate>Tue, 14 May 2024 14:26:43 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[#smart#fhir #santeware #hl7 #integration]]></category>
		<category><![CDATA[#smart#fhir#santeware #hl7 #integration]]></category>
		<category><![CDATA[RESTful APIs]]></category>
		<category><![CDATA[XML]]></category>
		<guid isPermaLink="false">https://santeware.com/?p=11598</guid>

					<description><![CDATA[Introduction Health Level Seven (HL7) v2 and Fast Healthcare Interoperability Resources (FHIR) are two prominent data models in the healthcare industry. HL7 v2, a widely used standard, employs ASCII text-based messages and requires custom coding for interoperability. In contrast, FHIR, introduced in 2014, is an open standard that enables seamless data exchange between applications and [&#8230;]]]></description>
		
					<wfw:commentRss>https://santeware.com/comparing-hl7-v2-vs-fhir-data-models-which-one-improves-implementer-usability-healthcare-interoperability/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>De-Identification of Healthcare Data: Safeguarding Privacy and Advancing Research</title>
		<link>https://santeware.com/de-identification-of-healthcare-data-safeguarding-privacy-and-advancing-research/</link>
					<comments>https://santeware.com/de-identification-of-healthcare-data-safeguarding-privacy-and-advancing-research/#respond</comments>
		
		<dc:creator><![CDATA[superadmin]]></dc:creator>
		<pubDate>Tue, 30 Apr 2024 14:32:20 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Algorithms]]></category>
		<category><![CDATA[data-driven]]></category>
		<category><![CDATA[Deidentification]]></category>
		<category><![CDATA[Privacy]]></category>
		<guid isPermaLink="false">https://santeware.com/?p=11605</guid>

					<description><![CDATA[In an era where data powers innovation and drives progress, the healthcare sector stands out as a prime beneficiary and a crucial steward of vast amounts of sensitive information. However, with great data comes great responsibility, especially concerning privacy and security. De-identification of healthcare data has emerged as a pivotal strategy to balance the need [&#8230;]]]></description>
		
					<wfw:commentRss>https://santeware.com/de-identification-of-healthcare-data-safeguarding-privacy-and-advancing-research/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
