NextDayDoctor is a telehealth service that handles protected health information. This page sets out the controls we operate to protect it. It is generated from our compliance system rather than written by hand, so it reflects the programme as it currently stands.
The controls we operate, grouped as a reviewer would expect to find them. A mark indicates a control we operate. Internal control identifiers, owners, verification methods, schedules and per-control results are not published here; they are part of the evidence shared under a confidentiality agreement.
How the production environment is reached, watched and physically protected.
| Access granted only on documented authorization Access is registered, authorized and credentials issued only after an approved request identifying the access needed. | ✓ |
| Access list reviewed on a cycle The list of people holding access is reviewed on a regular cycle, and access no longer needed is removed. | ✓ |
| Access revoked on termination or role change Access is removed or modified promptly when a workforce member leaves or changes role, and the removal is evidenced. | ✓ |
| Account management process Accounts are created, modified, disabled and deleted through a defined process, with dormant accounts identified and removed. | ✓ |
| Automatic logoff and session timeout Electronic sessions terminate after a predetermined period of inactivity on systems holding sensitive information. | ✓ |
| Emergency access procedure Procedures exist for obtaining necessary access to sensitive information during an emergency, and their use is logged and reviewed afterwards. | ✓ |
| External access protections The company implements protections against security threats from sources outside its system boundaries. | ✓ |
| Least privilege enforced Access is granted at the least level of privilege required for the role, and elevated rights are the exception rather than the default. | ✓ |
| Logical access security architecture Logical access security software, infrastructure and architectures are implemented over protected information assets. | ✓ |
| Multi-factor authentication enforced Multi-factor authentication is required for administrative and remote access to production systems and to systems holding sensitive information. | ✓ |
| Password policy enforced Procedures govern the creation, changing and safeguarding of passwords, and the policy is enforced technically where the platform allows. | ✓ |
| Periodic access review User access to systems and data is reviewed on a defined basis against current role, and anything no longer warranted is removed. | ✓ |
| Privileged access restricted and reviewed Administrative and privileged accounts are limited to named individuals with a demonstrated need, inventoried, and reviewed more frequently than standard access. | ✓ |
| Service and machine accounts inventoried Non-human accounts are inventoried, owned by a named person, scoped to least privilege and rotated on a defined cadence. | ✓ |
| Unique user identification Every workforce member is assigned a unique name or number for identifying and tracking their identity in systems holding sensitive information. | ✓ |
| Access to patient information reviewed Records of who accessed patient information are reviewed on a regular cycle. | ✓ |
| Alerting on security-relevant events System components are monitored for anomalies indicating malicious acts, natural disasters and errors, and alerts reach someone who acts on them. | ✓ |
| Audit logging enabled Hardware, software and procedural mechanisms record and examine activity in systems that hold or use sensitive information. | ✓ |
| Availability monitoring System availability is monitored against the company's commitments, with alerting on degradation. | ✓ |
| Clocks synchronised to a reliable source System clocks are synchronised to a reliable time source, so that log timestamps can be relied on. | ✓ |
| Configuration drift detected Deviation from secure configuration baselines is detected and corrected. | ✓ |
| Log integrity protected Logs are protected against modification and deletion, including by the accounts whose activity they record. | ✓ |
| Log retention period defined Logs are retained for a defined period sufficient to support investigation and the applicable regulatory requirement. | ✓ |
| Log review performed Records of information system activity — audit logs, access reports, incident tracking — are reviewed on a defined basis. | ✓ |
| Logs kept free of secrets and regulated data Logs are kept free of credentials, secrets and regulated data. | ✓ |
| Malware detection alerting Malware detections are alerted on and investigated rather than only logged. | ✓ |
| Monitoring and alerting themselves tested Monitoring and alerting are tested periodically to confirm they still detect and raise what they are meant to. | ✓ |
| Network infrastructure managed Network devices and services are inventoried, securely configured and kept current. | ✓ |
| Network monitoring and defence Network traffic is monitored for malicious activity, and defences are maintained at the network boundary. | ✓ |
| Penetration testing performed Independent testing of the company's defences is performed on a defined basis and its findings are tracked to closure. | ✓ |
| Remediation timeframes defined Findings are assigned remediation timeframes by severity, and exceptions are approved rather than silent. | ✓ |
| Vulnerability scanning performed The company detects and monitors changes to configurations and newly identified vulnerabilities on a defined cadence. | ✓ |
| Contingency access to facilities Procedures allow facility access in support of restoration of lost data under the disaster recovery and emergency mode operations plans. | ✓ |
| Data centre physical security assured Where hosting is outsourced, physical security at the provider is assured through its assurance reporting rather than assumed. | ✓ |
| Facility access controls Policies limit physical access to facilities and systems while ensuring properly authorized access is allowed. | ✓ |
| Media movement recorded Movements of hardware and electronic media holding sensitive information are recorded, including the person responsible. | ✓ |
Who is accountable, what the policies require, and how the people with access are screened and trained.
| Approved technology and devices The technologies, services, channels and devices that may be used are approved in advance and bounded. | ✓ |
| Code of conduct acknowledged on hire and periodically Workforce members acknowledge the code of conduct on hire and periodically thereafter, and the acknowledgements are retained. | ✓ |
| Code of conduct established The company maintains a written code of conduct setting out expected standards of integrity and ethical behaviour for the workforce. | ✓ |
| Conflicting duties separated or compensated Conflicting duties are separated where possible, and compensating controls are applied and recorded where they cannot be. | ✓ |
| Conflicts of interest disclosed and approved Conflicts of interest and related-party arrangements are disclosed and approved. | ✓ |
| Control deficiencies tracked to resolution Identified internal control deficiencies are recorded, assigned an owner and tracked through to remediation. | ✓ |
| Decisions recorded by the capacity they were made in Where one person holds more than one role, each decision is recorded in the capacity it was made, and independence is claimed only where it genuinely exists. | ✓ |
| Ethics and security concern reporting channel A channel exists for workforce members to report ethical or security concerns, including anonymously where practicable, without fear of retaliation. | ✓ |
| External communication of security commitments The company communicates its security commitments and relevant obligations to customers, partners and other external parties. | ✓ |
| Information security policies established and approved The company maintains written information security policies, approved by management, that state what must be true and who is accountable. | ✓ |
| Internal communication of security responsibilities Security objectives and individual responsibilities are communicated internally to the people who have to carry them out. | ✓ |
| No retaliation for raising a concern No one is intimidated or retaliated against for making a privacy complaint or raising a security concern. | ✓ |
| Periodic technical and non-technical evaluation The company performs a periodic evaluation of how well its safeguards meet its security requirements, and after environmental or operational changes. | ✓ |
| Policies reviewed and re-approved on a defined cadence Each policy is reviewed periodically, and after any material change in operations, law or risk, and is re-approved on the record. | ✓ |
| Policy and procedure documentation retained Policies, procedures and required records are retained for the period the applicable standard or regulation requires, and remain available to the people who need them. | ✓ |
| Privacy official designated The company has designated a privacy official responsible for developing and implementing its privacy policies and procedures. | ✓ |
| Security official designated The company has designated a security official responsible for developing and implementing its security policies and procedures. | ✓ |
| Security roles and responsibilities assigned Security responsibilities are assigned to named roles, and the assignment is documented rather than assumed. | ✓ |
| Background screening before access Background checks appropriate to the role and to law are completed before a workforce member is granted access to sensitive information. | ✓ |
| Competence assessed and developed The company demonstrates a commitment to attract, develop and retain competent individuals in alignment with its objectives. | ✓ |
| Confidentiality agreements signed Workforce members and contractors sign confidentiality obligations before handling sensitive information. | ✓ |
| Offboarding checklist completed A documented offboarding process covers access revocation, asset return and final acknowledgements, and its completion is evidenced. | ✓ |
| Onboarding checklist completed A documented onboarding process covers access provisioning, agreements and training, and its completion is evidenced. | ✓ |
| Periodic security awareness training The workforce completes security awareness training on a defined basis, and completion is evidenced. | ✓ |
| Periodic security reminders Security reminders are issued to the workforce periodically and recorded. | ✓ |
| Personnel records minimised and segregated Personnel records are minimised, access-restricted, and kept separate from other systems. | ✓ |
| Phishing and social engineering awareness The workforce receives practical training or simulation on phishing and social engineering, the most common initial access route. | ✓ |
| Privacy training delivered Workforce members are trained on the privacy policies and procedures relevant to their functions. | ✓ |
| Sanction policy established The company applies appropriate sanctions against workforce members who fail to comply with its security policies and procedures. | ✓ |
| Sanctions applied and documented Where a violation occurs, the sanction applied — including a decision that none was warranted — is recorded. | ✓ |
| Security awareness training at hire New workforce members complete security and privacy awareness training before or shortly after being granted access. | ✓ |
| Security responsibilities in job descriptions Role definitions state the security responsibilities attached to the role, so competence can be assessed against them. | ✓ |
| Workforce clearance procedure Procedures determine that a workforce member's access to sensitive information is appropriate to their role. | ✓ |
How changes reach production, and how the equipment used to make them is configured.
| Branch protection enforced Deployable branches are protected so that changes cannot bypass review and required checks. | ✓ |
| Change management process defined Infrastructure, data, software and procedural changes are authorized, designed, developed, tested, approved and implemented under a defined process. | ✓ |
| Changes tested before release Changes are tested before release, and the testing performed is evidenced. | ✓ |
| Dependency vulnerability scanning Third-party dependencies are scanned for known vulnerabilities and remediated within a defined window. | ✓ |
| Emergency change procedure Emergency changes follow a defined path with after-the-fact review and approval, rather than no path at all. | ✓ |
| Environments separated Development, test and production environments are separated, with access to production restricted accordingly. | ✓ |
| Peer review before merge Code changes are reviewed by someone other than the author before being merged to a deployable branch. | ✓ |
| Rollback capability maintained A tested means of reverting a change exists, so that a failed release can be withdrawn rather than fixed forward under pressure. | ✓ |
| Secure coding practices applied Developers follow documented secure coding practices appropriate to the languages and frameworks in use. | ✓ |
| Secure development lifecycle documented The company documents how software is designed, built, reviewed and released, including its security requirements. | ✓ |
| Automatic screen lock enforced Endpoints lock automatically after a period of inactivity and require authentication to resume. | ✓ |
| Endpoint inventory maintained The company maintains an inventory of the endpoints that access its systems or hold sensitive information. | ✓ |
| Endpoint safeguards confirmed before access Endpoint safeguards are confirmed before access is authorized, and again after any failure. | ✓ |
| Full-disk encryption on workstations Workstations and portable devices that may hold sensitive information encrypt data at rest, so that a lost device is a lost device rather than a disclosure. | ✓ |
| Operating system and application patching Endpoints receive security updates for the operating system and installed applications within a defined window. | ✓ |
| Removable media controls The use of removable media with sensitive information is controlled, and media are encrypted or prohibited according to policy. | ✓ |
| Secure configuration baselines applied Endpoints and servers are configured against a documented secure baseline rather than vendor defaults. | ✓ |
| Workstation physical safeguards Physical safeguards restrict access to workstations that access sensitive information to authorized users. | ✓ |
| Workstation security baseline Workstations used to reach production are held to a security baseline covering disk encryption, automatic screen lock, host firewall and application controls. | ✓ |
| Workstation use policy Policies specify the proper functions to be performed on workstations that access sensitive information and the manner in which they are performed. | ✓ |
Risk assessment, incident handling, continuity, and oversight of the suppliers in the chain.
| Change-driven risk reassessment The company identifies and assesses changes that could significantly affect its system of internal control, and reassesses risk accordingly. | ✓ |
| Objectives specified to enable risk identification The company specifies its objectives with sufficient clarity to allow the identification and assessment of risks to those objectives. | ✓ |
| Risk acceptance documented and approved Where a risk is accepted rather than treated, the acceptance, its rationale and its approver are recorded. | ✓ |
| Risk assessment performed periodically The company conducts an accurate and thorough assessment of the risks and vulnerabilities to the confidentiality, integrity and availability of the information it holds. | ✓ |
| Risk register maintained Identified risks are recorded in a register with their likelihood, impact, owner and current treatment status. | ✓ |
| Risk treatment plans tracked to completion The company implements security measures sufficient to reduce risks to a reasonable and appropriate level, and tracks those measures to completion. | ✓ |
| Security exceptions registered and time-bound Security exceptions are recorded with a named owner, a defined scope, an expiry date and a review date. | ✓ |
| Security management process established The company implements policies and procedures to prevent, detect, contain and correct security violations. | ✓ |
| Breach risk assessment performed For each suspected breach the company performs and documents a risk assessment determining whether notification is required. | ✓ |
| Business associate breach reporting Contracts require business associates to report breaches to the company, and received reports are acted on. | ✓ |
| Every incident assessed against the breach standard Every incident involving patient information is assessed against the formal breach standard, and the assessment is recorded. | ✓ |
| Incident evidence preserved Evidence from a security incident is preserved with a documented chain of custody. | ✓ |
| Incident response plan documented A security incident response programme defines containment, remediation, communication and recovery. | ✓ |
| Incident response plan tested The incident response plan is exercised on a defined basis, and the exercise is evidenced. | ✓ |
| Incident response plan tested periodically The incident response plan is exercised on a defined cycle, not only when an incident occurs. | ✓ |
| Incident response roles assigned Named roles and contacts are defined for incident response, including who may declare an incident. | ✓ |
| Incident severity classification Incidents are classified by severity so that response effort and escalation match the actual exposure. | ✓ |
| Incidents reported within the required window Security incidents and breaches are reported to the responsible party within the time the contract requires. | ✓ |
| Notification to affected individuals Affected individuals are notified of a breach of unsecured protected information without unreasonable delay and within the required period. | ✓ |
| Notification to the media where required Where a breach affects more than the threshold number of residents of a State or jurisdiction, prominent media outlets are notified. | ✓ |
| Notification to the regulator Breaches are reported to the Secretary in the form and within the period the rule requires, and the log of reportable breaches is maintained. | ✓ |
| Post-incident review performed After a material incident the company reviews what happened and feeds the lessons into its controls and its next test. | ✓ |
| Public vulnerability reporting channel A public channel is maintained for reporting security vulnerabilities, and its reachability is checked automatically. | ✓ |
| Recovery from identified incidents The company recovers from identified security incidents and restores affected systems and data to a known good state. | ✓ |
| Security events evaluated for significance Detected security events are evaluated to determine whether they represent a control failure or an incident. | ✓ |
| Security incidents identified and documented Suspected and known security incidents are identified, documented and their outcomes recorded. | ✓ |
| Application and data criticality analysis The company assesses the relative criticality of specific applications and data in support of its contingency plan. | ✓ |
| Backup success monitored, including silent failure Backup success is monitored for each system, including detecting when a backup did not run at all. | ✓ |
| Backups isolated and protected from deletion Backups are held in a separate failure domain and protected against premature deletion. | ✓ |
| Backups performed on a defined schedule Retrievable exact copies of sensitive information are created and maintained on a defined schedule. | ✓ |
| Backups restored to prove they work Backups are periodically restored to confirm that they can actually be recovered from. | ✓ |
| Business continuity and disaster recovery plan A contingency plan establishes how the company responds to an emergency or other occurrence that damages systems holding sensitive information. | ✓ |
| Capacity monitored and managed Current processing capacity and use are monitored and managed to meet the company's objectives. | ✓ |
| Continuity plans exercised Business continuity and disaster recovery plans are exercised. | ✓ |
| Data recovery capability The company maintains a data recovery capability sufficient to restore in-scope systems to a known good state. | ✓ |
| Emergency mode operation Procedures exist to enable continuation of critical processes and protection of sensitive information while operating in emergency mode. | ✓ |
| Recovery objectives defined Recovery time and recovery point objectives are defined for each material system and are consistent with the continuity plan. | ✓ |
| Recovery plan tested periodically Recovery plan procedures supporting system recovery are tested on a defined basis, and the results are recorded. | ✓ |
| Agreement in place before a supplier receives patient information A business associate agreement is executed before any supplier is given access to patient information. | ✓ |
| Periodic vendor review Vendors are reviewed on a defined basis against their risk tier, and the review is evidenced. | ✓ |
| Security commitments in vendor contracts Contracts with vendors handling sensitive information carry security, confidentiality and notification commitments. | ✓ |
| Subcontractor flow-down obligations Vendors are required to impose equivalent obligations on their own subcontractors that handle the company's data. | ✓ |
| Supplier term differences disclosed and authorized Where a supplier's standard terms differ from what is required, the difference is disclosed and authorized before any regulated data flows. | ✓ |
| Suppliers reviewed periodically Suppliers are reviewed on a defined cycle, and the review is recorded. | ✓ |
| Vendor assurance reports reviewed Where a vendor provides an assurance report, it is obtained and reviewed, including its complementary user entity controls. | ✓ |
| Vendor inventory maintained The company maintains an inventory of vendors and business partners, including what data each one can reach. | ✓ |
| Vendor offboarding When a vendor relationship ends, access is revoked and the return or destruction of data is confirmed. | ✓ |
| Vendor risk assessed before onboarding Risks associated with a vendor are assessed before the vendor is given access to systems or data. | ✓ |
| Written agreements with business associates The company obtains satisfactory assurances, through a written contract, that each business associate will appropriately safeguard the information it receives. | ✓ |
Encryption, retention, disposal, and the limits on how patient information may be used.
| Accounting of disclosures maintained The company can produce an accounting of disclosures of an individual's information on request. | ✓ |
| Agreement sought before sharing with family or carers Patients are given the opportunity to agree or object before information is shared with family or others involved in their care. | ✓ |
| Artificial intelligence use approved and contractually covered Any use of artificial intelligence or external processing is approved in advance, covered by contract, and reviewed. | ✓ |
| Authorization obtained where the law requires it Where a patient's written authorization is required before information is used or disclosed, it is obtained first. | ✓ |
| Confidential communication requests honoured Reasonable requests to receive communications by a particular method, or at a particular address, are accommodated. | ✓ |
| Cryptographic key management Cryptographic keys are generated, stored, rotated and revoked under a documented procedure, with access restricted. | ✓ |
| Data classification scheme defined The company identifies and maintains the categories of information it holds, so that protection can be applied according to sensitivity. | ✓ |
| Data integrity controls The company protects sensitive information from improper alteration or destruction, and can detect when it has occurred. | ✓ |
| De-identification held to the formal standard Information is treated as de-identified only where it meets the formal regulatory standard, and only with prior written approval. | ✓ |
| Disclosure to third parties controlled Personal information is disclosed to third parties only for identified purposes and with the consent or authority required. | ✓ |
| Encryption at rest Sensitive information is encrypted at rest in databases, object storage and backups. | ✓ |
| Encryption in transit Sensitive information is encrypted in transit over networks using current, non-deprecated protocols and cipher suites. | ✓ |
| Identity and authority verified before disclosure The identity and the authority of anyone requesting patient information are verified before any disclosure is made. | ✓ |
| Individual right of access honoured Individuals can inspect and obtain a copy of their information within the period the applicable rule requires. | ✓ |
| Information returned or destroyed when a relationship ends Patient information is returned or securely destroyed at the end of a processing relationship. | ✓ |
| Inventory of sensitive data locations The company maintains an inventory of where sensitive information is stored, processed and transmitted, including third-party locations. | ✓ |
| Legal holds placed, tracked and released Where records must be preserved for a legal matter, a hold is placed, tracked, and released only on proper authority. | ✓ |
| Minimum necessary use and disclosure Patient information is used and disclosed only for permitted purposes, and only to the minimum extent needed for that purpose. | ✓ |
| No waiver of privacy rights as a condition of care No patient is asked to give up their privacy rights in order to receive care. | ✓ |
| Notice of privacy practices provided The company provides a notice describing how it uses and discloses personal information, and updates it when practices change. | ✓ |
| Personal information kept accurate Personal information is maintained accurate, complete, current and relevant for the purposes for which it is used. | ✓ |
| Privacy inquiries and complaints handled A process exists for receiving and resolving inquiries, complaints and disputes about privacy practices. | ✓ |
| Production data restricted in non-production Live sensitive data is not used in development or test environments, or is masked before it is. | ✓ |
| Records destruction notices issued Notices required by state law about the destruction of health records are posted and delivered. | ✓ |
| Restriction requests handled The company has a process for receiving and deciding requests to restrict uses and disclosures. | ✓ |
| Retention schedule defined and applied Retention periods are defined for each category of information and applied in practice, not only on paper. | ✓ |
| Right to amendment honoured Individuals can request amendment of their information, and the company responds and records the outcome. | ✓ |
| Secure disposal of information and media Information and the media holding it are disposed of securely at end of life, in accordance with the retention schedule. | ✓ |
| Transmission security procedures Technical security measures guard against unauthorized access to sensitive information transmitted over an electronic network. | ✓ |
| Use limited to identified purposes The use of personal information is limited to the purposes identified in the notice given to data subjects. | ✓ |
Partners, payers and prospective practices can request our policies, a risk assessment summary, a current statement of open items, or a business associate agreement. Shared under a confidentiality agreement.
If you believe you have found a security vulnerability in this service, please write to us. We will acknowledge your report and keep you informed while we investigate.
How patient information is handled, and the rights that attach to it, are set out in our Privacy Policy and Notice of Privacy Practices.