Posts

Showing posts from November, 2023

How AGI can reshape the world

1. AGI Overview:    - AGI represents a major leap in capabilities, transitioning beyond NarrowAI.    - Full AGI realization will take time, but ongoing evolution is evident.   2. Human-like Potential:    - AGI has the potential to accomplish any task a human can, bridging the gap between specialized AI and human adaptability.   3. Comprehension and Learning:    - AGI aims to comprehend and learn data, addressing the challenge of machines excelling at tasks but lacking generalization abilities.    - It unlocks understanding and problem-solving across diverse domains.   4. Transformative Features:    - AGI enables intuitive interactions with technology, impacting various sectors like healthcare, education, manufacturing, and finance.    - Applications include personalized learning, predictive maintenance, and emotional understanding.   5. Diverse Applications:  ...

Programming languages. popularity , resources and comparison

Stackoverflow survey showing popularity of languages: https://survey.stackoverflow.co/2023/#programming-scripting-and-markup-languages Most in demand prog languages with related resources: https://bootcamp.berkeley.edu/blog/most-in-demand-programming-languages/ Difference in Python and Javascript :https://freecodecamp.org/news/python-vs-javascript-what-are-the-key-differences-between-the-two-popular-programming-languages/

Languages needed to become a full-stack developer in the healthcare domain

For someone aspiring to become a full-stack developer in the healthcare domain, it's essential to have a well-rounded skill set that includes both frontend and backend development. Here's a breakdown of programming languages that one might find useful for different aspects of full-stack development in the healthcare industry: Frontend Development: 1. JavaScript (and its frameworks/libraries): For web-based applications, JavaScript is a must. Popular frameworks like React.js, Angular, or Vue.js are widely used for building interactive and dynamic user interfaces. Backend Development: 1. Java: Java is a solid choice for backend development. It's widely used, scalable, and has good support for building robust server-side applications. In the healthcare industry, Java is often used for middleware and backend services. 2. Python: Python is versatile and has a strong ecosystem for backend development. It's used in various healthcare applications for data processing, server-si...

How HL7 v2 messages goes into a CDR (Clinical Data Repository) instance and mapped into FHIR bundles

A.  Smile CDR is capable of ingesting messages in this format and converting them into a FHIR-formatted bundle.   https://www.smiledigitalhealth.com/hl7-v2-walkthrough B.  2 HL7 version 2 to FHIR mapping scenarios https://www.ringholm.com/docs/04350_mapping_HL7v2_FHIR.htm C. additional: hl7 conformance statement pdf Page 10 to 13 of PDF (46 pages) https://www.arthrex.com/resources/860-0036-00/arthrex-synergynet-hl7-conformance-statement

HL7 messages - definitions, samples, resources

A. Message types defined , samples: https://www.interfaceware.com/hl7-adt HL7 ADT (Admit, Discharge and Transfer) HL7 ORM (Order Entry) HL7 ORU (Observation Result) HL7 MDM (Medical Document Management) HL7 DFT (Detailed Financial Transactions) HL7 BAR (Billing Account Record) HL7 SIU (Scheduling Information Unsolicited) HL7 RDS (Pharmacy/treatment Dispense) HL7 RDE (Pharmacy/Treatment Encoded Order) HL7 ACK (Acknowledgement Message) B.  https://hl7messageparser.azurewebsites.net/Parse/Samples C. https://community.intersystems.com/post/types-hl7-adt-message-and-example-adta04 Subtype with description: ADT^A01 Patient admission/visit  ADT^A02 Patient transfer ADT^A03 Patient discharge ADT^A04 Patient registration ADT^A05 Patient pre-admission ADT^A08 Patient information update ADT^A11 Cancel patient admission ADT^A12 Cancel patient transfer ADT^A13 Cancel patient discharge D. Several samples: https://docs.enterprisehealth.com/functions/system-administration/in...

