Replies: 3 comments 3 replies
-
|
Did you forget to post your code attempts? Error messages? Sample inbound messages? Expected outbound messages for that inbound message? |
Beta Was this translation helpful? Give feedback.
-
|
@pacmano1 have you had a chance to review? I'm also needing to process AL1s and other segments that come in multiples. Thanks in advance for your assistance. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. I was afraid of that. And you are right about the extension. I am finding it quite clunky. I'm having to write a lot of routines to get around issues, such as this looping problem. I'll put in a ticket. Thanks again. And you have helped me out in the past, much appreciated. I fully understand your response here. Later. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm attempting to generate a FHIR RelatedPerson Resource type from HL7v2x NK1(s).
If a single NK1, it creates a related person resource type and it looks pretty good.
If multiple NK1 segments, the related person resource type is a bit jacked up. Has anyone been able to figure out how to put a loop around the process of the NK1s to generate the proper output? I am looking for the output to be laid out like the contacts are in the Patient resource type. This also uses the NK1. I have tried several different ways to code this similar to how the contacts are handled, but I'm getting many different issues or no output and no error feed back.
If anyone has tried this with success, I would be appreciated to discuss and get an idea as to how to make the Related Person resource type work. Thanks
Beta Was this translation helpful? Give feedback.
All reactions