You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Kun Deng (Jira)" <ji...@apache.org> on 2020/07/27 14:23:00 UTC
[jira] [Commented] (NIFI-6320) ExtractHL7Attributes should better
tolerate custom segments (e.g. Z segments)
[ https://issues.apache.org/jira/browse/NIFI-6320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17165747#comment-17165747 ]
Kun Deng commented on NIFI-6320:
--------------------------------
Hi, this issue is not completely resolved. I have a lot of HL7 messages that are of version 2.3 but they have Z segments. Without removing those segments, HL7 processor fails to parse/decode the messages no matter whether I choose use segment names or not.
Here is an example:
MSH|^~\&|MICHART|HOSP.MED.UMICH.EDU|HUB|HOSP.MED.UMICH.EDU|202007201229||ADT^A04|653933223|P|2.3
EVN|A04|202007201229||OPR|663756413^Mcdaniel^Alonzo
PID|1|669298786|735878472^^^^PM~735878472^^^^PI~^^^^AI||Craft^Jorge^|Morrison^Madeline|19441030000000|F|Holder^Van|W|259 Bronco Ct^^Portola Valley^CA^27872^US^P^^NEWAYGO|NEWAYGO|5554447^^^^^^^^~5554092^^^^^^^^|5558521|AME|M|MET||348-320-7506||||||||||20200926101832|N
NK1|1|Perez^Rufus^|1|175 Bestway Pkwy^^Titusville^PA^94028^US|5555535~5559056|5550548|E
NK1|2||||||N
NK1|3||||||J
PV1|1|O|NSA^^^UTC|S||||||||||Phys/Clinic||||V|221042577|CARE|||||||||||||||||||||Scheduled|||20200720080000
PV2||||||||20200721080000
GT1|1|795174596|Garza^Gwen^
IN1|1|10100303|752586155||847 Greenridge Trl^^Lamar^CO^81052||5554852||||^^904927671|20170101|""|||Scott^Randal^|Spouse|19450731000000|461 Comedy Ln^^Mud Butte^SD^16354^US^^^OCEANA|||1|||N||||||||||2897830|883519529|||||||F||No||BOTH|TRICARE FOR LIFE WPS
IN2||670-150-6379|||Payor Plan||||||||||||||||||||||||||||||||||||||||||||||||||||||||||5555359
IN1|2|200103|258570286||81 Appletree Ct^^Lamar^CO^57758||5555834||||^^792264677|20100201|""|||Scott^Randal^|Self|19450731000000|461 Comedy Ln^^Mud Butte^SD^16354^US^^^OCEANA|||2|||Y||||20200526000000|090979981^Bond^Lena^|||||2897834|678956970|||||||F||El||BOTH|MEDICARE PART A AND B
IN2||670-150-6379|||Payor Plan
ZPID|N||||||20200526000000|||||||||||||||(123)456-7890||||||||||||||||||||||||||||||||""
ZPV3|""|047196^OCHS^xxx^yyy|(111)222-333|xxxx^^^yyy^MI^11111-1234|||||||||||||OV
ZBK|||||999907908764|||||||||NSA|P
ZST|Epic.MiChart_ADT_INBOUND|POC_OUT|2020-07-20 12:30:03.442
> ExtractHL7Attributes should better tolerate custom segments (e.g. Z segments)
> -----------------------------------------------------------------------------
>
> Key: NIFI-6320
> URL: https://issues.apache.org/jira/browse/NIFI-6320
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.9.2
> Environment: OSX iMac
> Reporter: Gary Teichrow
> Priority: Minor
> Labels: Processor, hl7
> Fix For: 1.10.0
>
> Original Estimate: 1h
> Time Spent: 20m
> Remaining Estimate: 40m
>
> If a user is processing an HL7 message that contains custom segments (e.g. Z segments), an NPE is thrown at line 288 in ExtractHL7Attributes.java upon encountering that segment. The call to segment.getNames() will return a list of Nulls from HAPI for this custom segment.
> Added a check whereby, if the user is using the "Use Segment Names" option in the ExtractHL7Attributes processor and the HL7 message being processed contains custom user segments (e.g., Z Segments), the code will downgrade to returning the Segment Label as it does when this option is not used. Without this a null pointer is thrown at line 288.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)