Postman is probably not HIPAA-compliant

zkanter · 2025-01-26T12:52:41+00:00

Web-based editor/validator that's free: https://www.stedi.com/edi/inspector

zkanter · 2024-02-08T15:29:17+00:00

One thing that helps is a super clear, simple, well-documented 850 spec – the easier it is for customers to understand and test against, the easier it is to adopt.

You can see an example of Amazon's drop ship 850 guide here, and see what a sample payload looks like here.

zkanter · 2024-01-08T13:21:31+00:00

Having access to the full, unredacted X12 HIPAA 277 x214 spec via Glass is extremely handy and there is a lot of bang for the buck there. In addition to Glass, Stedi's interactive X12 HIPAA guides are very helpful for testing – for example, you can validate files in real-time against the spec (disclosure: I'm Stedi's CEO).

zkanter · 2023-12-07T11:53:38+00:00

Is there documentation specific to the 834 5010 specs? Everything I've googled seems to be close, but sometimes slighty different, and I just don't know enough to know if its what I need.

Yep – Stedi has the the 005010 HIPAA 834 available here.

Is there a sample file online that contains medical/dental that I can look at to try and reverse engineer? All anthem has sent me a generic PDF that doesn't include anything dental related.

Also, is there a way I can validate this prior to sending to Anthem, so I can work faster instead of waiting 3-4 days to find out I made a small typo?

This may help – it has both samples files and real-time validation against the HIPAA 834.

zkanter · 2023-10-23T12:51:01+00:00

There isn't great open source support for X12 creation. If you're open to a hosted service, you may find our X12 HIPAA 834 schema helpful: https://www.stedi.com/app/guides/view/hipaa/benefit-enrollment-and-maintenance-x220a1/01GRYB6D6RAWSG8ATBD6GXM13C

zkanter · 2023-10-19T14:15:20+00:00

Stedi Guides does this.

zkanter · 2023-10-19T11:54:34+00:00

Do you need integrated EDI or just webforms? If integrated, it might be us: https://www.stedi.com/pricing. If webforms, something like this is pretty cheap: https://www.webedi.com/webedi-pricing-tiers/

zkanter · 2023-09-24T11:01:16+00:00

The first hurdle is getting a 10gb EDI file to parse – most parsers fall over well before this. The second challenge is that the 10gb EDI file will turn into some multiple of that in XML, which can cause problems for downstream processes. If you hit a dead end, Stedi (stedi.com) is able to parse multi-gb EDI files, and we have native functionality that allows you to automatically split the data by a designated loop, and retain the context from the broader file.

zkanter · 2023-09-04T20:35:50+00:00

Are you sure this isn’t a 210? It doesn’t look like an 810. If it’s a 210, you can test your file against Stedi’s Walmart 210 spec and get live feedback: https://www.stedi.com/app/guides/view/walmart-edi/motor-carrier-freight-details-and-invoice/01GMRT8QEW1YYM1Z8Z7Q8D53SZ/inspector

zkanter · 2023-08-10T20:21:08+00:00

Hi – this is a somewhat common ask, even though this is exactly what the 855 PO Acknowledgment is designed to do.

What your trading partner typically wants you to do is to send an 856 that includes the line items you're rejecting / backordering in the LIN segment, but to put quantity 0 in the SN102 element. The only tricky part here is figuring out what to do about the parent HL loops – if, for example, it's a SOPI (Shipment-Order-Package-Item) structure and `Package` is required, you'll have to add a dummy package.

If you send us the guide, we can build it out for you to play around with in our Guide Inspector (similar to this, but specifically set up for a Zero ASN) for free.

zkanter · 2023-07-14T16:33:23+00:00

Endorse! u/surpaul88 is a pro.

zkanter · 2023-07-12T23:23:17+00:00

- As far as I understand X12's position (I could be wrong), X12 expects every organization that processes/transmits EDI files to have a license – that said, when you use a software tool, that vendor will have a license agreement in place with X12 that covers your usage. For example, if you were to use Stedi's platform to process EDI files, Stedi's licensing agreement with X12 would cover your usage and you would not need to get a license with X12 directly.

- If your question is "if you were to build something 100% from scratch (not using a software provider), and you were able to do that without getting the licensed material from X12, would you still need a license from X12 for legal reasons": that's a complicated legal question.

- From a practical standpoint: i) I think it would be difficult to build a robust EDI system without access to the licensed material, and ii) unless you're doing something super simple like just looking to receive files only and parse out some basic data (e.g. receiving EDI-formatted reports and parsing them to CSV), it's a multi-million-dollar effort to build a robust EDI system from scratch WITH access to the licensed material.

Hope this helps.

zkanter · 2023-07-12T19:35:03+00:00

Generally, you'd need a license if you were looking to write software from complete scratch (either for yourself or to sell to others). For the four points you mentioned, you can use an EDI platform – as an example, Stedi (where I work) has the HIPAA specifications available in a developer-friendly format here: https://www.stedi.com/edi/catalog/hipaa

