FHIR Patient Engagement Platform on AWS — 8-Week Implementation
Kriv AI · Cybersecurity & IT
Certification per AWS Marketplace.
Evidence tier Source Confirmed · 4 captures on record
What the publisher says
As described on AWS Marketplace.
Close care gaps, engage patients, and meet federal interoperability mandates — without multi-year systems integration.
Kriv AI's FHIR-Native Patient Engagement Platform is a production-grade 8-week implementation that stands up HealthLake, Bedrock, Comprehend Medical, Lake Formation, Glue, and QuickSight as a cohesive patient engagement stack. We deploy in your AWS account, hand over operations, and leave a documented runtime averaging roughly $360–$450/month in AWS infrastructure after teardown of pilot resources.
Show the rest of the publisher’s description (17 more lines)
Why IDNs, payers, and ACOs engage Kriv AI
The ONC Cures Act Final Rule, CMS Interoperability and Patient Access Rule, and the Prior Authorization Final Rule (CMS-0057-F) have moved FHIR from a strategic option to an operational requirement. CMS-0057-F API provisions are effective Jan 1, 2027 with compliance ramping through 2026. Most health systems already license a FHIR gateway but have not operationalized it for patient engagement, care-gap closure, or payer-provider API flows. We bridge that activation gap.
What we deploy
HealthLake ingestion + normalization for FHIR R4 resources from Epic, Cerner/Oracle, MEDITECH, athenahealth, or HL7 v2 feeds via Glue pipelines
Five Amazon Bedrock agents with Guardrails (PHI filtering + denied medical-diagnosis topics):
PatientEngagementCoordinator — segmentation, channel selection, outreach cadence
CareGapAdvisor — evaluates 15 preconfigured care-gap rules (mammography, colonoscopy, A1C, immunizations, annual wellness, depression screening) and surfaces candidates
ProviderFinder — NPI-verified in-network provider matching by specialty, geography, language, acceptance status
PatientEducator — condition-specific education grounded on CDC/NIH literacy sources
ComplianceMonitor — logs agent actions, PHI access, policy exceptions for audit
Comprehend Medical for unstructured clinical note entity extraction
Lake Formation row + column-level access control over the FHIR data lake
QuickSight dashboards — 5 views: Population Health, Care Gaps, Patient Engagement, FHIR Interop Monitor, Security + Compliance
AgentCore HIPAA-eligibility (Feb 10, 2026) — unlocks agentic workflows on PHI without custom compensating controls
8-week engagement. Weeks 1–2 Design (BAA, FHIR sources, US Core data model, IAM + Lake Formation). Weeks 3–5 Build (HealthLake, Glue medallion, 15 care-gap rules + NPI provider index, Bedrock agents, Comprehend Medical). Weeks 6–7 Evals + validation (QuickSight, UAT, MITRE ATLAS red-team, Cures Act $export bulk-FHIR conformance, load test). Week 8 Cutover (production go-live, runbook, knowledge transfer, 30-day hypercare).
Three tiers. Starter ($75K) for <500-bed hospitals or single-payer pilots: 1 care-gap use case + 2 agents + 1 dashboard. Professional ($100K) for 500–1,000-bed IDNs, ACOs, mid-market payers: 5 care gaps + 3 agents + 3 dashboards + Epic FHIR integration. Enterprise ($150K) for 1,000–1,500-bed IDNs, national payers: 15 care gaps + 5 agents + 5 dashboards + Epic + Cerner/Oracle integration + multi-tenant Lake Formation + 30-day hypercare. Optional 90-day Hypercare Extension ($35K). EDP-eligible — implementation fees ($75K–$150K) count toward your AWS Enterprise Discount Program commitment (up to 25%). AWS infrastructure costs (estimated $360–$450/month post-deployment) bill separately through your AWS account. Contact info@kriv.ai to structure a private offer against your EDP or PPA.
Important disclosures. AWS infrastructure costs are billed separately by AWS. Kriv AI delivers platform engineering, agent configuration, and methodology only — this platform is NOT a clinical decision support system and does not replace clinician judgment. Customer retains ownership of all HIPAA Business Associate Agreements, patient data, regulatory filings, and ongoing operational responsibility post-handover. Not legal, regulatory, or clinical advice. "Anthropic" and "Claude" are trademarks of Anthropic PBC; Anthropic does not endorse this specific solution.
Highlights
Highlighted by the publisher on AWS Marketplace.
8-week HealthLake + Bedrock deployment — FHIR R4 ingestion, 5 governed agents, 15 care-gap rules, production handover in your AWS account. Five Bedrock agents (PatientEngagementCoordinator, CareGapAdvisor, ProviderFinder, PatientEducator, ComplianceMonitor) with Guardrails enforce PHI filtering and denied medical-diagnosis topics. Comprehend Medical for unstructured note extraction; Lake Formation for row/column-level PHI access; QuickSight for population health.
ONC Cures Act, CMS Interoperability, and CMS-0057-F Prior Authorization Final Rule aligned (FHIR API mandate effective Jan 1, 2027). Compliance artifacts included: BAA template, US Core / USCDI v3 conformance, bulk-FHIR $export validation, audit-trail evidence via CloudTrail, AgentCore HIPAA-eligibility (Feb 10, 2026) leveraged so agentic workflows run on PHI without custom compensating controls. Pairs with E3 (HIPAA AI Governance Framework) for governance overlay.
AWS Select + Databricks + Anthropic CPN delivery — ~$360–$450/mo AWS runtime after pilot teardown. Three tiers: Starter $75K (1 care gap + 2 agents + 1 dashboard) for <500-bed hospitals; Professional $100K (5 care gaps + 3 agents + 3 dashboards + Epic integration) for 500–1,000-bed IDNs/ACOs/mid-market payers; Enterprise $150K (15 care gaps + 5 agents + 5 dashboards + Epic + Cerner + multi-tenant Lake Formation + 30-day hypercare) for national payers. Optional 90-day Hypercare $35K.
Agent build and provenance
See the full provenance
The layer-by-layer build, the evidence behind each claim, the risk basis and the cross-marketplace links are open to any account. Some rows are disclosed, some the source leaves Unknown; a free account shows you which.
Compliance
- FedRAMPConfirmedNot listed90%, registry-checkedNo FedRAMP Marketplace entry matched this vendor's domain, checked 2026-08-27registry recordas observed 2026-08-27
Confirmed means matched to a public authoritative registry. Claimed means the vendor or its listing states it, not yet cross-checked. A framework not shown was not found in any source we hold, which is not evidence against it. Not listed means a scoped registry check found no match for this vendor's domain: a No is a scoped registry check, not a compliance judgment. Confidence bands: 95% domain-verified, 90% registry-checked, 80% self-attested, 70% weak signal. Self-attested items marked “vendor's site” are gathered from the vendor's own website and are not verified by us.
Vendor
External enrichment · as of 2026-08-29
Sources
Publisher resources
3 linksLinked repositories
Unknown means this listing does not publish a repository. It is not a statement that the code is closed, and a linked repository is not a claim that the publisher wrote it: the registry computes that relationship privately and does not publish it.
Evidence risk is the share of the build you cannot see before you deploy, not a security rating. Sign in to see the layer-by-layer basis for this band.