834 EDI Companion Guide - Amazon S3
834 EDI Companion GuideIntroductionASC X12 005010 834 Enrollment Implementation Format is a standard format for electronicallyexchanging health plan enrollment data. An 834 file contains a string of data elements and each data elementrepresents a fact, such as a subscriber’s name, hire date, etc. The entire string is called a data segment. Thepurpose of this document is to describe EDI elements that are required for Teladoc Health.The EDI 834 file will be used to load eligible lives in “bulk” for the Teladoc Health service for a specificorganization or group.This file is used for adding, modifying and terming eligible lives in the Teladoc Health system.This document should not replace the ANSI 834 Implementation Guide. The contents of this documentare intended to be a supplement containing Teladoc Health specific file needs. Teladoc Health encourages you torefer to the ANSI 834 Implementation Guide for further information on any item covered or not covered by thisdocument.Usage A Teladoc Health account will be created for each new eligible life in the file. All eligible lives will have a pending account status until they have completed their account set up in theTeladoc Health system and have agreed to the Teladoc Health Terms and Conditions. Responsible Party and Provider information will be stored in the Teladoc Health System, if available. Further detail on processing logic and file processing results can be found in the Eligibility FileSpecification document.File Name CompanyName YYYYMMDD.txtoExample: ABC 20160401.txtoNo spaces are allowed in file nameGeneral Data Requirements All Teladoc Health required fields must be present in file. Teladoc Health requires that all files be transmitted through a secure file transfer connection. Each file must be PGP encrypted using the Teladoc Health encryption key.This document is Proprietary and Confidential. No part of this document may be copied or reproduced in any form or by any means without the expressprior written consent of Teladoc Health, Inc. Information in this document is subject to change. V. 9-2018Page 1
834 EDI Companion Guide The Teladoc Health secure file transfer server has IP restrictions and the IP address or addresses thatwill be connecting are required prior to receiving login credentials.Processing Requirements There are two methods available to process eligibility files. Only one method of the below should be usedfor a file.ooUnique Member id The Member ID is used to uniquely identify the member/record of a specific group withinthe Teladoc Health system. It is very important that Member ID value remain static for each member/record. When the Member ID differs from the previously sent Member ID on a subsequent file fora specific member/record, it will cause a new account to be created in the Teladoc Healthsystem.Family member id The family member id, date of birth, gender and either first name or last name are used touniquely identify the member/record of a specific group(s) within the Teladoc Healthsystem. It is very important that family member id remain static for each member/record. When the family member id differs from the previously sent family member id on asubsequent file for a specific member/record and a match was not found on familymember id, date of birth, gender and either first name or last name in Teladoc Healthsystem, it will cause a new account to be created. If more than one record is received for an eligible life, the last record will be used as the current state. For a dependent record, its corresponding primary record must exist on the same file. Responsible Party and Provider Information will be overwritten with the values provided for the member inthe most recent file.This document is Proprietary and Confidential. No part of this document may be copied or reproduced in any form or by any means without the expressprior written consent of Teladoc Health, Inc. Information in this document is subject to change. V. 9-2018Page 2
834 EDI Companion GuideField Requirements Table834 Information834 rGS04834 DescriptionInterchangeControl nformationInterchange IDQualifierInterchangeSender IDTeladoc Health InformationTP UsageValuesRR00R spaces R00R spaces RZZRInterchange IDQualifierInterchangeReceiver rInterchangeControl nt RequestedUsage IndicatorR Interchange SenderID Value ZZR201020949RyyyymmddRHHMMR R00501R001234567R0RT or PComponentElementSeparatorFunctionalGroup HeaderFunctionalIdentifier CodeApplicationSender’s CodeApplicationReceiver’s ERABCDR201020949RyyyymmddThis document is Proprietary and Confidential. No part of this document may be copied or reproduced in any form or by any means without the expressprior written consent of Teladoc Health, Inc. Information in this document is subject to change. V. 9-2018Page 3
834 EDI Companion Guide834 Information834 LoopTeladoc Health Information834 DescriptionTP HeaderBGN06HeaderBGN08Group ControlNumberResponsibleAgency CodeVersion/Release/IndustryIdentifier CodeTransaction SetHeaderTransaction SetIdentifier CodeTransaction SetControlNumberImplementation ConventionReferenceBeginningSegmentTransaction SetPurpose CodeTransaction SetReferenceIdentificationTransaction SetCreate DateTransaction SetCreate TimeTime ZoneCodeOriginalTransaction SetNumberAction 1000A1000A1000AFile EffectiveDateDate R007(File EffDate)Date TimePeriod FormatQualifierDate TimePeriodRD8RFileEffectiveDateN1Sponsor NameRN101Plan SponsorRN102Plan SponsorNameSP5This document is Proprietary and Confidential. No part of this document may be copied or reproduced in any form or by any means without the expressprior written consent of Teladoc Health, Inc. Information in this document is subject to change. V. 9-2018Page 4
834 EDI Companion Guide834 Information834 000BN1N101InsurerR1000BN102Insurer ode QualifierInsurerIdentificationCodeMember 0INS082000REF2000REF012000REF02Teladoc Health Information834 DescriptionTP UsageValuesIdentificationCode nMaxLengthTypeRequiredY or N1CharyRelationshipto Primary.(Allowedvalues 18,01,19)Relationship ofthis member tothe Primary.Teladoc willTranslate18 TO 0,01 and Gender‘M’ TO 1,01 and Gender‘F’ TO 2,19 and Gender‘M’ TO 3,19 and Gender‘F’ TO 42NumYPrimary IDThe Member IDof the primaryaccount holderfor thismember/record.This record mustbe present onlyif 2000 loopINS 'N'A-Z, a-z, 0-9(Underscore)(Hyphen) onshipCodeRYR18 (Self)MaintenanceType CodeMaintenanceReason CodeEmploymentStatus limitThis document is Proprietary and Confidential. No part of this document may be copied or reproduced in any form or by any means without the expressprior written consent of Teladoc Health, Inc. Information in this document is subject to change. V. 9-2018Page 5
834 EDI Companion Guide834 Information834 Loop834 DescriptionTP ber Groupor PolicyNumberReferenceIdentificationQualifierClient NumberTeladoc Health Entity IdentifierCodeEntity TypeQualifier PersonMember LastName2100A2100ANM105NM106NM107MemberMiddle NameMember NamePrefixMember NameSuffixRequiredHealth PlanIDThe Health PlanID of themember.A-Z, a-z, 0-950CharYEDIstandardlimitRRSNNYGroup IDR2100AType1LMember NameMember 100A2100AFieldLast NameFirst NameMiddleNameName PrefixName SuffixGroup ID thatuniquelyidentifies thegroup related tothe member50CharYEDIstandardlimitLast Name60CharYFirst NameEDIstandardlimit35CharYMiddle NameEDIstandardlimit25CharYName prefixEDIstandardlimits10CharNName suffixEDIstandardlimit10CharNEDIstandardlimitThis document is Proprietary and Confidential. No part of this document may be copied or reproduced in any form or by any means without the expressprior written consent of Teladoc Health, Inc. Information in this document is subject to change. V. 9-2018Page 6
834 EDI Companion Guide834 Information834 Loop834 DescriptionTP eR2100APERS2100APER01ContactFunction CodeInsured G032100ALUI2100ALUI012100ALUI02Teladoc Health me PhoneRHPCommunicationNumberQualifierWork Phone/Cell graphicsDate TimePeriod FormatQualifierMember Code QualifierLanguage CodeSRFieldDescriptionMaxLengthTypeRequiredmember idThe ID thatuniquelyidentifies theMember/recordin the Teladocsystem.**This valuemust not changefor themember/recordon subsequentfiles.A-Z, a-z, 0-9(Underscore)(Hyphen)60CharYHome Phone12Char(Parsed byTeladoc)NWorkPhone/Cellphone12Char(Parsed rNRBirth Date10DateYRGenderDate of birthYYYYMMDDGender (AllowedValues M, F, U)1CharYLanguage1CharE – EnglishS – SpanishNRRRD8LELanguageThis document is Proprietary and Confidential. No part of this document may be copied or reproduced in any form or by any means without the expressprior written consent of Teladoc Health, Inc. Information in this document is subject to change. V. 9-2018Page 7
834 EDI Companion Guide834 Information834 401834 DescriptionTP alifierEntity TypeQualifier PersonMemberMailingAddressMail AddressLine1SMail AddressLine2MemberMailing City,State, ZipMail City NameTeladoc Health eRequiredAddress Line1The mailingaddress of theprimary accountholder. **Mustbe enclosed indouble quotes iffield contains acomma.The mailingaddress of theprimary accountHolder. **Mustbe enclosed indouble quotes iffield contains CharY3CharNSRSAddress N402Mail State CodeRState2100CN403Mail PostalCodeRZip2100CN404Country ustodialParentEntity IdentifierCodeEntity TypeQualifier PersonRS3R1The mailing cityof the primaryaccount holder.The mailing zipof the primaryaccount holder.XXXXX or XXXXXXXXX format.Default USAThis document is Proprietary and Confidential. No part of this document may be copied or reproduced in any form or by any means without the expressprior written consent of Teladoc Health, Inc. Information in this document is subject to change. V. 9-2018Page 8
834 EDI Companion Guide834 Information834 Loop2100F2100F834Segment/ElementNM103NM104834 DescriptionTP UsageCustodialParent LastNameRCustodialParent FirstNameRContactFunction CodeContactFunction 03HealthCoverageMaintenanceType CodeInsurance LineCodeHealthCoverage DatesDate TimeQualifierDate TimePeriod FormatQualifierBenefit BeginDate2300DTPS2300DTP012300DTP02HealthCoverage DatesDate TimeQualifierDate TimePeriod FormatQualifier2300DTP03Benefit EndDateTeladoc Health iredLast NameLast name of theresponsibleparty.60charNCharNFirst NameRPQRTER030RHLTFirst name of imitHome PhoneFor responsibleparty12Char(Parsed byTeladoc)NStart DateDate in whichmember iseligible forTeladoc service.10Date(CCYYMMDDwill beformatted toyyyy-mm-dd)YTerm DateDate in whichmember is nolonger eligiblefor TeladocHealth service.10Date(CCYYMMDDwill beformatted toyyyy-mm-dd)NRR348RD8RR349RD8RThis document is Proprietary and Confidential. No part of this document may be copied or reproduced in any form or by any means without the expressprior written consent of Teladoc Health, Inc. Information in this document is subject to change. V. 9-2018Page 9
834 EDI Companion Guide834 Information834 0NM1012310NM1022310NM10323102310NM104NM105834 DescriptionTP UsageHealthCoveragePolicy ntificationRHealthCoveragePolicy ntificationRProviderInformationProv AssignedNumberProvider NameSRTeladoc Health InformationValuesReportingCategory 1ReportingCategory 1 value**Must beenclosed indouble quotes ifline contains acomma.150ReportingCategory 2ReportingCategory 2 value**Must beenclosed indouble quotes ifline contains acomma.150ProviderNameName of theprovider.60NM108RP3R1 or 2Prov First NameSProv ID CodeQualifierRequiredTeladoc willconcatenateNM104,NM105,NM103.Note thatthe PCP isoften aclinic, inwhich caseonly,Organizationin whichcase only,OrganizationName(NM103) willbe ame of theprovider.Name of 10Type1Prov Entity IDCodeProv EntityType QualifierProv Last Nameor OrganizationNameProv This document is Proprietary and Confidential. No part of this document may be copied or reproduced in any form or by any means without the expressprior written consent of Teladoc Health, Inc. Information in this document is subject to change. V. 9-2018Page 10
834 EDI Companion Guide834 Information834 Loop834 DescriptionTP Usage2310834Segment/ElementNM109Prov ID CodeS2310NM110R2310N32310N301Prov EntityRelationshipCodeProviderAddressProv AddressLine12310N302Prov AddressLine2Teladoc Health iredProvider NPINationalProviderIdentifier10NProviderAddress 1The address ofthe s 2The address ofthe provider.EDIstandardlimit2310N42310N401Provider City,State, Zip CodeProv City NameSRProvider CityThe city of theprovider.30NEDIstandardlimit2N2310N402Prov State CodeRProviderStateThe stateabbreviation ofthe provider.2310N403Prov Zip CodeRProvider Zip10Teladoc willload DirectlyN2310N404Prov CountryCodeSProviderCountryCodeThe zip of theprovider. XXXXXor XXXXX-XXXXformat.Default erPhoneXXX-XXX-XXXXformat12Teladoc willformatN2310PER052310PER06Provider FaxXXX-XXX-XXXXformat12Teladoc ons NumbersInformationContactCommunicationNum QualifierCommunicationNumCommunicationNum QualifierCommunicationNumTransaction SetTrailerNumber ofincludedSegmentsTrailerSE02Transaction SetControl NumRICRTERSFXSRRRThis value is usedfor validatingsegment countsreceived in File.4567Must MatchST02This document is Proprietary and Confidential. No part of this document may be copied or reproduced in any form or by any means without the expressprior written consent of Teladoc Health, Inc. Information in this document is subject to change. V. 9-2018Page 11
834 EDI Companion Guide834 Information834 E02TrailerIEATrailerIEA01TrailerIEA02834 DescriptionTP UsageFunctionalGroup TrailerNumber ofTransactionSets IncludedGroup ControlNumberRTeladoc Health ypeRequiredMust matchGS06RNumber R1R001234567Must MatchISA13This document is Proprietary and Confidential. No part of this document may be copied or reproduced in any form or by any means without the expressprior written consent of Teladoc Health, Inc. Information in this document is subject to change. V. 9-2018Page 12
834 EDI Companion GuideSample DataISA*00**00**ZZ*ABCD*ZZ*201020949*170308*1932* *00501*000000103*0*T*: 0A1 ST*834*0103*005010X220A1 BGN*00*714*20170308*1906*PT*00001**4 DTP*007*D8*20170201 N1*IN*ABCD*FI*943226498 INS*Y*18*030*XN*A***AC REF*0F*1000 REF*17*10291 REF*1L*1234 NM1*IL*1*Jason*Baker*D***34*1000 PER*IP**HP*2144324143 DMG*D8*19780728*F**H LUI*LE*SPA**6 NM1*31*1 N3*123 Main St N4*Dallas*TX*75254 NM1*S3*1** PER*PQ**TE* HD*030**HMO*NDPH MNHC MC CHILD18*IND****N DTP*348*D8*20170601 DTP*349*D8*20180530 REF*XX1*CHN REF*XX2*SOUTH LX*1 NM1*P3*1*Tom*Weisberg*A***SV*2131014444*72 N3*123 Preston rd N4*Dallas*TX*75254 PER*IC**TE*2344569996*FX*2344569997 COB*P**1 REF*6P*E*Group A*Small Bussiness REF*ZZ*Sr Accountant INS*N*18*030*XN*A***AC REF*0F*1000 REF*17*10291 REF*1L*1234 NM1*IL*1*Emily*Baker****34*1001 L.COM DMG*D8*19951007*F**ALUI*LE*ENG**6 NM1*31*1 N3*123 Main St N4*Dallas*TX*75254 NM1*S3*1** PER*PQ**TE* HD*030**HMO*DPH COPC MC MCE*IND****N DTP*348*D8*20170601 DTP*349*D8*20180530 REF*XX1*CHN REF*XX2*SOUTH LX*1 NM1*P3*1*Tom*Weisberg****SV*2131014444*72 This document is Proprietary and Confidential. No part of this document may be copied or reproduced in any form or by any means without the expressprior written consent of Teladoc Health, Inc. Information in this document is subject to change. V. 9-2018Page 13
834 EDI Companion GuideN3*123 Preston rd N4*Dallas*TX*75254 PER*IC**TE*2344569996*FX*2344569997 COB*P**1 REF*6P*E*Group A*Health care REF*ZZ*Developer SE*1007*0103 GE*1*103 IEA*1*000000103 File typesEligibility new files /Eligibility subsequent files fall into two classes:The client decides which type of file class to be sent. Full Files – This type is used as both New and Subsequent. These files will include allmembers. The subsequent files sent should include all primary and dependents that shouldhave access to Teladoc Health services. Members not included on the file may be termed byabsence. The decision to term by absence should be made during implementation by client. Change Files –This type is only used after a Full File is loaded. These files will include newmembers and any members with information changes.Additional informationAccount Setup Restrictions (Primaries) Individuals will not be allowed to create accounts through the Teladoc website or Call Center unlessthey are sent in eligibility files and successfully processed. For this reason, it is important to reviewany errors detailed in the results file to avoid customer service issues.Account Setup Restrictions (Dependents) It is suggested to send dependents records in file only if information of all dependents of the primary isavailable. Primary members can be allowed to create or cancel accounts for their dependents throughthe Teladoc website or Call Center. Allowing primary account holders to add dependents is permission based and must be establishedduring the implementation process. When a primary member is cancelled via the file all dependentsunder that primary member will also be cancelled.Individual Information Changes To prevent problems with customer information being overwritten by information contained in files,individuals registered through a file will not be allowed to alter the required demographic fields in thefile layout. Any changes to this information must be sent in a file. Non-required information is setupon account creation via the auto-eligibility files and can be updated by the member at any time.This document is Proprietary and Confidential. No part of this document may be copied or reproduced in any form or by any means without the expressprior written consent of Teladoc Health, Inc. Information in this document is subject to change. V. 9-2018Page 14
834 EDI Companion GuideAcknowledgement After a file is processed, a results summary email will be sent to distribution list provided by the Client. Any record with missing required field or duplicate member record with in the file will be rejected andstored. The file name will be appended with “.results” at the end of the file name and stored.o Example: ABC 20160401.csv file will be named as ABC 20160401.csv.results If record count of missing required fields exceeds the threshold, the file processing will be stopped andthe file name will be appended with “.failed” at the end of the file name and stored. A header row is counted towards error threshold.o Example: ABC 20160401.csv file will be named as ABC 20160401.csv.failedExample Results Summary EmailThis email is to let you know that file ABC 20160401.csv was processed by Teladoc Health on 04-01-16 04:38:54 with aresulting status of processed successfully. A results file will be available on the server where you placed your file. Asummary is provided below. Individual error counts listed below may not add up to total number of error records as asingle record may have multiple errors:Total Members: 427Additions: 0Updates: 426Terminations by absence: 1Total member errors: 550Group id error: 1Member id error: 1Account holder id error: 1First name error: 1Last name error: 1Gender error r: 1Date of birth error: 1Start date error: 1 following text will be included in the email if # of errors exceeds 201 The threshold of 200 errors has been exceeded inthis email. Please refer to the results file on the server where you placed your file for full details of the rows with errors.John, Jones, missing or invalid group idClive, Dujon, missing or invalid member idClive,Dujon, missing or invalid account holder id,Jones, missing first nameJohn, , missing last nameClive, Lloyd, missing or invalid genderClive, Ben, missing or invalid date of birthClive, Ben, missing start dateClive, Dujon, primary member is under 18 years oldClive, Sally, Primary ID for this dependent is not included on the file or the account holder id has an errorThis is a system generated email. Please do not reply to this email. If you have questions, please email dataservices@teladoc.comThis document is Proprietary and Confidential. No part of this document may be copied or reproduced in any form or by any means without the expressprior written consent of Teladoc Health, Inc. Information in this document is subject to change. V. 9-2018Page 15
834 EDI Companion Guide Introduction ASC X12 005010 834 Enrollment Implementation Format is a standard format for electronically exchanging health plan enrollment data. An 834 file contains a string of data elements and each data element represents a fact, such as a subscriber’s name, hire
4010 EDI documents (note EDIFACT transaction sets will be required by Amazon EU divisions): EDI 753 - Request for Routing Instructions EDI 855 - PO Acknowledgement EDI 754 - Routing Instructions EDI 856 –Advance Ship Notice EDI 810 - Invoice EDI 860 –PO Change Request EDI 846 - Inventory Advice/Update EDI 865 –PO Change Seller
This Companion Guide provides information about the 834 Enrollment file that is specific to HCA and HCA trading partners. It will include both the 834 Audit and 834 Update. This Companion Guide is intended for trading partner use in conjunction with the ASC X12 TR3 834
4010 EDI documents (note EDIFACT transaction sets will be required by Amazon EU divisions): EDI 753 - Request for Routing Instructions EDI 855 - PO Acknowledgement EDI 754 - Routing Instructions EDI 856 – Advance Ship Notice EDI 810 - Invoice EDI 860 – PO Change Request
collection of EDI data is received in a batch. The batch of EDI data includes a plurality of EDI documents and each of the plurality of EDI documents has at least one EDI transaction corresponding to a transaction type. The EDI transactions included in the EDI documents are identified by decoding the received EDI data according to EDI standards.
1. What is EDI? 2. What is the 'Omni-hannel' 3. Omni-Channel EDI solutions 4. Where does EDI fit into the marketplace? 5. Third Party Logistics (3PL) EDI 6. Online Retailers and CommerceHub EDI 7. eCommerce Platform EDI 8. B2BGateway EDI and QuickBooks Online 9. Pricing 10. Customer Service 11. B2BGateway Fact Sheet & Trading Partners 12 .
TrueCommerce EDI Buyer's Guide As supply chains become more complex, EDI offers the technology . and provides all the components required for EDI, such as mapping, translation, and connectivity to trading partners. . h EDI 940 - Warehouse Shipping Order h EDI 945 - Warehouse Shipping Advice h EDI 997 - Functional Acknowledgement
MAPPING Involves transforming an EDI document into another format (such as XML, a flat file, a delimited file, etc.) TRANSLATION The process of accepting in bound EDI data, or preparing an outbound file for transmission COMMUNICATIONS Refers to the transmission of the EDI transaction Accepted. The EDI message conforms to all agreed upon EDI .
Accounting information and managerial work. Accounting, Organizations and Society, 35 (3), 301-315. ABSTRACT . Despite calls to link management accounting more closely to management (Jonsson, 1998), much is still to be learned about the role of accounting information in managerial work. This lack of progress stems partly from a failure to incorporate in research efforts the findings regarding .