HL7 message decoded: Patient Information Update

 ADT_A08 Patient Information Update Sample MSH|^~\&|AccMgr|1|||20050110045504||ADT^A08|599102|P|2.3||| EVN|A01|20050110045502||||| PID|1||10006579^^^1^MRN^1||DUCK^DONALD^D||19241010|M||1|111 DUCK ST^^FOWL^CA^999990000^^M|1|8885551212|8885551212|1|2||40007716^^^AccMgr^VN^1|123121234|||||||||||NO NK1|1|DUCK^HUEY|SO|3583 DUCK RD^^FOWL^CA^999990000|8885552222||Y|||||||||||||| PV1|1|I|PREOP^101^1^1^^^S|3|||37^DISNEY^WALT^^^^^^AccMgr^^^^CI|||01||||1|||37^DISNEY^WALT^^^^^^AccMgr^^^^CI|2|40007716^^^AccMgr^VN|4|||||||||||||||||||1||G|||20050110045253|||||| GT1|1|8291|DUCK^DONALD^D||111^DUCK ST^^FOWL^CA^999990000|8885551212||19241010|M||1|123121234||||#Cartoon Ducks Inc|111^DUCK ST^^FOWL^CA^999990000|8885551212||PT| DG1|1|I9|71596^OSTEOARTHROS NOS-L/LEG ^I9|OSTEOARTHROS NOS-L/LEG ||A| IN1|1|MEDICARE|3|MEDICARE|||||||Cartoon Ducks Inc|19891001|||4|DUCK^DONALD^D|1|19241010|111^DUCK ST^^FOWL^CA^999990000|||||||||||||||||123121234A||||||PT|M|111 DUCK ST^^FOWL^CA^999990000|||||8291 IN2|1||123...

HL7 message decoded: Patient admit

ADT_A01 Patient Admit Sample  MSH|^~\&|AccMgr|1|||20050110045504||ADT^A01|599102|P|2.3||| EVN|A01|20050110045502||||| PID|1||10006579^^^1^MRN^1||DUCK^DONALD^D||19241010|M||1|111 DUCK ST^^FOWL^CA^999990000^^M|1|8885551212|8885551212|1|2||40007716^^^AccMgr^VN^1|123121234|||||||||||NO NK1|1|DUCK^HUEY|SO|3583 DUCK RD^^FOWL^CA^999990000|8885552222||Y|||||||||||||| PV1|1|I|PREOP^101^1^1^^^S|3|||37^DISNEY^WALT^^^^^^AccMgr^^^^CI|||01||||1|||37^DISNEY^WALT^^^^^^AccMgr^^^^CI|2|40007716^^^AccMgr^VN|4|||||||||||||||||||1||G|||20050110045253|||||| GT1|1|8291|DUCK^DONALD^D||111^DUCKST^^FOWL^CA^999990000|8885551212||19241010|M||1|123121234||||#Cartoon Ducks Inc|111^DUCK ST^^FOWL^CA^999990000|8885551212||PT| DG1|1|I9|71596^OSTEOARTHROS NOS-L/LEG ^I9|OSTEOARTHROS NOS-L/LEG ||A| IN1|1|MEDICARE|3|MEDICARE|||||||Cartoon Ducks Inc|19891001|||4|DUCK^DONALD^D|1|19241010|111^DUCK ST^^FOWL^CA^999990000|||||||||||||||||123121234A||||||PT|M|111 DUCK ST^^FOWL^CA^999990000|||||8291 IN2|1||123121234|Cartoon...

