I am using Chameleon to create HL7 file. Everything was working fine until I encountered large number of OBX segments in in one group. My problem is sequence in which my vmd populating hl7 file with OBX segments is not correct. If I have 10 sequential OBX segments in one group, OBX with setId 6-10 are above then those having sequence from 1-5. In DB tables data is present in sequential manner, now I dont know how to configure my vmd to get those segments im ascending setIds.
Right now I am getting something like
while I want
can someone help me how to deal with it?
I have figured out the reason but not able to find solution yet.
Problem is I have added a group for repeating OBX. As Chameleon itself create columns of group, it creates three columns (message_id(varchar2), parent_id(varchar2), group_id(varchar2)) within a group. Now all of these are of type VARCHAR2. I have to add a row to group whenever I add in OBX table. Now when total OBX in one message increase to 10, ‘group_id’ column of Group table starts rearranging itself on basis of its varchar2 type
In GROUP table its group_id arrangement is something like
and the same way vmd capture OBX rows. That’s why my hl7 file carries incorrect sequence of OBX. Now I cant change the arrangement in which data is stored in tables after insertion, is there any way to customize selection of data into hl7 file, I mean I can use ‘order by’ in its default query?
You must be logged in to reply to this topic.
Please don't hesitate to take anonymous feedback survey or leave us a comment.