Hi Mihai, I'm not entirely sure what is going on with the terser path you present, but "replace hapi-path" and "AIL-3|in HL7-message|@messageId" is certainly not valid syntax. Would you be able to provide an example by posting a complete Java class illustrating your issue?
Cheers, James On Mon, Aug 9, 2010 at 10:39 AM, Mihai Barbat <miha...@gmail.com> wrote: > Hi James > > First I will show you my messages. > > > MSH|^~\&|BLA|BLA|BLA|BLA|200911111530||SIU^S12^SIU_S12|123456789|P|2.5||||||8859/1 > SCH|QP_7913-X > TQ1||||||180|201006181630 > NTE|||Insert appointment|RE > PID|1||A3_NIP^^^TEST^PN||Name^FirstName||19800101 > PV1|1 > RGS|1 > AIS|1||CXR||| > AIG|1||G_7913-X|GENERAL > AIL|1||D_7913-X|D > AIL|2||E_7913-X|E > AIP|1||P_7913-X|P > AIP|2||T_7913-X|T > > Using hapi-0.5 from Fitnesse to be able to access the AIL field from an S12 > I did this: > > |replace hapi-path|AIL-3|in HL7-message|@messageId|with random > value|D_*|scenario| > > but with the latest hapi (hapi-0.5.1.2) this doesn't work anymore. > > Now I can only access the AIL segment like this: > > > |replace hapi-path|/.RESOURCES/.LOCATION_RESOURCE(0)/.AIL-3|in > HL7-message|@messageId|with random value|D_*|scenario| > > Isn't the new hapi backwards compatible? > > So ok I said, things changed and now we have to use the new way to access > the AIL field (.RESOURCES/.LOCATION_RESOURCE(0)/.AIL-3). And as I said it > works for an S12 message. > > > > MSH|^~\&|BLA|BLA|BLA|BLA|200911111530||SIU^S13^SIU_S12|123456789|P|2.5||||||8859/1 > SCH|QP_7913-X > TQ1||||||180|201006201630 > NTE|||Insert appointment|RE > PID|1||A3_NIP^^^TEST^PN||Name^FirstName||19800101 > PV1|1 > RGS|1 > AIS|1||CXR||| > AIG|1||G_7913-X|GENERAL > AIL|1||D_7913-X|D > AIL|2||E_7913-X|E > AIP|1||P_7913-X|P > AIP|2||T_7913-X|T > > > But as soon as I try to access the AIL field from an S13 message using > > > |replace hapi-path|/.RESOURCES/.LOCATION_RESOURCE(0)/.AIL-3|in > HL7-message|@messageId|with random value|D_*|scenario| > > I get a Java Exception: class ca.uhn.hl7v2.HL7Exception Can't find AIL as a > direct child > > So using (hapi-0.5.1.2) I have to use the old way: > > |replace hapi-path|AIL-3|in HL7-message|@messageId|with random > value|D_*|scenario| > > to access the AIL from the S13! > > > So why do you think I cannot use /.RESOURCES/.LOCATION_RESOURCE(0)/.AIL-3 > for an S13 with hapi-0.5.1.2 ? > > And why isn't hapi-0.5.1.2 backwards compatible and doing > > |replace hapi-path|AIL-3|in HL7-message|@messageId|with random > value|D_*|scenario| > > doesn't work anymore? > > And my 3-rd question: why is 7edit displaying the AIL,AIG,AIS, AIP fields > differently for S12 and S13? This difference is also present in the hapi > issue above. > > I hope you understand me better now > Mihai > > > > On Mon, Aug 9, 2010 at 3:53 PM, James Agnew <ja...@jamesagnew.ca> wrote: > >> Hi Mihai, >> >> Would you be able to provide a complete code sample illustrating this >> issue? >> >> The SIU messages (S12 through S26) all share the same structure (SIU_S12), >> so they should all work exactly the same when it comes to Terser paths. >> >> Cheers, >> James >> >> >> On Mon, Aug 9, 2010 at 8:41 AM, Mihai Barbat <miha...@gmail.com> wrote: >> >>> Hi >>> >>> Does anyone have any idea why when looking over an S12 message with 7Edit >>> Lite we get the segments AIL, AIG, AIS grouped in >>> Resources\Location_resource or personnel_resource and when I look over the >>> same segments in an S13 message they are shown as not belonging to any >>> group, just like PID,PV1..etc >>> >>> This is important because with the latest hapi to access the fields from >>> AIL. AIG segments I had to do this from Fitnesse: >>> >>> |replace hapi-path|/.RESOURCES/.LOCATION_RESOURCE(0)/.AIL-3|in >>> HL7-message|@messageId|with random value|D_*|scenario| >>> >>> But this doesn't work with an S13 message because there's no Resources >>> grouping there. >>> >>> Anyone has any idea why? I am using hapi-base-1.0.1 >>> >>> Mihai >>> >>> >>> ------------------------------------------------------------------------------ >>> This SF.net email is sponsored by >>> >>> Make an app they can't live without >>> Enter the BlackBerry Developer Challenge >>> http://p.sf.net/sfu/RIM-dev2dev >>> _______________________________________________ >>> Hl7api-devel mailing list >>> Hl7api-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/hl7api-devel >>> >>> >> >
------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________ Hl7api-devel mailing list Hl7api-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hl7api-devel