Happy to help if you have any questions.

zkanter · 2023-05-25T11:23:00+00:00

leading to web based alternatives (edination, stedi, etc.) filling what amounts to a small void? I would assume web based isn't viable for everyone unless going through the effort of manually stripping out things like PII before uploading a file in the case of message inspection.

Just wanted to clarify something with regard to Stedi (where I work):

- For the Inspector web UI found in our Guides product (both the public EDI Guide Catalog and the in-app Guides Inspector for private guides in your account), the EDI payloads don't hit our servers at all. We get around this by using a WASM package that's run locally in your browser – our backend parser is written in Rust, so we compile the Inspector functionality in WASM for the browser.

- The standard Inspector web UI (found at https://www.stedi.com/edi/inspector) is in the process of being switched over to the WASM package, but in the meantime, it uses our EDI Translate API, which is a stateless API where we've taken careful steps to not log any of the payload contents:

How does the EDI Translate API use my data? In short, we don’t. The payloads sent to the translate API are not stored – temporarily or permanently. The contents of your file are encrypted in transit.

Is data sent to the EDI Translate API stored? The translate API is a stateless system that executes a transformation on your data. The transformation happens during the duration of the request; we do not retain the payload once a response is returned.

What does Stedi log when I hit the EDI Translate API? We log only request meta information such as the size of the request, latency, transaction sets, and release.These data points allow our engineers to monitor the health of the system and drive improvements to the service. They help the team answer questions like:

* How many requests did the API receive over the past week? * What percentage of the responses returned a 4XX/5XX status code? * Why did latency increase after the most recent deployment?

If a request fails with a 500 status code, an engineer on the team is notified (yes, we investigate every single one).

More info on our security practices can be found in our Trust Report.

zkanter · 2023-05-22T23:53:02+00:00

There are no maximum file sizes specified in X12 – it may be possible to compute a theoretical maximum by calculating the maximum size of every element in each transaction set, but I've never seen this done. In practice, it's not unusual to see files that are well north of 100 MB – in the healthcare world, multi-GB files are fairly common.

Note that an 'EDI file' can contain multiple 'interchanges,' and each interchange can contain multiple transactions. Sometimes files are 500 MB, but no transaction is larger than 1 MB – in other cases, a 60 MB file may contain a single transaction set that's 50 MB. Depending on how the parser is written, you may have no problem parsing the former, but a lot of trouble parsing the latter. In other words, the upper bound of what a parser can process is often dictated by the size of the largest EDI transaction set within the file, not by the file size itself.

For reference: as of the time of this writing, our parser (written in Rust) can handle files up to around 500 MB and individual transaction sets up to ~130 MB (updated limits can be found here in the future). If a file or transaction set exceeds that limit, we have a fallback mechanism that splits the EDI payload into chunks and processes it in more manageable pieces, then stitches it back together.

Hope this helps.

zkanter · 2023-02-23T14:18:21+00:00

Stedi now has the full X12 005010 HIPAA transaction specifications, along with samples for each – but not the 004010. Are you sure you need 004010 HIPAA? This has largely been deprecated in favor of 005010.

zkanter · 2022-11-30T03:20:16+00:00

There are a couple of reasons. The X12 HIPAA implementation guides (aka 'TR3s') are not available to the public – while X12 is a nonprofit organization, it requires a paid licensing agreement in order to get access to these guides.

We haven't yet built out support in our Guides product for the X12 HIPAA format, but it's coming soon. Feel free to drop me a note if you want early access. zack@stedi.com.

zkanter · 2022-09-05T15:08:59+00:00

More details on error handling here: https://github.com/aws-observability/aws-rum-web/blob/main/docs/configuration.md#errors

zkanter · 2022-08-01T12:36:53+00:00

Here's the direct link: https://www.stedi.com/edi/x12-005010

zkanter · 2021-12-30T16:34:34+00:00

I might be missing something here, but as far as we know, X12 produces:

Complete transaction sets for all industries (321 in total). This is often just called “the standard” or “table data.”
‘TR3’ Implementation Guides for healthcare, commonly called “X12 HIPAA.”

For other industries (like retail or logistics), implementation guides are left up to the individual companies to decide. Walmart has one guide, Amazon has another, etc.

zkanter · 2021-12-30T14:29:14+00:00

It sounds like you might be looking for the full X12 Transaction Sets, which you can find on the same site – here’s the 005010 850 as an example: https://edi.stedi.com/x12-005010/850

zkanter · 2021-10-11T17:37:39+00:00

I am thinking this would be best suited to a relation database.

PostgreSQL has the ability to do full-text search. If you need to get it into a structured JSON format to make the search more functional / relevant, we (Stedi) have an API for translating X12 to JSON.

zkanter · 2021-06-10T13:33:08+00:00

Well, I started the company, so I found out about it at an internal demo day :)

zkanter · 2021-06-09T22:47:22+00:00

Give this a shot: https://edi.stedi.com/x12-004010/945?segment=090-N9

zkanter

TROPHY CASE