HL7 message decoded: Patient registration

  ADT_A04 Patient Registration Sample MSH|^~\&|ADT1|MCM|LABADT|MCM|198808181126|SECURITY|ADT^A04|MSG00001|P|2.4 EVN|A01-|198808181123 PID|||PATID1234^5^M11||JONES^WILLIAM^A^III||19610615|M-||2106-3|1200 N ELM STREET^^GREENSBORO^NC^27401-1020|GL|(919)379-1212|(919)271-3434~(919)277-3114||S||PATID12345001^2^M10|123456789|9-87654^NC NK1|1|JONES^BARBARA^K|SPO|||||20011105 NK1|1|JONES^MICHAEL^A|FTH PV1|1|I|2000^2012^01||||004777^LEBAUER^SIDNEY^J.|||SUR||-||1|A0- AL1|1||^PENICILLIN||PRODUCES HIVES~RASH AL1|2||^CAT DANDER DG1|001|I9|1550|MAL NEO LIVER, PRIMARY|19880501103005|F|| PR1|2234|M11|111^CODE151|COMMON PROCEDURES|198809081123 ROL|45^RECORDER^ROLE MASTER LIST|AD|CP|KATE^SMITH^ELLEN|199505011201 GT1|1122|1519|BILL^GATES^A IN1|001|A357|1234|BCMD|||||132987 IN2|ID1551001|SSN12345678 ROL|45^RECORDER^ROLE MASTER LIST|AD|CP|KATE^ELLEN|199505011201 Subparts of the HL7 message: 1. MSH Segment (Message Header): - Field Separator: | - Encoding Characters: ^~\ - Sending Applica...

