The Certification Team of InterSystems Learning Services is in the process of developing an exam focusing on creating and working with TrakCare Integration, and we need input from our InterSystems TrakCare community. Your input will be used to evaluate and establish the contents of the exam.
How do I provide my input? We will provide a list of job tasks. You will rate them on their importance as well as other factors.
How much effort is involved? It takes about 15-20 minutes to fill out the survey.
I have been using embedded python for more than 2 years now on a daily basis.
May be it's time to share some feedback about this journey.
Why write this feedback? Because, I guess, I'm like most of the people here, an ObjectScript developer, and I think that the community would benefit from this feedback and could better understand the pros & cons of chosing embedded python for developing stuff in IRIS. And also avoid some pitfalls.
Sometimes we need to convert FHIR message to HL7 V2, e.g. to register a patient to the PACS system. In this article, I will explain the steps to achieve the desired by using IRIS FHIR Server production.
Below are the steps we need to follow:
Make sure FHIRServer production is started.
Register Business Service with FHIRServer endpoint.
Define Business Processes to convert FHIR message to SDA and then Convert SDA to HL7 v2.
Post JSON resource to FHIRServer endpoint and get HL7 V2 response.
Let's review the steps in detail.
Step 1. Make sure FHIRServer production is started
Open the production page and make sure Production is started. In the next step, we need to make sure business service HS.FHIRServer.Interop.Service is registered with FHIRServer
Step 2. Register Business Service with FHIRServer endpoint
From the management portal, Click on Health tab
Then click on FHIR configuration from the list and then click on Server Configuration
Select the endpoint and make sure under the Service Config Name, HS.FHIRServer.Interop.Service (Business service defined in production) is defined.
Step 3. Define Business Processes to covert FHIR message to SDA and then Convert SDA to HL7 v2
Define the business process (Solution.BP.Process is already defined in the application). Please note that we are applying a condition here that the endpoint must contain hl7 augment to proceed with conversion otherwise consider it as a normal FHIR request.
Then pass the message to the FHIR_SDA process which will convert the message to SDA. FHIR_SDA is derived from a user-defined Solution.BP.Process class. After conversion FHIR_SDA, the process passes the message to the SDA_HL7 process SDA_HL7 process is derived from a user-defined Solution.BP.SDATransformProcess class which converts SDA message to HL7 V2 message.
Define processes in the production as follows:
Step 4. Post JSON resource to FHIRServer endpoint and get HL7 V2 response
NOTE:Our FHIRServer endpoint is http://localhost:32783/csp/fhirserver/fhir/r4/, but we are passing hl7 as an argument to detect from the Production business process that this is not a normal FHIR Post request but it is a request to transform FHIR message.
The same functionality we can use from Our Web Applications. Select the Patient Resource, then click on the resource from the list, select the HL7 FHIR or Resource Details tab, and click on the "Transform FHIR to HL7 V2" button
The application will get the transformation message HL7 V2 with the help of FHIR Server production.
HL7 V2 to FHIR transformation
Select HL7 to FHIR from the menu and enter HL7 V2 data, Click the convert button to transform HL7 message to FHIR message
HL7 to FHIR Transformation is also using production to convert the HL7 V2 message to the FHIR message.
HL7_Http_Service Business Service sends HL7 message to HL7_SDA process and then HL7_SDA sends SDA data to SDA_FHIR process, which finally converts it to FHIR
For more details and code review, please visit iris-fhir-lab open exchange application page.
In a customer project I was asked how you can keep track of database changes: Who changed what at which date and time. Goal was to track insert, update and delete for both SQL and object access.
This is the table that I created to keep the Change Log:
In a world where healthcare technology is rapidly evolving, the importance of efficient, reliable, and interoperable healthcare applications has never been greater.
This is where FHIR (Fast Healthcare Interoperability Resources) comes in, a standard that has revolutionized data exchange in healthcare.
The introduction above is an example generated by AI, and as you can see, AI is around us everywhere, accessible to everyone…
Why IRIS-FHIRfy?
We need to learn more about using AI to our advantage, making life easier in every aspect.
The idea for IRIS-FHIRfy is to empower professionals and simplify its integrations; it's a solution that addresses the intricate needs of healthcare data integration.
If you read @José Pereiraarticle (which I strongly recommend since it will be worth your time and give you a better perspective of our project), when you have a chance to join a hackathon as a mentor, you encounter hackers with some challenges that we used to have a long time ago. They had never heard of InterSystems technology or had never interacted with the FHIR protocol before. But those hackers have something in common: an idea, a dream, and a willingness to bring that dream to reality.
Looking at those healthcare rookies in hackathons gave us the project idea, and we decided it would be amazing to offer a solution that could make their lives easier. So they don't need to worry about transformations, different standard types, and other concerns that a healthcare integration brings.
Now, let's dive into why we believe that IRIS-FHIRfy will help developers achieve their goals faster and easier than ever.
It streamlines the complex process of aligning various healthcare systems under the FHIR protocol or even HL7; why not?! This tool stands out for its:
Seamless Integration: Ensuring different healthcare systems communicate flawlessly.
Developer-Friendly Interface: Streamlining the coding experience.
Scalability: Capable of handling the ever-growing healthcare data demands.
The Unmatched Benefits for Developers
Interoperability at Its Finest: With IRIS-FHIRfy, developers can bridge disparate healthcare systems, ensuring seamless data flow and integration.
Rapid Development Cycle: This tool significantly reduces development time, allowing more focus on innovation and less on backend complexities.
Ease of Use: It offers an intuitive interface, making it accessible for developers and non-developers in a web app version and inside the developer's most preferable IDE (VSCode)
Understand your files: Understand the information you have in your hands, get suggestions, and accelerate the integration process. All of this is in a simple and easy-to-work interface.
Real-World Impact: Transforming Healthcare One Line of Code at a Time
Imagine a healthcare system where patient data is effortlessly integrated across different platforms, enhancing the efficiency and accuracy of medical care. IRIS-FHIRfy makes this possible. It's not just a tool; it's a catalyst for better healthcare delivery. This mindset is not something that only we, the creators of IRIS-FHIRfy, have others also see similar things for Healthcare Interoperability, like this post we saw today on LinkedIn.
Using an actual use case that happened to me a decade ago. Imagine that you never had to deal with a HL7 integration before. You just received the request to integrate a file format you had never heard of before and never interacted with. How are you supposed to know what every piece of information means?
Back then, I had to study the documentation, check every piece of information that the HL7 file gave me, and make a tedious process to generate the necessary integration files.
Now, bringing this exact use case to nowadays, I’ll use IRIS-FHIRfy to help me understand the file and suggest the integration with a simple “click.” The tools let the professional focus on the most important thing, the business rule, while IRIS-FHIRfy takes care of the “boring” part of the process.
Let's use this small HL7 file and see what IRIS-FHIRfy is capable of.
MSH|^~\&|WIR11.3.2^^|WIR^^||WIRPH^^|20200514||VXU^V04^VXU_V04|2020051412382900|P^|2.5.1^^|||ER||||||^CDCPHINVS PID|||3080500^^^^SR^~^^^^PI^||DTAP^TEST^M^^^^^|TESTM^TESTMOM^^^^^^|20180804|F|||1 E MAIN ST^1 main st^MADISON^WI^53703^^^^WI025^^||(354)686-5555^PRN^PH^^^354^6865555^^|||||||||||||||| PD1|||||||||||02^^^^^|N||||A NK1|1|DTAP^TESTMOM^^^^^^|MTH^MOTHER^HL70063^^^^^|^^MADISON^WI^^^^^^^| NK1|2|DTAP^TEST^^^^^^|SEL^SELF^HL70063^^^^^|1 E MAIN ST^1 main st^MADISON^WI^53703^^^^^^|(354)686-6575^PRN^PH^^^354^6866575^^ PV1||R||||||||||||||||||V07^ ORC|RE||0| RXA|0|999|20180910|20180910|20^DtaP^CVX^Infanrix^Infanrix^WVTN|1.0|||01^^^^^~38217674^WIR immunization id^IMM_ID^^^||||||||||| ORC|RE||0| RXA|0|999|20190807|20190807|150^Influenza Quadrivalent P-Free^CVX^Fluarix Quadrivalent, P-Free^Fluarix Quadrivalent, P-Free^WVTN|1.0|||00^^^^^~38253123^WIR immunization id^IMM_ID^^^||^^^Division of Public Health^^^^^^^^^^^||||jlb234||SKB^SKB^MVX^^^||| RXR|IM^^HL70162^^^|^^HL70163^^^
Standing Tall Among Giants: Why IRIS-FHIRfy is the Go-To Choice
Compared to other tools in the market, iris-fhirfy stands out for its comprehensive approach to FHIR-based integration, ease of use, and robust support. It's not just about what it does but how it does it – intuitively, effectively, and reliably.
Looking Ahead: The Future of IRIS-FHIRfy and FHIR Technology
The journey continues. With continuous updates and enhancements, IRIS-FHIRfy is poised to become even more powerful and indispensable in the healthcare technology landscape.
Conclusion: A Call to Action for Developers
Choosing the right tools is crucial in an industry where technology can directly impact lives. iris-fhirfy is more than just a tool; it's a step towards better, more integrated healthcare solutions, and why not say more integrated solutions are more accessible to everyone? That's why we invite you to be a part of this journey.
We are exploring the potential, contributing to the evolution, and being at the forefront of healthcare technology innovation.
Acknowledgment
Once again, we would like to thank you for all the support from the community in each of the applications we create.
If you found our app interesting and contributed some insight, please vote for IRIS-FHIRfy and help us on this journey!
Open Exchange.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
