Dave Weitzel

This is an interesting article because EHR companies, like Epic and Oracle's Cerner, have made siloing data a major part of their business model. Overall, I like EPIC’s ability to review records from other EPIC shops. It also has a nod to interoperability with its “Care Everywhere“ feature. However, this is often a disorganized and outdated collection of information. Using it requires a ninja level of both tech expertise and medical knowledge possessed mainly by younger physicians and chief residents. I am a fan (and advisor) of companies like Zus Health focused on user-friendly, comprehensive, and up-to-date interoperable health care data tools.

57

25 Comments

🕒 Tired of Time Tracking Terrors? Wrike's Got You! 🕒 Struggle with spreadsheets? Say goodbye to the grind with Wrike's "Getting Started in Wrike: Time Tracking" deminar. 🎯 From task timers to terrific reports, learn the simple steps to save time and secure your success. See how real teams like yours are turning time tracking into a triumph! Don't miss out, register TODAY! 🌐

2

See how to improve provider negotiations by accurately modeling contract rate changes using actual claims data for an expedited, accurate and simplified contracting process. #HealthcareContracting #NetworX #NetworXModeler #Analytics #CMSBenchmarking Cognizant https://cogniz.at/45SBibf

3

See how to improve provider negotiations by accurately modeling contract rate changes using actual claims data for an expedited, accurate and simplified contracting process. #HealthcareContracting #NetworX #NetworXModeler #Analytics #CMSBenchmarking Cognizant https://cogniz.at/44mCGlX

8

How does a FHIR resource id differ from a resource identifier? The distinction between them is not always obvious to those new to FHIR. Look at this Patient resource for August T. Faulkner: https://lnkd.in/gai3m7N6 The resource has an id of “eacce214-93d1-41cd-5cd8-866c785dc5f1” — a random GUID generated by the FHIR server when the resource was created. - Every resource stored in FHIR must have an id - It does not change for the lifetime of the resource - It is unique to that resource type in that FHIR server - No meaning should be inferred from its value The last point is interesting, as many online examples of resources use meaningful id values such as “patient” or “blood-pressure-observation.” These are misleading and can cause confusion as they suggest the id itself has some meaning. It doesn’t. Here’s how to look up the above patient using the resource’s id: - /Patient/eacce214-93d1-41cd-5cd8-866c785dc5f1 - /Patient?_id=eacce214-93d1-41cd-5cd8-866c785dc5f1 More about the resource id: https://lnkd.in/gY-HnhJ9 Our patient August T. Faulkner also has a Medical Record Number — possibly provided by the hospital — of 78510398960. This is added to the same FHIR resource as an identifier. Identifiers in FHIR are business identifiers. Unlike the FHIR resource id they are not created by the FHIR server and have no connection to the server.  Examples of other identifiers used for patients are: - Social security number - Health card number - Passport number A patient resource in FHIR may have any number of identifiers of various types, or none at all. Here’s how you look up the patient August T. Faulkner using his Medical Record Number: - /Patient?identifier=78510398960 - /Patient?identifier=http: //my .localhospital .ie/fhir/patient-MRN|78510398960 More about identifiers: https://lnkd.in/gm-F_rs2 And identifier types: https://lnkd.in/g4gEDQsA Here’s the Patient resource for August T. Faulkner on the HAPI test server: https://lnkd.in/gYt99mxR

65

11 Comments

While the #FHIR specification greatly enhances healthcare #interoperability, beginners often find it challenging to navigate. Analysts and developers frequently face issues that aren't directly addressed in the FHIR documentation. Below is an overview of some common questions surrounding the FHIR search. For those seeking more detailed information and examples, check out our comprehensive article on FHIR search linked in the comments! #hl7 #healthIT

22

2 Comments

Automation can transform RCM, but it’s not a magic bullet. For example, automating claims can improve cash flow but requires upfront investment. In his Becker's Healthcare article, Navaneeth Nair explores four key distinctions to keep in mind: 1️⃣ initial investment vs. immediate savings 2️⃣ worker displacement vs. evolution 3️⃣ standardization vs. customization 4️⃣ scalability vs. complexity Find more in the article here: https://lnkd.in/g4F8Y8mV #RCMAutomation #HealthcareTech #AI #ML #BeckersHealthcare

28

1 Comment

The devil is in the details. Learn why record retrievals for HEDIS and Risk can be challenging and how Inovalon solutions help

17

1 Comment

Health insurance organizations can reduce fraud, get paid faster, and improve claims processes and patient care with cloud-native tools. Watch our webinar with Microsoft to learn how Epic Payer Platform on Azure can help. Webinar link in the comments. ⬇️ Bill Pritchett Josh P. Luke Yerkovich #epiconazure #epicEHR #epicpayerplatform #healthit #epic #azure

4

1 Comment

Check out this new article from Terri LeFort on how the integration of clinical governance into every phase of a #HealthIT project can set a #healthcare organization up for a successful #DigitalTransformation, help address current enterprise-wide challenges, and steer the course toward a healthier future.

6

KPI the most comprehensive view of patient insurance status available, encompassing over 200 million de-identified U.S. patient lives. Eager to learn more? Lucky for you, it's not too late to register for tomorrow's webinar 🙌 (Thursday, June 27, at 12 p.m. ET) Check the comments for the registration link 👇 #payeranalytics #KPI #komodopatientinsurance #patientinsurance #dualeligible #marketaccess

6

1 Comment

I love it when this sort of somewhat petty PR somehow makes its way through large enterprise organizations' approval processes. The actual reality of interoperability is that while Epic can certainly improve (like any EHR), it laps Oracle/Cerner when you look at any real metric for an apples-to-apples comparison: - Quantifiably more FHIR APIs, including for writing data - Advanced FHIR features like CDS Hooks and FHIRcast that no other EHR makes available - An easier API program (fhir.epic.com is easier to use and more supported than code.cerner.com) - Patient access apps deployed to all 400+ customers within 12 hours of registration - Quantifiably more HL7v2 interfaces - All health systems live on Carequality by default - A quantifiably broader and deeper set of data available to pull via Carequality with patient level CDA, encounter level CDA, specialty specific CDAs for obstetrics/oncology, all PDFs/images/docs stored in Epic. Curious what other metrics are out there that the author is thinking of. https://lnkd.in/g75Ys8bK

103

30 Comments

In this article on 2024 health IT predictions for AI, Pega's Robert Connely weighs in on how AI can streamline operations and align clinical and administrative data. https://pe.ga/3xT9t6n

3