{"id":13299747,"url":"https://github.com/freight-trust/spdx-asc-x12","last_synced_at":"2026-03-04T11:01:08.369Z","repository":{"id":103603283,"uuid":"297790167","full_name":"freight-trust/spdx-asc-x12","owner":"freight-trust","description":"ASC X12 License information","archived":false,"fork":false,"pushed_at":"2020-10-17T03:58:42.000Z","size":28,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":2,"default_branch":"master","last_synced_at":"2025-02-26T10:19:10.509Z","etag":null,"topics":["asc","edi","x12"],"latest_commit_sha":null,"homepage":"","language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"other","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/freight-trust.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2020-09-22T22:44:54.000Z","updated_at":"2020-10-17T03:58:44.000Z","dependencies_parsed_at":"2023-03-13T15:07:11.909Z","dependency_job_id":null,"html_url":"https://github.com/freight-trust/spdx-asc-x12","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/freight-trust/spdx-asc-x12","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/freight-trust%2Fspdx-asc-x12","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/freight-trust%2Fspdx-asc-x12/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/freight-trust%2Fspdx-asc-x12/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/freight-trust%2Fspdx-asc-x12/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/freight-trust","download_url":"https://codeload.github.com/freight-trust/spdx-asc-x12/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/freight-trust%2Fspdx-asc-x12/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":30078405,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-03-04T08:01:56.766Z","status":"ssl_error","status_checked_at":"2026-03-04T08:00:42.919Z","response_time":59,"last_error":"SSL_connect returned=1 errno=0 peeraddr=140.82.121.5:443 state=error: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["asc","edi","x12"],"created_at":"2024-07-29T17:37:51.508Z","updated_at":"2026-03-04T11:01:08.348Z","avatar_url":"https://github.com/freight-trust.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"# ASC X12\n\n\u003e source: x12.org/license \n\n**The License has only been formated to make it easier to read, no other modifications**\n\n## X12 License \n\nAll X12 work products are copyrighted. Any use of any X12 work product must be\ncompliant with US Copyright laws and X12 Intellectual Property policies.\n\nIntroduction\n============================\nX12 has developed standards and associated products to facilitate the\ntransmission of electronic business messages for over 40 years. X12 manages the\nexclusive copyright to all standards, publications, and products, and such works\ndo not constitute joint works of authorship eligible for joint copyright.\n\nAll X12 products are subject to this IP policy, including published and draft\nworks.\n\nX12 is the only organization authorized to grant permission for use of X12\nproducts. Users of all X12 products should make sure that they understand the\npermissible uses, as well as the limitations on such usage, as outlined below.\n\nFair Use\n============================\nU.S. Copyright laws and X12 Intellectual Property (IP) policies apply to the use\nand distribution of any X12 product, including published and draft works. X12's\ncopyrighted products, include but are not limited to, standards, technical\nreports, guidelines, workbooks, segment directories, element directories, data\nelement dictionaries, table data, schema, and mapping instructions.\n\nAny use of X12 IP is predicated on the party holding an active license\npermitting the specific use of the associated X12 product's content. From time\nto time, X12 may make certain products available for public use at no cost. U.S.\nCopyright laws and these IP policies shall apply to such products.\n\nIf written permission is required for a use of copyrighted content, distribution\nof an artifact(s) using the X12 copyrighted content is prohibited until X12\ngrants permission for the use in writing. Once permission for use of X12 content\nhas been granted, an organization may distribute a permitted artifact to its\ntrading partners via printed document, electronic document or a website.\n\nWritten permission of the copyright holder is required in the following\nsituations:\n\n* For any use that includes distribution of information based on the copyrighted\ncontent outside the corporate structure of the organization holding the active\nlicense, regardless of the method of distribution or format of the distributed\ninformation.\n\n* For any use that reproduces portions of the product, excepting short citations\nintended as support for comment, news reporting, criticism, teaching or\nscholarship, or research.\n\n* For any other use not expressly allowed as not requiring written permission.\nProvided that a proper citation is included, written permission is not required\nin the following situations:\n\n* For internal purposes, that is for use within the corporate structure of the\norganization holding the active license\n\n* To reproduce short citations intended as support for comment, news reporting,\ncriticism, teaching or scholarship, or research.\n\n* Posting of X12's copyrighted products on another organization's public website\nis strictly prohibited.\n\n* Direct distribution of X12's copyrighted products by any organization or\nindividual to another organization or individual is strictly prohibited.\n\n* Draft versions of X12 products may only be used by X12 members, and then only\nfor the purposes of official X12 collaboration and internal discussion or\nevaluation within the member's own organization. Distribution of X12 drafts\noutside of the member's own organization and any use of the IP intended for\ndistribution outside of the member's own organization are strictly forbidden.\n\nRequesting Permission for External Use of X12 Work Products\n===================================================================\n\nAll parties requesting permission to use X12 copyrighted products under X12's\nFair Use policies must follow the procedures listed below. X12 will handle\nrequests and related artifacts as confidential, available only to designated\nreviewers. An organization may have up to three (3) active permission requests\nat any time. If you have more than 3 artifacts to submit, please allocate time\nfor multiple review cycles.\n\n1. Review X12's Fair Use policies and ensure the request falls under the parameters\nof Fair Use. If so, use the instructions in the Request Permission Form section\nfound at the bottom of this page to submit a request to reproduce or use content\nfrom a copyrighted X12 product in a proprietary artifact. An advance copy of\neach artifact must be submitted with the request form via email to ip@x12.org\nwith the Subject line of \"Request to Use X12 Copyrighted IP: [[YOUR COMPANY\nNAME]].\"\n\n2. X12 will review your submission and ensure that the use of content from an X12\nproduct is compliant with applicable X12 policies, generally accurate in the\ncontext presented, and that style requirements have been met.\n\nNOTE: The review of submitted artifacts is focused on X12 IP use and compliance\nwith X12 policy. The review does not include evaluation of compliance with any\napplicable State or Federal mandate, including HIPAA, or evaluation of the\naccuracy or validity of the X12 products within the context of your submission.\n\n3. Following review of a submitted artifact, X12 will make a determination of\npermission.\n\nIf permission is granted, the requesting party may use or cite the X12 content\nunder the following conditions:\n\nPermission is for the specific artifact submitted and for the specific use cited\nin the request. Permission is not granted for other artifacts, including\nrevisions to the approved artifact, or for other uses.\n\nThe artifact must include a statement referencing X12's copyright and that\nexplicit permission to use or cite the material was granted for this use.\nPermission is not transferable.\n\nThe preceding conditions are continuing, and X12 reserves the right to revoke\nthe permission at any time if the preceding conditions are not met\nIf permission is not granted, the reasons will be conveyed to the requesting\nparty and the requesting party will be given an opportunity to revise and\nresubmit the artifact or the use statement as necessary to meet the requirements\nfor use.\n\nGuidance for Use of X12 Content in Artifacts Based on X12 TR3s\n===========================================================================\n\nMany organizations produce artifacts which contain proprietary instructions for\ncreating transactions based on an associated X12 Type 3 Technical Report (TR3),\nalso known as an X12 Implementation Guide (IG). Such artifacts are often called\nCompanion Guides. These artifacts must adhere to U.S. Copyright laws and X12 IP\npolicies.\n\nThis section outlines the requirements for artifacts that use or are based on\nthe contents of TR3s. These requirements supplement, but do not replace or\noverrule, the associated copyrights and X12's Fair Use policies. Artifacts must\nconform to these restrictions to avoid infringing on X12 copyrights and related\nintellectual property rights.\n\nIt is recognized that artifacts may also include information that is unrelated\nto X12 intellectual property; X12 has no jurisdiction over that portion of an\nartifact and does not review that information during an IP Review.\n\nContent Guidelines\n============================\n\nSuch Artifacts must:\n\nAbide by US Copyright Law.\n\nAbide by X12's Fair Use and Copyright policies.\n\nCorrectly identify the X12 organization and any referenced X12 products.\nInclude a statement about where to purchase a license for the underlying TR3 and\nthe associated URL.\n\nExample: The X12 TR3 that details the full requirements for this transaction can\nbe licensed at https://x12.org/licensing.\n\nInclude a disclaimer that the TR3 retains ultimate authority over the\nrequirements of the transmission.\n\nExample: Every effort has been made to ensure consistency between this document\nand the X12 TR3. However, if there is a discrepancy between the documents, the\nX12 TR3 is the final authority.\n\nBe used in conjunction with an associated X12 TR3; they must not be stand-alone\nrequirements documents\n\nConform to all the requirements of the associated TR3.\nUse the full official name, including the unique identifier, at the first\nreference to any TR3.\n\nExample: X12/006020X267 Health Care Claim Status Request and Response (276/277).\nIf a shortened TR3 title will be used in the Artifact, it may either be the\nunique identifier or the TR3 name.\n\nExample: 006020X267, 6020X212 or Health Care Claim Status Request and Response.\nOnce permission for use of X12 copyrighted material has been granted, the\nArtifact must include a statement at the beginning of the document noting \"X12\nhas granted express permission for use of X12 copyrighted materials within this\ndocument.\"\n\nSuch Artifacts may:\n\nInclude proprietary information or instructions that clarify the TR3\ninstructions for specific trading partners.\n\nClarify a TR3 example, based on proprietary instructions.\nAdd examples specific to proprietary instructions.\n\nClarify specific processing intentions related to TR3 requirements\n.\nCodes allowed in the TR3 must be accepted if transmitted however the Artifact\nmay note that one or more codes from the TR3 code list are preferred or not\nprocessed.\n\n\"Not processed\" means it will not be recognized in internal processing, it does\nnot mean the transaction can be rejected if the code is transmitted.\n\"Preferred\" means that internal processes require a specific value, it does not\nmean the transaction can be rejected if the specified code is not transmitted.\nClarification of the use of loops/segments/elements in the TR3 identified by\nsituational rules stating trading partner requirements control usage:\nExamples of such situational rules:\n\n\"Required when the payer's adjudication is known to be impacted\"\n\n\"Required when such transmission is required under the insurance contract\"\nIndicate the number of repetitions which will be applied in the transaction\nprocessing application for loops or segments without repetition limitations in\nthe TR3.\n\nIdentify trading partner information necessary to initiate or enable the\ncommunications between trading partners.\nExample: \"GS02 – send your TPID in this element\".\n\nInclude information from X12 Requests for Interpretation (RFIs) as a reference\nfor trading partner specific instructions as long as the RFI is explicitly\nreferenced.\n\nArtifacts must not:\n\nReplicate the information presented in the associated TR3.\n\nContradict, countermand or duplicate any requirement of the associated TR3.\n\nContain material duplication of a section of the associated TR3, unless\npermission for the citation has been granted.\n\nAdd, modify or delete any requirements, including loop, segment or element\nnames, notes or rules, examples, appendix, or code list subsets from Section 2\nof the associated TR3.\n\nUse the unique identifier listed in GS08 unless the transaction conforms to the\nrequirements documented in the associated TR3, within the parameters of the\nCompliance in X12 document.\n\nAdd, modify or disallow any defining, explanatory, or clarifying content (within\nSection 1), example (within Sections 2 and 3) or Appendix (within Section 4).\nInclude tutorial information about X12 syntax, the underlying transaction set or\nrelated transaction sets.\n\nInclude tutorial information about the use or interpretation of a TR3.\n\nGuidance for Use of X12 Materials in Artifacts Based on Any Other X12 Product\nMany organizations produce artifacts which contain proprietary instructions for\ncreating transactions based on an X12 product. Such artifacts must adhere to\nU.S. Copyright laws and X12 IP policies.\n\nA separate section outlines the requirements for artifacts based on X12 TR3s.\nThis section outlines the requirements for artifacts that use or are based on\nall other X12 products. These requirements supplement, but do not replace or\noverrule, the associated copyrights and X12's Fair Use statement. Artifacts must\nconform to these restrictions to avoid infringing on X12 copyrights and related\nintellectual property rights. Artifacts may also include information that is\nunrelated to X12 products; X12 has no jurisdiction over that portion of an\nartifact and does not review that information during an IP Review.\n\nArtifact Distribution\n============================\n\nBy definition, artifacts are intended for distribution outside of the developing\norganization. Once permission for use of X12 products has been granted; an\norganization may distribute an artifact to its trading partners via printed\ndocument, electronic document or via a website.\n\nNo organization may post X12 Standards, Technical Reports, Guidelines,\nWorkbooks, Segment Directories, Element Directories, Data Element Dictionaries,\nTable Data, Schema or any other X12 product on its website for public reference\nat any time.\n\nContent Guidelines\n============================\n\nArtifacts must:\n\nAbide by US Copyright Law.\n\nAbide by X12's Fair Use and Copyright statements.\n\nUse the full name \"X12\" to identify the X12 organization or products.\nBe used in conjunction with an associated X12 product; they must not be\nstand-alone requirements documents.\n\nInclude a statement about where to purchase the underlying X12 product and the\nassociated URL.\n\nExample: The X12 Standard that details the full requirements for this\ntransaction is available at https://nex12.org/index.php/licensing.\nConform to all the requirements of the associated X12 product.\nUse the full official name at the first reference to any X12 product.\nExample: X12 006020\nOnce permission for use of X12 copyrighted material has been granted, the\nartifact must include a statement at the beginning of the document noting\n\"Express permission to use X12 copyrighted materials within this document has\nbeen granted.\"\nArtifacts may:\n\nInclude proprietary information or instructions that clarify the X12\ninstructions.\nAdd examples specific to a proprietary implementation.\nAdd specific processing instructions not otherwise contained in the X12 product.\nIndicate the number of repetitions which are allowed in a proprietary\nimplementation.\nIdentify trading partner information necessary to initiate or enable the\ncommunications between trading partners.\nInclude information from X12 Requests for Interpretation (RFIs) as a reference\nfor trading partner specific instructions as long as the RFI is explicitly\nreferenced.\n\nArtifacts must not:\n\nReplicate the information presented in the associated X12 product.\n\nContradict, countermand or duplicate any requirement of the associated X12\nproduct.\n\nContain material duplication of a section of the associated X12 product, unless\npermission for the citation has been granted.\n\nInclude tutorial information about X12 syntax, the underlying transaction set or\nrelated transaction sets.\n\nInclude tutorial information about the use or interpretation of an X12 product.\nGuidance for Citation of X12 Content in Artifacts\nOrganizations may on occasion wish to produce artifacts which contain a limited\nnumber of exact quotes of X12 copyrighted products. These artifacts must adhere\nto U.S. Copyright laws and X12 IP policies.\n\nThis section outlines the requirements for citing, or exactly quoting, X12\ncopyrighted content in an artifact. These requirements supplement, but do not\nreplace or overrule, the associated copyrights and X12's Fair Use statement.\nArtifacts must conform to these restrictions to avoid infringing on X12\ncopyrights and related intellectual property rights.\n\nArtifacts may also include information that is unrelated to X12 copyrighted\ncontent, X12 has no jurisdiction over that portion of the artifact and does not\nreview that information during an IP Review.\n\nCitation Format\n============================\n\nThe basic style below is adapted from the Modern Language Association (MLA)\nStyle Manual and by convention includes line breaks and an indent for each\nsuccessive line:\n\nAuthor Name. \"Title: Subtitle, Figure number,\nif appropriate, Segment ID - Name, if appropriate.\"\nTitle of Book, identifier.\nPublisher, Date of publication. \u003cURL\u003e. Page Number(s) [if applicable].\n  \n  * Examples\n  \n    If someone wants to reproduce figure 1.1 of 006020X258, the choices are:\n\n    Place a footnote reference number in relation to the reproduced figure and\n    place the following as the footnote, or place the following directly below the\n    figure:\n\n    Accredited Standards Committee X12, Insurance Subcommittee, X12N. \"1.4.1\n    Information Flows, Fig. 1.1.\" Health Care Claim Payment/Advice (835),\n    006020X258. X12 Incorporated, June 2012. \u003chttp: //www.x12.org\u003e. 3.\n\n    Or place in-line with the text an abbreviated citation:\n\n    The 835 presents an \"Information Flow\" figure, reproduced below,\n    illustrating the flow of information from payer to payee (006020X258 1).\n\n    The style above requires that a works-cited list be created and placed at\n    the end of the document. Each citation is assigned a number. In the example\n    above, the 1 refers to the first citation in the list; which appears in the\n    works cited list like this:\n\n    1. Accredited Standards Committee X12, Insurance Subcommittee, X12N. \"1.4.1\n    Information Flows, Fig. 1.1.\" Health Care Claim Payment/Advice (835),\n    006020X258. X12 Incorporated, June 2012. \u003chttp: //www.x12.org\u003e. 3.\n        \n        A span of page numbers is appropriate when the quoted material is on\n        consecutive pages. For example, to refer to the payer business contact\n        information segment:\n        \n        Accredited Standards Committee X12, Insurance Subcommittee, X12N. \"PER –\n        Payer Business Contact Information.\" Health Care Claim Payment/Advice\n        (835), 006020X258. X12 Incorporated, June 2012. \u003chttp: //www.x12.org\u003e.\n        94-96.\n\n        \nGlossary\n\nSee the X12 Wordbook (X12|ID required to access) for terms and their\ndefinitions: wordbook.x12.org.\n\nFrequently Asked Questions\nQ: When can I expect a response to my companion guide permission\nrequest?\nA: X12 will make every effort to complete the review within 30 business\ndays.\n\nQ: I want to send an X12 Technical Report, Type 3 (Implementation Guide)\nto my trading partners, is this allowed?\nA: No. Each organization needs to hold their own active license\npermitting use of the associated X12 product's content within their\norganization.\n\nQ: I want to share an X12 product that I legally purchased with my\ntrading partners, is this allowed?\nA: No. Each organization needs to hold their own active license\npermitting use of the associated X12 product's content within their\norganization.\n\nQ: How can I obtain permission to distribute an X12 Technical Report,\nType 3 (Implementation Guide) to my trading partners?\nA: X12 does not permit other organizations or individuals to directly\ndistribute its products. Each organization needs to hold their own\nactive license permitting use of the associated X12 product's content\nwithin their organization.\n\nQ: How can I obtain permission to distribute an X12 product to my\ntrading partners?\nA: X12 does not permit other organizations or individuals to directly\ndistribute its products. Each organization needs to hold their own\nactive license permitting use of the associated X12 product's content\nwithin their organization.\n\nQ: I created a proprietary companion guide with instructions\nsupplemental to an X12 TR3. Can I post the document on my website for\npublic viewing?\nA: If you have applied for and been granted permission for the use of\nX12 intellectual property in your companion guide, you may post the\ndocument on your website. You may not post the document prior to being\ngranted explicit permission.\n\nQ: I created a proprietary companion guide with instructions\nsupplemental to an X12 TR3. Can I post the document on my website with\naccess restricted to people who have a registered user id?\nA: If you have applied for and been granted permission for the use of\nX12 intellectual property in your companion guide, you may post the\ndocument on your website. You may not post the document prior to being\ngranted explicit permission.\n\nQ: Are these rules only for documents related to implementation guides,\nor Technical Reports, Type 3?\nA: No, these rules apply to use of all copyrighted X12 products.\n\nQ: My vendor has informed me that it has an agreement with X12 which\nallows for distribution of material generated from its commercial\nproduct without submitting an IP Use Request and without being granted\nexpress permission from X12 for the use of copyrighted materials. Is\nthis correct?\nA: Maybe, documents based on appropriately obtained X12 copyrighted\nmaterials, which includes documents generated with a tool properly\nlicensed from X12, may be used internally without explicit permission,\nbut distribution of such to any external organization or entity requires\nexplicit approval from X12.\n\nQ: Who can grant the necessary permission for use of X12 copyrighted\nmaterial?\nA: Only X12 has authority to grant such permission.\n\nQ: How can I verify that my vendor has obtained the appropriate\npermission or entered into a licensing agreement with X12?\nA: Please contact X12, at https://x12.org/licensing to verify your\nvendor has been granted rights to X12 copyrighted materials.\nRequest Permission\nSend an email to ip@x12.org to request permission to reproduce X12 IP.\nInclude your name, organization, title, address, city, state, zip,\nemail, a detailed description of the Submitted Artifact, including the\nunderlying or cited X12 Product, and a detailed description of the\nintended audience and planned distribution method for the Artifact.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ffreight-trust%2Fspdx-asc-x12","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Ffreight-trust%2Fspdx-asc-x12","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ffreight-trust%2Fspdx-asc-x12/lists"}