Wireframe preview

Best viewed on desktop.

This is a wireframe for review, not the finished site. The responsive (mobile) treatment comes in the design and build phase. Open this page on a screen at least 1200 px wide to see the layout as intended.

How It Works

Post-n-Track Gen 3 authenticates, validates, translates and routes healthcare transactions, X12 EDI, HL7 and FHIR, in transit, and retains no PHI at rest. It is the architecture behind the 2026 MedTech Breakthrough Award for Best Overall Healthcare Cybersecurity Solution.

What Post-n-Track Is

Post-n-Track Gen 3 is PNT Data Corp.'s current, in-market platform. PNT calls this model a healthcare data sharing authority platform: a platform that moves and verifies regulated data between organizations without ever taking custody of it. Gen 3 performs the functions healthcare data intermediaries have always performed, accept, translate, validate and route, with one architectural difference: the transaction is not retained after it is delivered. There is no central repository of customer transaction history.

A shorter retention window or stronger encryption at rest still leaves a repository in place, one that exists and is reachable by valid credentials. Gen 3 does not create the repository, so there is nothing for those controls to protect.

From Gen 1 to Gen 3

Gen 1 systems were batch: files moved on a schedule, store-and-forward was the only reliable mechanism, and retention was a byproduct of the transport model. Gen 2 added real-time paths on top but kept the central store, because by then retained data had become a product in its own right. Gen 3 removes the store. The functional capability is unchanged from the customer's perspective; what changes is that a compromise of the intermediary does not expose the customer's transaction history, because it isn't there.

An intermediary that retains nothing cannot serve retrospective analytics on payloads it no longer holds, and cannot re-send a transaction from a copy it does not keep. Those capabilities require a different architecture: provenance and status metadata rather than payload retention. Organizations that want their intermediary to also be their data warehouse are asking it to also be their breach surface. Gen 3 declines that combination on purpose.

How a Transaction Flows

Every transaction, whether a claim, a remittance, an eligibility inquiry or a clinical message, takes the same path through Post-n-Track. The whole trip happens in transit; nothing is written to a repository at any step.

  1. Authenticate

    Your system sends the transaction in the format it already produces, an X12 EDI file, an HL7 v2 message or a FHIR API call, in real time or on your schedule. Post-n-Track authenticates the submitter at the boundary before anything else happens.

  2. Validate

    The transaction is checked against the HIPAA implementation guide and the receiving payer's own edits while it is still in motion. Errors come back immediately, while the person who can fix them is still looking at it.

  3. Translate

    Where sender and receiver use different formats, Post-n-Track maps between them: proprietary to X12, HL7 v2 to FHIR, one X12 variant to another. Normalization and enrichment happen here too.

  4. Route

    The transaction is delivered directly to the correct endpoint, a payer, a provider, a clearinghouse or a partner platform, and the response comes back the same way. Post-n-Track keeps no copy.

  5. Track

    Status and provenance metadata are recorded for every transaction: what was received, when, from whom, and where it went. That drives alerting, reporting and audit evidence without holding any PHI.

Connectivity and Onboarding

Post-n-Track connects to the systems you already run. It accepts and delivers X12 EDI, HL7 v2, FHIR R4 and proprietary formats, in real time or in scheduled batch, with direct connectivity to the nation's largest commercial payers. There is no portal to upload to and no repository to load.

The service runs on resilient, AWS-based multi-zone infrastructure with intelligent routing and failover, and is independently audited. Onboarding and support are handled by a 100% U.S.-based team, with no long-term agreement and no exclusivity required.

  • X12 EDI, HL7 v2, FHIR R4 and proprietary formats
  • Real time or scheduled batch
  • AWS multi-zone infrastructure with failover
  • No long-term agreement, no exclusivity

Frequently Asked Questions

What is Post-n-Track Gen 3?

Gen 3 is PNT Data Corp.'s current healthcare data platform. It authenticates, validates, translates and routes X12 EDI, HL7 and FHIR transactions in transit and retains no PHI at rest, eliminating the central repository that makes traditional intermediaries high-value breach targets.

How is Gen 3 different from Gen 1 and Gen 2 systems?

Gen 1 was batch store-and-forward, where retention was a byproduct of the transport model. Gen 2 added real-time paths but kept the central store. Gen 3 removes the store: the same accept, translate, validate and route functions, without retaining the transaction afterward.

Is zero-residency the same as encryption at rest?

No. Encryption at rest protects data that still exists and is still reachable by anyone with valid credentials. Zero-residency means the data at rest does not exist. The distinction matters most in exactly the scenario encryption does not cover: a compromise using legitimate credentials.

Ready to talk through your use case?

Talk to a Post-n-Track specialist about your data challenges. A direct conversation, starting with what you need.