FHIR Showcase

YOUR INFORMATION

Privacy policy

Effective November 7, 2026 · Operated by Ariel Serbin

FHIR Showcase is an independent experimental application for exploring provider and health-plan information. It is not an insurer, enrollment service, or medical advice service. Contact arielserbin@gmail.com with privacy questions, complaints, or requests to access, correct, or delete information.

What we use and why

When you search, we process the provider names, NPI numbers, specialties, cities, states, ZIP codes, counties, and plan criteria you enter to find public directory information and compare plans. Selected doctors and practices stay in the page’s memory for that visit and are sent to our server when checking plan associations. Although directory records are public, your searches and selections can reveal personal interests.

Public provider data comes from Humana and the national NPI registry (CMS NPPES). Public plan records are stored in our catalog. These are separate from personal health records.

Health overview demonstration

The health overview currently displays clearly labeled, fictional example records. These are authored demonstration data, not information about you or records retrieved from a health plan. Search filters and preview scenarios stay in page memory and reset when the page reloads. A failed connection does not substitute example records for your information.

Connecting a health-plan account

Blue Cross NC member login is not enabled yet. The connection flow requires you to acknowledge this policy and separately consent before leaving for the insurer’s login. Your insurer receives your login credentials; FHIR Showcase does not receive your password.

When enabled, this version requests read-only account access, verifies the connection, and temporarily holds the access token on our server. It does not yet fetch or display personal claims or clinical records. We do not save patient records in a database, retain refresh tokens, or access your account in the background. Any future feature that uses your records will explain its purpose and require express consent before access or use.

We will not sell your health information, use it for advertising, send it to an AI service, or use it for employment or insurance eligibility decisions. We will obtain express consent before any new use or sharing of health information. Disclosures required by law may occur without consent; we limit them to what is required. We will not transfer health information as a business asset without notice and express consent unless law requires the transfer.

Services involved

Railway hosts this application and its public plan database. Search providers receive the search criteria needed to answer your request. Provider address maps load from Google Maps or OpenStreetMap; those providers receive the displayed practice address and ordinary connection information, such as your IP address and browser information. No connected-account token or patient record is sent to maps, public directory searches, or the public API activity panel.

We do not use advertising or analytics trackers. Our hosting provider may process operational connection metadata, including IP address, browser information, requested paths, status, and timing. Infrastructure logs have separate retention controls; clearing an app session does not delete those logs. Retention depends on the hosting service’s policies and configuration and may extend up to 90 days. We do not intentionally write patient records, authorization codes, tokens, or passwords to application logs.

Your device and session

We do not request your contacts, precise device location, photos, files, camera, or microphone. You enter any location used for searches. The connection page uses a secure, HTTP-only session cookie containing a random identifier, not health information or a token. We do not use browser local storage for health information. Normal browser and network information is needed to deliver the site.

Retention, withdrawal, and deletion

Connection information, consent acknowledgement, and encrypted access tokens are held only in server memory for at most 15 minutes from the start of a visit, or less when the token expires. Sessions also disappear when the server restarts. Expired sessions become unusable immediately and are removed by cleanup within 10 seconds. No patient-session backups or durable patient-record store are created.

Select Disconnect and clear this session (or Clear this session) on the connection page to remove the app’s session and token immediately. Closing a tab alone does not immediately end the server session. To withdraw the insurer’s authorization as well, remove FHIR Showcase from your insurer’s connected-app settings or contact its member support. Deleting our copy of a token does not itself revoke the insurer’s grant.

Reloading or closing the explorer page clears its selected-doctor list. Public directory responses may be cached on the server for up to one hour; public plan records remain in the catalog and are refreshed independently. These public records are not your personal account records.

Email the contact above for access, correction, or deletion help. Please do not send passwords, member IDs, or health records by email. We may ask for minimal information to verify a request. We cannot correct an insurer’s or public registry’s source record; we will explain how to contact that source. Privacy correspondence is retained only as needed to resolve the request and meet applicable obligations. Email services and hosting logs have their own retention and backup controls.

Protection and accountability

We use HTTPS, server-side credentials, short-lived sessions, explicit consent checks, and encrypted tokens held in memory. Only the application operator and necessary hosting services administer the application. No system can guarantee perfect security. If we discover an incident affecting personal information, we will investigate, limit access, and notify affected people and authorities as applicable. This policy does not claim HIPAA certification or CARIN accreditation.

Changes

We will update the effective date when this policy changes. Before materially expanding how health information is collected, used, or shared, we will explain the change and seek fresh express consent. You can decline by not connecting or by disconnecting.