ABOUT
FULLY IMMERSIBLE RESOURCES to HELP deliver innovative solutions
WHAT WE Do...
We resolve Identities and Entities in FHIR® repositories in a process, using Machine Learning for Matching, inference for Linking, and Open Source libraries for remediation.
We deploy next generation Healthcare workloads exclusively on Google Cloud Platform. Using FHIR® for core application development, Identity Feed participation with HL7, and Imaging workloads with the Google Cloud Healthcare API.
We mass transform delivery and payer data to FHIR® or the reverse using Databricks Medallion methodologies.
We participate in HL7/FHIR® Connectathons, IG development, and understand the importance of standards hacking breeding projects.
Still have questions? Get in touch
We deploy next generation Healthcare workloads exclusively on Google Cloud Platform. Using FHIR® for core application development, Identity Feed participation with HL7, and Imaging workloads with the Google Cloud Healthcare API.
We mass transform delivery and payer data to FHIR® or the reverse using Databricks Medallion methodologies.
We participate in HL7/FHIR® Connectathons, IG development, and understand the importance of standards hacking breeding projects.
Still have questions? Get in touch
Whats with the name?
For HL7 nerds, PID-2 is the external id supplied by organizations transacting to other facilities. Along with PID-3, these carry various identifiers from multiple assigning authorities.
PID-2: Patient ID (External ID) – the patient identifier number used by one or more outside institutions (i.e. a physician’s office that is referring the patient)
PID-2: Patient ID (External ID) – the patient identifier number used by one or more outside institutions (i.e. a physician’s office that is referring the patient)
is PID^TOO|| a startup?
Was, in the most popular sense.
PID^TOO|| is a deployable method to resolve identities and identities in a FHIR repository, we exhausted quite a bit of time and money into wrapping the whole thing up into a deployable stack, then realized we didnt need to for where we were heading. Now, we open up the solution and use it for grounding our grant submissions, which is the majority of our business strategy.
PID^TOO|| is a deployable method to resolve identities and identities in a FHIR repository, we exhausted quite a bit of time and money into wrapping the whole thing up into a deployable stack, then realized we didnt need to for where we were heading. Now, we open up the solution and use it for grounding our grant submissions, which is the majority of our business strategy.
Can YOU Pilot Your solutions?
Yes! Please!
If you have an interest in deploying one of our solutions in your environment, let us show you the way.
We have our first PID^TOO|| Pilot, that went live in January of 2024.
If you have an interest in deploying one of our solutions in your environment, let us show you the way.
We have our first PID^TOO|| Pilot, that went live in January of 2024.
What kind of support is available?
We manage data pipelines in the same manner as some managed service providers manage cloud adoption.
Whether its a Spark workload, Application Development, FHIR® Implementation or Identity Resolution we support and implement it to best practice.
Whether its a Spark workload, Application Development, FHIR® Implementation or Identity Resolution we support and implement it to best practice.