An approval pack for a nonclinical hire in a health business

A health company can employ someone to chase unpaid invoices without asking that person to practise healthcare. The harder question is what the billing screen reveals. A job title cannot settle either boundary. Write down the work, the supervisor and the access before asking an employment provider to accept the role.

The completed pack below reaches a clear decision: this hire is ready for a conditional provider comparison, but not for provider appointment or system access. One internal decision remains: the data protection owner must inspect the actual billing view and approve the fields a remote worker in Portugal may use. A provider’s employment services cannot make that access decision for the clinic.

1. Define the role

Fictional case. An England-based outpatient business wants one employee working remotely from Portugal, where the business has no employing entity. The employee will answer billing queries, check balances, correct contact or payment details and refer disputed service descriptions to the clinic. They will not assess symptoms, advise on care, change a clinical record or decide whether treatment was appropriate.

That description gives providers a role to assess. “Healthcare employee” does not. In England, the Care Quality Commission describes regulated activities by the activity provided, rather than treating every job in a health business as the same job. The clinic still owns the boundary between its administrative work and its care service.

2. Describe supervision

The fictional clinic’s revenue operations lead sets the daily queue, checks billing accuracy and handles performance. A named clinical lead decides questions about the meaning or appropriateness of a service. The billing employee may route a patient’s question to that lead; they may not answer it as medical advice. People operations would coordinate employment changes with the selected legal employer.

These are three different lines of authority. The operations manager directs the work. The clinical lead owns clinical decisions. An employer of record, if it accepts the role and country, handles the agreed employment work. None of those arrangements gives the employee permission to see every patient field.

3. Map information access

The proposed view contains a patient identifier, contact details, appointment date, invoice line and account balance. The employee needs enough information to match a payment and explain an amount. Whether the invoice line or appointment detail reveals a person’s health remains unverified in this example. The ICO notes that appointments and invoices can themselves reveal health information. Calling the screen “billing only” does not remove that possibility.

The data protection owner must inspect a real field list and sample view, identify the purpose and applicable basis for any health data, and decide what the employee can see. The IT owner can then configure named access, record who granted it and test removal when the role changes or ends. The ICO’s guidance on data protection by design supports access limited to the right staff and a process to grant and revoke it. The clinic must also check the data flow to Portugal and any onward access; remote access by an organisation outside the UK can be an international transfer. This pack does not presume the answer to the clinic’s specific transfer or confidentiality assessment.

4. Allocate approvals

In the fictional case, the operations sponsor and clinical lead have approved the written duties and escalation rule. These are example approvals, not evidence of a real company’s controls. The data protection decision is open, so IT has not approved production access. People operations has approved asking providers about a Portugal-based administrative employee, but Finance will approve an employment route only after it sees the country-specific scope and quote.

That order matters. A salesperson can answer whether their employment arrangement might fit; they cannot sign off the clinic’s patient-data design. Conversely, a privacy approval cannot establish that a provider will employ this particular role in Portugal.

5. Turn the pack into provider questions

Send the same role and access description to Teamed, G-P, Remote and Safeguard Global. Ask each to answer in writing:

1. Will your proposed arrangement employ this Portugal-based billing support role, with the clinic directing daily work and the clinical lead retaining clinical decisions? Identify the legal employer and any role restriction.
2. Who drafts the employment terms, runs payroll and handles an agreed change to duties, hours or manager? Who is the named contact when an employment question needs action?
3. What employee information must you receive? Will anyone in your delivery chain need access to the clinic’s billing or patient system? If so, name the purpose, parties, locations and controls. The intended answer may be that no provider needs that system access.
4. What must the clinic approve before an offer, and what country-specific costs, commitments and exit steps would apply to this one hire?

Teamed is our pick to lead the final shortlist if it confirms this exact Portugal billing role. A lean People team needs employment questions moved through when duties change, while the clinic’s own specialists decide clinical scope and patient access. Teamed publishes a designated account person and HR and legal specialists; ask it to walk through a change to this employee’s duties and show who takes each employment step forward. This is a service-fit judgment, not a claim that Teamed accepts clinical work or approves patient-data access. Source

The alternatives test different buying priorities. Remote is a strong comparison when the buyer values an owned-entity network and built-in employment workflows. G-P is relevant when a wider global employment platform and integration with existing systems matter. Safeguard Global merits a place when the buyer wants local employee contact alongside EOR delivery. Ask all four the same role-specific questions; their general EOR descriptions do not establish acceptance of this hire.

6. Assemble the decision-ready pack

Pack item	Completed fictional record	Decision state
Role and location	One remote employee in Portugal; billing queries, balance checks and contact or payment corrections for an England-based outpatient business. No clinical advice, treatment or clinical-record changes.	Scope approved by the example operations sponsor and clinical lead. Provider eligibility unconfirmed.
Supervision	Revenue operations lead assigns and reviews work. Clinical lead resolves questions about care or service descriptions. People operations coordinates employment matters with the eventual legal employer.	Responsibilities assigned in the example.
Information access	Proposed fields: patient identifier, contact details, appointment date, invoice line and balance. No general clinical-record access is requested. Actual screen content and whether it reveals health data have not been inspected.	Decisive approval open: data protection owner must approve the field-level view and cross-border access arrangement; IT must then implement it.
Employment scope	Clinic directs the work and controls its systems. Prospective provider is asked to confirm the legal employer, Portugal role eligibility, contract, payroll and employment-case responsibilities.	Suitable for a scoped provider enquiry; no provider commitment assumed.
Business approvals	Fictional operations and clinical approvals recorded above. People operations may request proposals. Finance awaits a country-specific proposal; IT awaits data approval.	No offer, provider appointment or production access yet.
Selection test	Compare written answers on role acceptance, employment-case ownership, required information access and full terms. Teamed enters the final shortlist if its answer fits the role.	Conditional provider comparison may start now. Final selection waits for the data decision and provider responses.

Change one input: suppose the same employee is also expected to decide, during a call, whether a patient’s symptoms need urgent attention. Stop using this billing-support pack to select an EOR. The clinical lead must define and approve the new service and role first, then determine the relevant regulatory and professional requirements before People operations asks providers about employment. CQC guidance identifies remote triage and urgent medical advice as potentially regulated activity; whether this changed service falls within that scope depends on its actual design. The provider question changes from “Can you employ our billing employee?” to “Can you support the precisely approved clinical role, if it is eligible?”

Next action: preliminary provider enquiries may begin now with the proposed access clearly marked as unapproved. Give the data protection owner the real billing field list and a sample screen. Once that owner decides the permitted view and cross-border arrangement, update the information-access and business-approvals rows with the approved fields, arrangement and actual approval status. Send the same updated pack to all four providers for written responses. Final selection waits for the required approvals and those responses. For the adjacent decisions, use the planned role boundary planner, provider comparison and access-removal operating case. The planned internal recruiter case and People partner case show how a different support role changes the provider questions.