| benf |
| Newbie |
|
| Phoenix, AZ |
|
|
| None Specified |
|
| Friday, February 22, 2008 |
| Friday, April 22, 2011 4:02:05 PM |
9
[0.05% of all post / 0.00 posts per day] |
|
Well stated Robert and I completely agree with your thoughts and suggestions. I was able to modify the config and .837 files to meet my needs but if I ever have to make changes it's very time consuming. Most of the time I find myself just making changes and saving it to see if it works, if it does I move on usually not knowing what I really did to fix it. With 5010 coming around I'm not looking forward to having to change/recreate these again.
I really like Mapforce, it's an excellent product, easy to use, and has saved me a ton of time. But I'd really like to see these improvements too!
|
I'm having trouble mapping results from an EDI 837 HIPAA claim file. If the subscriber is the patient it works great, but in cases where the patient is not the subscriber (loop 2000C) it's not reading the patient data. The default 837.Config file provided by Altova does not contain the 2000C loop which partially explains the problem, but several attempts by me to manually add in this loop to the 837.Config file have failed.
I did submit a ticket to Altova tech support regarding my problem, and they've been great at keeping in touch with me, but so far we haven't had any success finding an answer.
Before I go any further with the details of the problem I was hoping someone here has experience with MapForce and processing 837 EDI claim files. If you do I would really appreciate some assistance. Please reply here if you might be able to help out.
|
|
Thanks for the reply. I hadn't read the column on the right so will submit something formal to them on this. As for your suggestion, I'm doing the insert from the preview. I'm far from a programmer but did generate the code and compiled it successfully in .net, but the end result wasn't much faster than doing it from within MapForce.
|
|
Support? Hello?
|
I'm mapping a fairly large EDI/X12 formatted file to an Access database. Previewing the map takes awhile, but the actual map execution where it writes the values to the Access database takes around 30 minutes. I checked the mapping output and there's approximately 34,000 "insert into" statements.
Was wondering if anyone else has had issues with slow mapping and if there's anything I can do to speed things up. I know that's probably a hard question to answer without seeing the actual map but am hoping someone may have experienced this already and has some suggestions.
Below is a sample of the mapping ouput:
INSERT INTO [tbl_271_Incoming_Benefits] ([TraceNbr],[BenefitStatus],[BenefitCvgLevel],[ServiceCode],[InsCode],[PlanCvgDesc],[RefIDQualifier],[EligBenefitID],[PlanSponser],[DateTimeQualifier],[DateTimeFormat],[EligBenefitDate],[Healthplan],[ValidRequestInd],[RejectReason],[FollowUpAction],[Message])
VALUES (23377,'6','IND','30','MC','CATEGORICAL ELIG',NULL,NULL,NULL,'307','RD8','20070301-20071031',NULL,NULL,NULL,NULL,NULL)
INSERT INTO [tbl_271_Incoming_Benefits] ([TraceNbr],[BenefitStatus],[BenefitCvgLevel],[ServiceCode],[InsCode],[PlanCvgDesc],[RefIDQualifier],[EligBenefitID],[PlanSponser],[DateTimeQualifier],[DateTimeFormat],[EligBenefitDate],[Healthplan],[ValidRequestInd],[RejectReason],[FollowUpAction],[Message])
VALUES (23377,'6','IND','30','MC','CATEGORICAL ELIG',NULL,NULL,NULL,'318','D8','20070429',NULL,NULL,NULL,NULL,NULL)
INSERT INTO [tbl_271_Incoming_Benefits] ([TraceNbr],[BenefitStatus],[BenefitCvgLevel],[ServiceCode],[InsCode],[PlanCvgDesc],[RefIDQualifier],[EligBenefitID],[PlanSponser],[DateTimeQualifier],[DateTimeFormat],[EligBenefitDate],[Healthplan],[ValidRequestInd],[RejectReason],[FollowUpAction],[Message])
VALUES (23377,'6','IND','30','HM','UNDOC/FFS/EM',NULL,NULL,NULL,'307','RD8','20070429-20071130','FEDERAL EMERGENCY SERV',NULL,NULL,NULL,'1116 TANF EXPANDED 21-44 MALE')
INSERT INTO [tbl_271_Incoming_Benefits] ([TraceNbr],[BenefitStatus],[BenefitCvgLevel],[ServiceCode],[InsCode],[PlanCvgDesc],[RefIDQualifier],[EligBenefitID],[PlanSponser],[DateTimeQualifier],[DateTimeFormat],[EligBenefitDate],[Healthplan],[ValidRequestInd],[RejectReason],[FollowUpAction],[Message])
VALUES (23377,'R','IND','30','C1',NULL,'1L','NO POLICY ID','INACTIVE','290','RD8','20071024-20071024',NULL,NULL,NULL,NULL,NULL)
-->>> OK. 1 row(s).
|
Never mind, I figured this out after re-searching the forum. I had to connect the DTP segment to the root of my output database instead of connecting from the 2110 loop level.
|
I'm working with an inbound HIPAA 271 transaction file and in loop 2110C, segment DTP can occur multiple times within that loop. For example, one segment will show eligibility begin date, the next segment shows the eligiblity end date. Here's a specific example:
HL{5{2{22{0~
TRN{1{61050{9876543210~
NM1{IL{1{LASTNAME{FIRSTNAME{{{{MI{A12345678~
N3{2118 W STREET NAME~
N4{PHOENIX{AZ{85009{{CY{MARICOPA~
DMG{D8{19751013{M~
DTP{472{RD8{20071109-20071109~
EB{1{IND{30{MC{CATEGORICAL ELIG~
DTP{307{D8{20070801~
DTP{318{D8{20071215~
I'm using the default 271.config file and when the above is run through it the only segment I'm getting back is the one with qualifier 318 and date of 20071215... it appears to ignore the one above it.
The first part of loop 2110 in the 271.config file looks like this:
<Group name="Loop2110" maxOccurs="unbounded" minOccurs="0">
<Segment ref="EB"/>
<Segment ref="HSD" minOccurs="0" maxOccurs="9"/>
<Segment ref="REF" minOccurs="0" maxOccurs="9"/>
<Segment ref="DTP" minOccurs="0" maxOccurs="20"/>
As you can see, DTP has a maxOccurs value > 1 so I'm not sure what's going on. I've tried modifying the 271.config file several different ways but can't get this to work correctly.
Ideas anyone?
|
|