Automatic calculations such as BMI (Body Mass Index) can be handled through the use of FHIR

  In FHIR (Fast Healthcare Interoperability Resources), automatic calculations such as BMI (Body Mass Index) can be handled through the use of FHIR resources and expressions. Here's a general outline of how automatic BMI calculations might happen in the FHIR context:   1. Patient Resource:    - FHIR includes a resource type called "Patient" that represents an individual receiving or requiring healthcare services. This resource includes information about the patient, including their height and weight.   2. Observation Resource:    - To represent the patient's height and weight, FHIR has the "Observation" resource. The height and weight measurements can be recorded as observations associated with the patient.      Example:    ```json    {      "resourceType": "Observation",      "status": "final",      "category": [   ...

CDS Hooks (Clinical Decision Support Hooks) in FHIR

  CDS Hooks (Clinical Decision Support Hooks) in FHIR (Fast Healthcare Interoperability Resources) is a standard that enables the integration of clinical decision support (CDS) into healthcare workflows. CDS Hooks provide a mechanism for external decision support services to interact with healthcare systems in real-time, offering guidance and recommendations to clinicians as they make decisions about patient care. Here are five examples of how CDS Hooks can be used:   1. Drug-Drug Interaction Alerts:    - When a clinician is prescribing a medication, a CDS Hook can be triggered to check for potential drug-drug interactions based on the patient's medication history. The system can then provide real-time alerts or suggestions to the clinician about potential interactions and alternative medications.   2. Allergy Checking:    - When a clinician is about to order a medication, a CDS Hook can be triggered to check for known allergies in the pati...

Swagger vs Postman

Swagger and Postman are two powerhouse solutions that are pivotal in simplifying the complex processes of designing, testing, and documenting APIs. While they share common goals, they have distinct features and use cases that set them apart. Swagger is primarily used for API design, documentation, and testing, while Postman focuses on API testing, monitoring, and collaboration.  https://testsigma.com/blog/swagger-vs-postman/

REST API or RESTful API , examples, compared with SOAP

 What is a REST API? An API, or application programming interface, is a set of rules that define how applications or devices can connect to and communicate with each other. A REST API is an API that conforms to the design principles of the REST, or representational state transfer architectural style. # Focused articles:  (a) https://www.altexsoft.com/blog/rest-api-design/  (use arrow key to scroll down) (b) https://blog.postman.com/rest-api-examples/ # Article on advantage and type of solutions which use REST API  https://konghq.com/learning-center/api-gateway/what-is-restful-api  # Video: What Is REST API? Examples And How To Use It?  https://www.youtube.com/watch?v=-mN3VyJuCjM # For coders  https://www.freecodecamp.org/news/rest-api-tutorial-rest-client-rest-service-and-api-calls-explained-with-code-examples/ REST vs SOAP https://blog.hubspot.com/website/rest-vs-soap https://aws.amazon.com/compare/the-difference-between-soap-rest

Why snowflake for healthcare? Comparison with AWS, GCP

Personalize care with a holistic view of patients and members that combines multiple data sources. Snowflake enables easy access to unstructured, semi-structured and structured data from a single platform with near-infinite scale, which helps organizations generate holistic, real-time patient and member views across clinical, claims, consumer and socio-economic data silos. https://www.snowflake.com/en/solutions/industries/healthcare-and-life-sciences/ Snowflake is so popular because of its unique data platform architecture; separate compute and storage, which helps speed up operations and extensibility. Also, Snowflake integrates with the major public clouds, Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform (GCP). Ref www.cloudzero.com/blog/snowflake-vs-aws-vs-azure/

Utilization management (UM) and risk adjustment compared

  Utilization management (UM) and risk adjustment serve distinct but complementary purposes in the healthcare industry. While risk adjustment is primarily focused on accurately reflecting the health status of a population for reimbursement purposes, utilization management plays a crucial role in ensuring the appropriate and efficient use of healthcare resources. Here's why both are needed:     1. Different Focus and Objectives:    - Risk Adjustment: Primarily focuses on capturing and adjusting for the health risk and complexity of a population to determine accurate reimbursement levels for healthcare plans. It ensures that plans receive adequate compensation based on the expected health needs of their members.    - Utilization Management: Focuses on reviewing and managing the utilization of healthcare services to ensure that they are necessary, appropriate, and cost-effective. It aims to prevent overutilization, reduce unnecessary costs, and en...

Important Steps in Better Risk Adjustment in Healthcare. US healthcare

1. Member-Provider Connections Establishing meaningful connections between members and healthcare providers is crucial for successful risk adjustment. Primary care physicians (PCPs) play a central role in ensuring better care and monitoring for members, documenting health statuses, and fostering active engagement between members and providers. Programs that encourage regular check-ups, wellness visits, and screenings, along with incentives like gift cards, promote adherence to recommended procedures. Additionally, call-to-action programs and in-home assessments contribute to comprehensive care. 2. Accurate Medical Charting and Coding Accurate charting and coding of members' health status are vital for effective risk adjustment. Health plans can achieve this through ongoing provider education, prospective charting to capture chronic conditions, and leveraging new technologies such as artificial intelligence for value-based care. Concurrent coding expedites the billing cycle, while r...

Viewers to view FHIR / CCD xml data in a human readable format

 Use below XML viewers to view the data in a human readable format https://jsonformatter.org/xml-formatter  ( use search box in 'XMLtree' view to  search data of interest. eg. 'BMI' , 'diagnosis' , 'ICD' or 'cpt') Try it with this data: a.  CCD https://github.com/HL7/C-CDA-Examples/blob/master/Documents/CCD/CCD%202/CCD.xml b. Care plan   https://github.com/HL7/C-CDA-Examples/blob/master/Documents/Care%20Plan/Care_Plan.xml FHIR resource- Care plan : https://build.fhir.org/careplan.html  Go to 'XML' tab for xml template. ------ Another XML viewer:   https://codebeautify.org/xmlviewer

Sample Data for EDI 278 Request. Health Services Review

Health Care Claim Status Request and Response (278) transaction. Let's break down the components: 1. **ISA Segment:**    - ISA: Interchange Control Header    - 00: Authorization Information Qualifier    - 00: Authorization Information    - ZZ: Security Information Qualifier    - 123456789ABC: Security Information    - ZZ: Interchange ID Qualifier    - FIDELIS: Interchange Sender ID    - 180605: Interchange Date    - 2320: Interchange Time    - ^: Repetition Separator    - 00501: Interchange Control Standards Identifier    - 050443801: Interchange Control Version Number    - 0: Interchange Control Number    - T: Acknowledgment Requested 2. **GS Segment:**    - GS: Functional Group Header    - HI: Code identifying the type of functional group    - 123456789ABC: Application Sender's Code    - FIDELIS: Application...

Sample Data for EDI 278 Request. Admission Review

Example of an X12 EDI (Electronic Data Interchange) document. Each line represents a segment, and the segments are grouped to convey information about a specific transaction or business process. In this case, it seems to be a healthcare-related transaction, possibly related to a health insurance claim. Here's a brief breakdown of the structure: - ISA: Interchange Control Header - GS: Functional Group Header - ST: Transaction Set Header - BHT: Beginning of Hierarchical Transaction - HL: Hierarchical Level - NM1: Name (such as organization or individual name) - REF: Reference information - N3: Address information - N4: Location (city, state, zip) - DMG: Demographic information - TRN: Trace information - UM: Unit of Measurement - DTP: Date/Time Period - HI: Healthcare Information Codes - HSD: Health Care Services Delivery - CL1: Institutional Claim Code - SE: Transaction Set Trailer - GE: Functional Group Trailer - IEA: Interchange Control Trailer These segments and their data provide...

The calculation of an enrollee’s risk score, which is used in risk adjustment

  The calculation of an enrollee’s risk score, which is used in risk adjustment in healthcare, begins with their demographics and Hierarchical Condition Categories (HCCs), which are the medical codes for their conditions 1 . The demographic factors used to calculate risk scores include: Age Sex Socioeconomic data Disability status or eligibility Medicaid eligibility Institutional status (nursing homes, inpatient care, etc.) 1 These demographics are paired with an enrollee’s list of diagnoses. These codes have all been assigned a specific value for risk adjustment 1 . For example, diabetes that is well-managed with no complications would have an HCC of 19 ( requiring higher expense due to onoing care) , while diabetes in full ketoacidosis would be an HCC 17 (requiring lower expense due to a temporary problem) . These numbers, paired with the demographic information, would determine how much risk adjustment is necessary for this enrollee 1 . The variables that most impact one’s risk...

Risk adjustment: How clinical guidelines and scoring systems are used with HCC coding

  Milliman and InterQual are two prominent organizations that provide clinical guidelines and scoring systems in the healthcare industry. These scoring systems, particularly when used in conjunction with Hierarchical Condition Category (HCC) coding, play a crucial role in risk adjustment and reimbursement methodologies in healthcare.   1. InterQual Scoring:    - Purpose: InterQual is a decision support solution that assists healthcare professionals in making evidence-based decisions regarding patient care, utilization, and level of service.    - Scoring System: InterQual utilizes a scoring system to evaluate the medical necessity and appropriateness of healthcare services. This scoring helps determine the level of care needed for a patient.   2. Milliman Scoring:    - Purpose: Milliman offers various solutions, including Milliman Care Guidelines (MCG), to assist in care management and utilization review.    - Scoring...

HCC coding based calculations for risk adjustment - examples

  The Hierarchical Condition Category (HCC) coding system plays a crucial role in risk adjustment, especially in programs like Medicare Advantage, where payments are adjusted based on the health status of individuals. The process involves identifying relevant diagnoses, mapping them to HCC codes, and aggregating HCC scores to calculate an individual's overall risk score.   # Examples of HCC Code Allocation:   1. Diabetes Mellitus:    - Diagnosis: Diabetes with complications    - HCC Code: HCC 19: Diabetes with Complications   2. Chronic Kidney Disease:    - Diagnosis: Stage 4 Chronic Kidney Disease    - HCC Code: HCC 12: End-Stage Renal Disease   3. Congestive Heart Failure:    - Diagnosis: Congestive Heart Failure    - HCC Code: HCC 85: Heart Failure   4. Rheumatoid Arthritis:    - Diagnosis: Rheumatoid Arthritis with complications    - HCC C...