Security & Privacy
Built around HIPAA. Written into our contracts.
Fieldstone Health makes software that collects patient information for healthcare organizations. This page explains how we protect that information, in technical detail, and points to the section of our agreements that commits us to each safeguard.
Our key commitments are in documents you can hold us to: our Master Business Associate Agreement (BAA), the service schedule for your plan, and our Privacy Policy. Where a commitment comes from one of them, we cite the section. The rest of the page describes how we build and run the service to meet them.
The technical details below describe Secure Form, our patient forms platform, on its Direct Delivery and Workflow Portal plans. Donor Portal and Admissions Portal are covered by the same Master BAA, and each will have its own service schedule describing how it handles information.
Jump to a section
At a glance
- 3 Business Days: initial notice to you of a breach or security incident
- 10 Business Days: full written report, with everything you need for your own notices
- 1 key per customer: your data is encrypted with a key used only for your organization, itself protected in AWS’s key-management service
- 6 years: audit log of every view and download of a stored submission, visible to your administrators
- 30 days: Direct Delivery submissions are deleted 30 days after delivery, and their backups within 30 more
- Zero: cookies, analytics or third-party scripts on the pages your patients fill in
- U.S. only: patient information is stored in U.S. data centers, under business associate agreements
- Your service only: patient information is used only to run the services you signed up for
Our commitments
- We use patient information only to provide your service. We use and disclose protected health information (PHI) only to perform the services in your signed schedule, as the law requires, or within HIPAA’s limits for our own administration, and always only the minimum necessary. (BAA §§2.1–2.4)
- We tell you quickly when something goes wrong: an initial notice within 3 Business Days and a full report within 10. (BAA §4.2)
- You can see every access to your stored submissions, including ours. (Schedules A and B)
- We don’t reduce your protection without your signature. Silence or continued use is never agreement. (BAA §10.3)
- We answer for our vendors as if we had done their work ourselves. (BAA §5.3)
- Your records are always yours. You keep access to your PHI for as long as we hold it, whatever the state of your account. (BAA §6.1)
How our agreements protect you
Our contracts are written so that the protection is specific, checkable and hard to erode.
One Master BAA for every customer. It holds the HIPAA obligations only, and it is built on the sample business associate provisions the U.S. Department of Health and Human Services (HHS) publishes for 45 C.F.R. §164.504(e). Every customer of every Fieldstone product signs the same one.
A service schedule for each product or plan. The schedule says, in plain terms, how that product handles PHI:
- what is shared with other customers;
- where data is stored;
- how it is encrypted;
- how long it is kept;
- who can open it; and
- how it is returned or destroyed.
Each schedule carries a version number and date. Schedule A covers Secure Form Direct Delivery and Schedule B covers Secure Form Workflow Portal.
Schedule C, for organizations outside HIPAA. Schedule C is part of the Master BAA and applies automatically. It gives health information protected by contract the same protection as PHI, plus terms written for state health-data laws (see Organizations outside HIPAA).
Terms a compliance reviewer will look for
- The BAA comes first. It prevails over any conflicting schedule or other agreement about protecting PHI, and no schedule update can change it. (§11)
-
Updates can’t weaken your protection without you.
- We may update a schedule by notice only if, compared with your current terms, protection doesn’t go down. An improvement in one protection never offsets a reduction in another.
- Notice comes at least 30 days ahead, with the revised schedule and a summary of the changes. An urgent security update can shorten the notice, but nothing else.
- A reduction in protection, a new purpose, a new service, or a change to liability or fees needs your affirmative written agreement.
- Updates apply only going forward, and we keep every version and every notice. (§10)
- You have a real say over new subcontractors. We give you written notice at least 30 days before a new subcontractor first handles your PHI. You have 15 days to object on reasonable privacy or security grounds. If we can’t resolve it, you may end the affected service without penalty, and take your export first. (§5.2)
- Our restrictions flow down. Every subcontractor that handles PHI agrees in writing to HIPAA’s requirements and to the same limits on use and disclosure we accept. (§5.1)
- Help with patients’ rights is due on a deadline. We complete access, amendment and accounting help within 10 Business Days of your request, not just acknowledge it. (§§6.1–6.3)
- Your HIPAA role is stated, not assumed, on the signature page. If you are a business associate, we act as your subcontractor. (§1.4)
- Clear exits. You may terminate immediately where continuing would put PHI at material risk, and any suspension keeps your lawful access and return rights. (§9.2)
What stays with you
Security is shared, and the BAA says where the line sits (§§8.3–8.5). You are responsible for:
- the delivery addresses you set, and the security of your own mailboxes and systems once a form reaches them;
- who on your staff has an account, including removing access promptly when someone leaves;
- sending PHI to us only through the service, never by ordinary email, support tickets or our websites (for support that needs PHI, we designate a secure channel);
- sending blank forms when you ask us to build one; and
- not using the service with real patients until the Services Agreement, BAA and your schedule are signed and we have confirmed in writing that your account is activated.
Architecture and data flow
A patient’s answers are encrypted before they are stored, and every view or download of a stored submission is recorded in your audit log.
- The patient opens your form at your own address, such as yourpractice.secure-form.com. These addresses serve patient forms only; they have no sign-in pages. Your staff sign in at a separate address.
- The browser sends the submission over HTTPS (TLS 1.2 or later), through our hosting provider’s network edge, where Cloudflare provides protection against denial-of-service attacks.
- The application checks the submission against your form. Which organization it belongs to, and where it is delivered, come from settings on our server, never from anything in the form itself.
- It encrypts the answers, signatures and files with a key used only for your organization and stores them: answers in the database, files in Amazon S3. Only after the submission is safely stored does the patient see that it was received.
-
It makes the PDF, encrypts and stores it the same way, and delivers the submission the way your plan works:
- Direct Delivery: the PDF and any attached files are emailed through LuxSci’s secure email service. The subject and body name only the form, your organization and the time.
- Workflow Portal: your chosen staff get a notice with a link and no patient details, unless you ask us to attach the PDF, which is then delivered as on Direct Delivery. Staff open the submission in your secure portal, where they can search, view, download and track it.
- Every view and download of a stored submission is written to the audit log.
- Backups: nightly backups are kept 30 days. On Workflow Portal, for HIPAA covered entities and business associates, each submission is also written once to a locked archive.
The platform runs in our hosting provider’s HIPAA-enabled environment, with files, backups and keys in Amazon Web Services, all in U.S. data centers and all under business associate agreements.
Encryption and key management
Your data is encrypted with a key used only for your organization, and that key is itself protected by a master key that never leaves AWS’s key-management service.
In transit
- Every connection that carries PHI uses TLS 1.2 or later. Plain HTTP is redirected to HTTPS, and browsers are told to use HTTPS only (HSTS).
- The connection between the application and its database is required to use TLS.
- Email leaves our application over TLS. Our email provider delivers it over TLS. If a recipient’s mail server can’t accept TLS, the message is held in LuxSci’s secure portal, where the recipient signs in to read it. No submission email goes out unencrypted.
At rest, in two layers
- Application layer. Before anything is stored, the application encrypts each submission’s answers, signatures, files and PDF with a data key unique to your organization. That key is stored only in wrapped (encrypted) form and is unwrapped through a master key in AWS Key Management Service (KMS). The master key never leaves AWS, and AWS logs every use of it.
- Storage layer. Underneath, our database storage and Amazon S3 encrypt everything again with AES-256.
Why the keys live apart from the data. The keys that unlock encrypted answers and files can only be unwrapped through AWS KMS, a separate service with separate access, so the encrypted contents of a database copy or backup can’t be read on their own. HHS’s breach-notification guidance looks for exactly that separation when it treats encrypted PHI as secured.
Deleting your records when you leave
When you leave, we delete your records from our active systems within 30 days, and backups expire within a further 30. An archive copy can’t be deleted before its lock ends, even by us, so each one is deleted when its own one-year lock ends, and we tell you the date of the last one. Until then it remains PHI with every protection of the BAA. Disabling or deleting an encryption key doesn’t count as destroying PHI. (§9.4)
Keeping customers apart
Your records are walled off at more than one layer, and we test the walls.
What is shared, stated plainly
All Secure Form customers share one application, one database and one file store, along with our code, our administration and our email provider. We say so in your service schedule, because a compliance reviewer should know.
How your records stay yours
- In the application. Every record carries the organization it belongs to, and every staff account belongs to exactly one organization. Your staff see only your records.
- In the database. PostgreSQL row-level security on every customer table means that a query that doesn’t name its organization returns nothing. The application’s own database login is held to those rules on every request, and a check at every deploy stops the release if it isn’t. Automated tests check that one customer can’t read another’s rows, and we maintain those controls as the code changes.
- In file storage. Each organization’s files sit in their own folder, already encrypted with that organization’s key. They are downloaded only through the application, after its organization check, never through shareable links.
- In encryption. Each organization has its own data key, so your records are encrypted with a key no other customer’s data uses.
Access and sign-in
Every person signs in as themselves, with two factors, and sees only what their role allows.
- One account per person. No shared logins, for your staff or ours.
- Two factors for every account, with no opt-out. The default is a passkey (Face ID, fingerprint or device PIN), which counts as both. Otherwise a password plus a second step, with single-use backup codes; a text-message code is available as an added option, never the default.
- Strong passwords, at least 12 characters, checked against common passwords and stored only as salted hashes. For passkeys we store the public key and a random account tag, never your face or fingerprint. Repeated failed sign-ins are throttled.
- Trusted devices. A device a user chooses to trust can skip the second step for up to 30 days. The option is not for shared or public computers, and changing the password or removing the account ends it.
- Sessions end after 30 minutes without activity, or 8 hours after sign-in.
- A separate staff address. Staff sign in at a separate address; the addresses your patients use have no sign-in pages.
- Your administrators control your accounts. They add and remove staff, manage forms and delivery addresses, and see form counts and a delivery log. On Direct Delivery, administrators don’t view stored submissions; on Workflow Portal, staff work with them in the portal.
Fieldstone’s own access is narrow, named and visible to you
- Only Fieldstone’s authorized administrator and our designated emergency contractor can open stored submissions, each with their own account.
- They do so only for the purposes your schedule lists. On Direct Delivery: to deliver or resend a form, to fix a problem, in a documented emergency, or as you direct. On Workflow Portal: to support you, to fix a problem, in a documented emergency, or as you direct.
- Every view and download appears in your audit log.
A way in if our administrator can’t be reached. A designated emergency contractor, working under a confidentiality and business associate agreement with us, holds sealed emergency access to our systems, so your records stay reachable. Every view and download of your submissions through that access appears in your audit log.
Fieldstone’s own accounts with our hosting, storage, email and code providers also require a second sign-in step.
Audit and transparency
You can see who opened every stored submission, including us.
- Every view and download is recorded. The audit log records each view and download of a stored submission, with the person and the time. It holds no patient answers.
- Kept 6 years. The log is kept separately from submissions, so it survives the end of service. It keeps each person’s name even after their account is deleted.
- Your administrators see the whole log, on both plans, including every access by Fieldstone and by our emergency contractor.
- Disclosures are documented for HIPAA accounting: the date, the recipient, a description of the information and the purpose, kept 6 years. (BAA §6.3)
- Settings changes are logged with who made them, when, and the old and new values, including changes to the addresses where your forms are delivered.
- Delivery is visible. The delivery log shows each submission’s email as waiting, sent or failed, with no patient details.
Retention and deletion
We keep patient information only as long as your plan needs it, and we delete it everywhere it lives, backups included.
| Direct Delivery | Workflow Portal | |
|---|---|---|
| Submissions | Deleted 30 days after our email provider accepts the delivery email, so a lost email can be sent again | Stay in your portal while you are a customer, unless you choose a shorter period. Your staff can’t delete them; we delete junk or duplicates when you ask, and whenever the law requires |
| Backups | Expire within a further 30 days | Nightly backups kept 30 days |
| Locked archive | Never | HIPAA covered entities and business associates: each submission written once and kept 1 year. Other customers: no archive |
| When you leave: your copy | Any submission we still hold is returned securely if you ask, up to 30 days after the end | One free export if you ask, up to 10 days after the end, delivered within 10 Business Days |
| When you leave: deletion | All submissions, forms and account data deleted within 30 days; backups expire within a further 30 | The same. Each archive copy is deleted when its one-year lock ends, and we tell you the date of the last one |
| Audit records | 6 years | 6 years |
More detail
- Delivery failures on Direct Delivery. Our email provider accepting an email doesn’t prove it arrived. We watch for reported delivery failures, alert you, and agree with you what to do with any submission that can’t be delivered.
- The locked archive. On Workflow Portal, the archive protects your records against loss, mistakes and tampering. It uses Amazon S3 Object Lock in compliance mode: nobody, including Fieldstone and the AWS account’s own root user, can change or delete an archive copy before its year is up. Corrections are attached to the record rather than written over it, and they appear in every later view, export and disclosure. (BAA §6.2)
- The export. A ZIP file has a folder for each submission, named by its date, patient and form, holding its PDF and attached files. It comes with a CSV index (patient name, date of birth, form, date submitted and status), any amendments, and a copy of your audit log. You download it from your portal, and we tell you in advance when it is ready and when deletion will happen.
- Staff accounts are deleted within 30 days after a customer leaves, and their backups within a further 30 days.
- The law comes first. Where the law requires us to keep or delete information on a different schedule, the law prevails.
Privacy on the form page
The page your patients fill in carries your form and nothing else.
- No cookies, analytics or tracking on patient form pages: no advertising networks, pixels or social widgets.
- No outside code. Form pages load no scripts, fonts or images from other companies. Signatures are drawn with our own signature pad.
- Nothing left behind in the browser. We don’t store patients’ answers in browser storage, and we tell browsers not to cache form pages, which matters on shared front-desk tablets and computers.
- No patient details in addresses. Patient details stay out of page addresses, query strings and redirects, because our hosting provider’s request logs record each visitor’s IP address and the page address for 30 days. We protect those logs accordingly.
- No patient answers in our logs. Our application logs are designed to leave out patient answers and other personal information we don’t need, and a safeguard stops a mail misconfiguration from writing emails to the logs.
- Spam protection without third parties. We block spam with a hidden trap field, a proof-of-work check and rate limits, not with a third-party CAPTCHA that would see your patients. For these checks we keep only keyed hashes of IP addresses, for up to one hour. Our hosting provider’s request logs, described above, keep the IP address itself for 30 days.
- Uploaded files are handled carefully. Each file is checked by its content, not its name, and stored under a name taken from the form’s question, never the patient’s own file name.
- Forms for children. You can mark a form as being for patients under 13. It then shows “To be completed by a parent, guardian or other authorized adult” at the top.
Some things are outside any website’s control, such as a patient’s own downloads, browser autofill and browser history, and we say so in our Privacy Policy.
Incident response
If something goes wrong, you hear from us within 3 Business Days, and you get a full report within 10.
- Day 0 Discovery The first day we know of it, or would have known with reasonable diligence
- 3 Business Days Initial notice What we know so far, and a named contact person
- 10 Business Days Full report Each individual affected, and what you need for your own notices
What we report (BAA §4.1)
- any use or disclosure of PHI the BAA doesn’t allow;
- any breach of unsecured PHI, as 45 C.F.R. §164.410 requires; and
- any security incident.
When (BAA §4.2)
- Initial notice without unreasonable delay, and no later than 3 Business Days after discovery. It says what we know so far and names a contact person.
- Full report no later than 10 Business Days after discovery. It identifies each individual affected and gives you what you need for your own notices under 45 C.F.R. §164.404(c): what happened, the dates, the types of information involved, the steps individuals should take, and what we are doing to investigate and mitigate. We supplement it as we learn more.
- Discovery of a breach is defined by HIPAA’s rule: the first day we know of it, or would have known with reasonable diligence.
- An unfinished investigation doesn’t delay either notice. We tell you what is still unknown. These periods are outer limits: they never permit unreasonable delay, or delay past an earlier legal deadline.
- Business Days are weekdays other than U.S. federal holidays.
What counts. An attack that succeeds, disrupts availability or otherwise compromises PHI is reported, and that includes a denial-of-service attack that affects your access. Routine unsuccessful attempts, such as pings, port scans and failed sign-ins, are covered by a standing notice in the BAA, so your inbox isn’t flooded with noise. (§4.3)
How we reach you. A breach report goes to your notice contact by email and by phone. (§12.5)
After the notice, we mitigate any harmful effect we know of, and we cooperate with your notices to individuals, regulators and the media. (§§4.5, 4.6)
Patient information sent to us by mistake, such as a filled-in form attached to a website request, follows a set routine. We restrict it and never send it to AI. We assess it, give any notices required, and securely return or delete it, keeping only a short incident record without the patient details.
Subcontractors
Every company that handles your PHI for us is named, bound by a business associate agreement, and our responsibility.
| Provider | What it does for us | Handles PHI? | Agreement |
|---|---|---|---|
| Render | Hosts the application and database in a HIPAA-enabled environment, in the United States | Yes | Business associate agreement |
| Amazon Web Services | Stores files, backups, the locked archive and encryption keys (S3 and KMS), in the United States | Yes, encrypted | Business associate agreement |
| Cloudflare, through Render | Protects our hosting from attacks at the network edge | In transit | Covered through Render’s agreements |
| LuxSci | Sends our email securely; also runs our earlier form service | Yes | Business associate agreement |
| Microsoft 365 | Our own email | Only if sent to us by mistake | Microsoft’s business associate terms |
| Emergency contractor (an individual) | Support and sealed emergency access to our systems | Only when needed, and logged | Confidentiality and business associate agreement |
We give you the current list when you sign and whenever you ask. The version in effect when you sign becomes part of your BAA.
OpenAI is not on this list, by design. We use it only to draft web forms from blank forms, and it never receives patient information (see the next section).
AI, used narrowly
We use AI to build blank forms faster, never on patient information.
- What it does. When you send us a blank form to build, we may use an AI service, currently OpenAI, to draft the web version.
- Checks before anything is sent. We check each document for filled-in answers and for hidden or embedded data, and remove personal information we don’t need. A person confirms the document is blank before it goes.
- Never sent: completed forms and patient answers. Any file we upload to OpenAI is deleted there right after use.
- What OpenAI keeps. Requests are sent with OpenAI’s response storage turned off. OpenAI may still keep them for up to 30 days to monitor for abuse, and it doesn’t use them to train its models.
- Choosing models. When we evaluate or change AI models, we test on reviewed blank templates or made-up examples, never real patient information. Any model we use must stay within the same restrictions.
- In the contract. Our BAA forbids using PHI to develop or train AI or machine-learning models (§2.5), and every subcontractor must preserve that restriction (§5.1).
Demos and your first free form
You can try Secure Form without putting a single real patient at risk.
The website demo needs no account and no email address. It asks for made-up details, and nothing you type leaves your browser. The sample PDF shows our own made-up patient, not your answers, and opens right on the page for you to view or download. We don’t email it or keep a copy.
A practice demo is one of your own blank forms, built for you to try before you sign up. It is enforced on our server, not just described on the page:
- It is marked as a demo on every page and PDF.
- It accepts no file uploads.
- It takes a limited number of test submissions.
- It delivers only to the person who requested it.
- It expires after 15 days.
- Before using it, that person ticks a required, unticked box confirming they won’t enter real patient information or share the demo with patients. We record who accepted, when, and which version of the terms.
Demo submissions are deleted when the demo ends, and backup copies expire within 30 days.
Going live requires a signed Services Agreement, BAA and service schedule, and our written confirmation that your account is activated. Until then, nothing is live for patients. (BAA §8.5; Services Agreement §3.2)
If real patient information is entered in a demo anyway, we quarantine it, assess whether anyone must be notified, and securely delete or return it.
Organizations outside HIPAA
If HIPAA doesn’t apply to you, your information still gets HIPAA-level protection, by contract, plus terms written for state health-data laws.
Some of our customers, such as nonprofit milk banks, may not be HIPAA covered entities. They sign the same Master BAA, and Schedule C applies automatically to their health information. Under Schedule C:
- Same protection, by contract. Health information we handle for you receives every protection our BAA gives PHI. Signing doesn’t make you subject to HIPAA. (BAA §1.4)
- We act only on your instructions, as your processor or service provider, and tell you if we believe an instruction would break the law.
- Used only for your service. We use the information only to provide, secure and support your service, and keep it apart from any other data.
- Help with individuals’ rights. We help you respond to requests to access, confirm, correct or delete data, or to withdraw consent, within 10 Business Days. We forward any request that comes to us within 2 Business Days. When consent is withdrawn, we stop the processing you identify.
- Deletion everywhere. On your instruction, we delete from active systems within 30 days, and backup copies expire within a further 30, even where the law would allow longer. Your data never goes into a locked archive that would prevent deletion, and we confirm deletion in writing on request.
- The law prevails over our retention terms, in either direction.
- Same incident timetable. Incidents follow the same 3- and 10-Business-Day timetable, with the information you need for state breach and health-data notices.
Administrative safeguards and governance
HIPAA’s Security Rule asks for administrative and physical safeguards, written policies and documentation, not just technical controls. Our written program covers them.
- A written information security program covering the administrative, physical and technical safeguards of the HIPAA Security Rule. It also serves as the written information security program that Massachusetts requires under 201 CMR 17.00.
- A dated risk analysis of the systems that hold PHI, and the risk management that follows from it.
- Training before access. Our workforce and our contractor complete HIPAA privacy and security training before they get access.
- An incident response plan built around the BAA’s 3- and 10-Business-Day reporting, including the routine for information sent to us by mistake.
- A contingency plan: backups, tested restores, and the emergency access procedure described above.
- Vendor oversight. We keep each vendor’s signed BAA or terms on file. We check them against what we promise you, including breach-notice timing, data use and retention after deletion, and we require vendors to maintain appropriate security for personal information.
- Documentation kept. Security policies and procedures are kept at least 6 years, as HIPAA requires (45 C.F.R. §164.316(b)(2)). We keep every version of each service schedule, every update notice with proof of delivery, and a record of which version applies to each customer. (BAA §10.4)
- Available to HHS. We make our practices, books and records on PHI available to HHS as HIPAA requires. (BAA §7)
How we map to the HIPAA Rules
For reviewers who work from the regulation: key standards from the Security, Breach Notification and Privacy Rules, and how Fieldstone addresses each.
| Standard (45 C.F.R.) | How Fieldstone addresses it |
|---|---|
| §164.308(a)(1) Security management process | Written security program with a dated risk analysis and the risk management that follows from it; audit-log review |
| §164.308(a)(4) Information access management | Role-based access: your staff see only your records; Fieldstone opens submissions only for listed purposes; minimum necessary (BAA §2.3) |
| §164.308(a)(5) Security awareness and training | HIPAA privacy and security training before any workforce member or contractor gets access |
| §164.308(a)(6) Security incident procedures | Written incident response plan; 3-Business-Day initial notice and 10-Business-Day full report (BAA §4.2); mistaken-PHI routine |
| §164.308(a)(7) Contingency plan | Nightly backups kept 30 days; locked archive on Workflow Portal for HIPAA customers; tested restores; sealed emergency access |
| §164.308(b)(1) Business associate contracts | Business associate agreements with every subcontractor that handles PHI, preserving our restrictions (BAA §5.1); Subcontractor List given at signing and on request |
| §164.310(a)(1), (d) Facility access; device and media controls | PHI is stored only with the providers on our Subcontractor List, in their U.S. data centers, under business associate agreements; disposal by deleting the data itself, including archive copies when their lock ends |
| §164.312(a)(1) Access control: unique user identification | One account per person, for customer staff and for Fieldstone; no shared logins |
| §164.312(a)(1) Access control: emergency access procedure | Designated emergency contractor with sealed access and an account of his own; every view and download of your submissions through it appears in your audit log |
| §164.312(a)(1) Access control: automatic logoff | Sessions end after 30 minutes without activity, or 8 hours after sign-in |
| §164.312(a)(1) Access control: encryption and decryption | Application-layer encryption with a key per customer, wrapped by a master key in AWS KMS; AES-256 storage encryption underneath |
| §164.312(b) Audit controls | Every view and download recorded with person and time, kept 6 years, visible to your administrators |
| §164.312(c)(1) Integrity | Submissions stored before receipt is confirmed; locked archive with S3 Object Lock in compliance mode; amendments attached to archive copies, which can’t be changed |
| §164.312(d) Person or entity authentication | Two factors for every account, with phishing-resistant passkeys as the default; failed sign-ins throttled |
| §164.312(e)(1) Transmission security | TLS 1.2 or later; HSTS; TLS required to the database; email over TLS or held in a secure portal |
| §164.314(a) Business associate contracts | Master BAA with the required terms; Schedule C for health data outside HIPAA |
| §164.316(b) Documentation | Written policies and procedures kept at least 6 years (§164.316(b)(2)); every schedule version and update notice kept (BAA §10.4) |
| §164.410 Breach notification by a business associate | Initial notice within 3 Business Days and full report within 10, with the contents §164.404(c) requires |
| §164.504(e) Business associate agreement terms | Master BAA built on the HHS sample provisions |
| §§164.524, 164.526, 164.528 Access, amendment, accounting | Help completed within 10 Business Days; amendments attached to archive copies; disclosures documented and kept 6 years; patient requests forwarded within 2 Business Days |
What we don’t claim
There is no official HIPAA certification; HHS doesn’t certify vendors. We don’t hold a third-party audit report such as SOC 2 today. What we offer instead is specific: a BAA with firm deadlines, service schedules that describe exactly how your data is handled, and answers to your security questionnaire. Ask, and we’ll complete it.
Earlier forms on our legacy service
Some organizations still use our earlier form service, which works differently. For those forms, LuxSci, our secure email and forms provider, receives each submission under its business associate agreement and delivers it by email to the organization, and our earlier application keeps no database of completed submissions. Those forms load LuxSci’s scripts. The portal, per-customer encryption keys and retention periods described on this page apply to the current platform. The earlier service stays under its existing agreements until each organization moves over.
Questions from compliance and IT reviewers
Can we read the BAA before we sign?
Yes. A sample of the Master BAA and the service schedules is published at /legal/baa/. Every customer signs the same master agreement.
Is our data in its own database?
No, and we say so in your schedule. All customers share one application, one database and one file store. Your records are kept apart by the application, by row-level security in the database, which we test, and by an encryption key unique to your organization.
Who at Fieldstone can see our patients’ submissions?
Only our authorized administrator and our designated emergency contractor, each with their own account, and only for the purposes your schedule lists: on Direct Delivery, to deliver or resend them, to fix a problem, in a documented emergency, or as you direct; on Workflow Portal, to support you, to fix a problem, in a documented emergency, or as you direct.
Can we see when Fieldstone accesses our data?
Yes. Your administrators see the full audit log on both plans, including every view and download by Fieldstone and our contractor.
How quickly will you tell us about an incident?
An initial notice within 3 Business Days of discovery, and a full report within 10, by email to your notice contact; a breach report also comes by phone. An unfinished investigation doesn’t delay either one.
What happens to our data if we leave?
On Workflow Portal, if you ask before the end or up to 10 days after, you get one free export. Then everything is deleted within 30 days, backups within a further 30, and archive copies are deleted when their one-year lock ends. Only audit and disclosure records are kept, for 6 years. The retention table has the details.
Can our staff delete submissions?
Not on Workflow Portal. Records can’t quietly disappear. We delete junk or duplicate submissions when you ask, and whenever the law requires.
What if a patient contacts Fieldstone directly?
We securely forward the request to you within 2 Business Days, or sooner if the law requires, and help you respond. We don’t decide the request ourselves unless you direct us or the law requires.
We aren’t a HIPAA covered entity. Can we still use Secure Form?
Yes. You sign the same Master BAA, and Schedule C protects your health information by contract, including deletion everywhere: from active systems within 30 days, and from backups within a further 30.
Will you change the terms on us?
Not in any way that reduces your protection without your written agreement. Other updates come with at least 30 days’ notice and a summary of what changed; only an urgent security update can come sooner.
Documents and contact
- Privacy Policy
- Master BAA and Service Schedules (sample)
- Services Agreement (PDF)
- Free Demo Terms
- Terms of Use
Security questions, questionnaires and requests for documents
Fieldstone Health, LLC14 Algonquian Drive, Natick, MA 01760
security@fieldstone-health.com · 617-237-0220