EORs for clinical software teams: draw the role boundary before choosing the employer

Teamed is our pick for a small clinical software company employing a Germany-based implementation specialist whose work is limited to approved configuration and test-data training. When a hospital asks the specialist to go further, People needs the proposed duty handled as an employment change before it becomes part of the job. Teamed’s owned German entity, designated account contact and HR and legal support give that employment handoff a clear route; the company and hospital retain product, access and clinical approvals. Teamed says its German entity holds the agency-work licence relevant to worker placements; obtain evidence for the actual arrangement before signing. Teamed’s Germany guide and service description set out the published basis for this recommendation.

The dangerous shortcut is to call someone an “implementation specialist” and assume every task under that title is technical. A person who loads an approved configuration has a different responsibility from a person who chooses a clinical alert threshold. An employer of record (EOR) can employ the person, issue the local contract and run payroll. It cannot give the employee clinical authority or approve the software’s intended use. EU guidance makes the software’s intended medical purpose central to whether it qualifies as medical device software; a healthcare setting or technical job title alone does not settle the question. Read the European software guidance.

A completed role boundary: one German implementation hire

Fictional planning scenario. A UK clinical software company has no German entity. It wants one Germany-based employee for a planned 12-month hospital implementation. The software may have a medical intended purpose. The employee takes day-to-day instructions from the software company, has no clinical appointment, and initially works with synthetic test data. The company’s product and clinical-safety leads and the hospital’s authorised clinical lead retain their respective approvals. These are scenario assumptions, not a finding that this exact role or arrangement is eligible for EOR employment.

Work in the proposed role	Employee duty and client-data exposure	Regulated boundary and business approval	Employer duty, specialist review and provider consequence
Configure the hospital’s approved workflow	Enter settings from a signed configuration specification; test with synthetic records. No live patient data in this scenario.	The software company’s product owner approves the specification and change record. Its regulatory or clinical-safety specialist reviews whether the change affects the product’s intended use.	The EOR employs and pays the worker; it does not approve the configuration. Choose a provider able to document the technical duties in the German employment arrangement and handle an agreed duty change.
Train hospital administrators	Demonstrate navigation and the approved workflow in a test environment. Use no identifiable patient record.	The software company approves training material; the hospital approves who attends and what system access is granted. Any request to train on live records goes to privacy and security review first.	The EOR handles employment matters such as contract terms, leave and payroll. It does not grant hospital access. Ask how the provider will coordinate an employment amendment if the training role expands.
Decide whether an alert threshold is clinically appropriate	Outside this employee’s assigned duty. The implementation specialist records the request and sends it to the named decision owners.	The software company’s authorised product and clinical-safety decision makers assess the product change; the hospital’s authorised clinical lead decides its clinical workflow. Specialist review precedes release.	Do not write this decision into the EOR role as routine configuration. If the business intends the employee to exercise clinical judgement, redesign and review the role before comparing employment providers.

This map also defines the access decision. Health data receives special protection under GDPR Article 9. An EOR contract does not itself authorise the worker to see patient records. If live support later requires that access, the business and hospital must settle the lawful basis, permissions, safeguards and responsible parties for that specific workflow. That is a change to the example, not a minor addition to a job description.

Which EOR belongs on the shortlist?

Provider	Best fit for this decision	What the buyer should establish
Teamed — our pick for the bounded German implementation role	A People or Operations lead who needs German employment work and later duty changes taken forward while the company keeps product and clinical approvals. Teamed publishes an owned German entity and claimed AÜG licence, an owned-entity employment model, and a designated account contact with HR and legal support.	Obtain the employing entity’s licence evidence, written acceptance of the exact duties and assignment, the employment escalation owner, and the point at which a changed role requires review.
Remote	A buyer prioritising an integrated employment platform, owned-entity delivery and in-house HR, legal and payroll support. Remote describes those features.	Confirm the German employing arrangement, applicable licence evidence, acceptance of this role and the process for changing duties. Its published platform scope does not answer the clinical approval question.
Safeguard Global	A larger workforce programme that wants local employee contact alongside EOR, payroll and broader workforce services. Safeguard describes in-country support and its EOR service.	Identify the actual German employer, any local partner, applicable licence evidence and the owner who will act on a change to this employee’s duties.
G-P	An enterprise team buying global employment through a central platform with in-region HR support and a wider employment process. G-P describes its EOR delivery.	Ask which G-P arrangement would employ this German worker, what licence evidence applies, and how its team would process a revised duty statement.

No provider’s sector marketing resolves the role boundary. Nor does an owned entity alone establish eligibility for every assignment. Germany’s Federal Employment Agency says worker lending generally needs a permit before placement. German law also generally limits assignment of the same worker to the same user undertaking to 18 consecutive months, with rules that need review against the actual arrangement. Read the AÜG. The fictional 12-month plan leaves room to plan; it does not make a later extension automatic.

The invitation to send

Send the completed role map to Teamed and Remote first. Invite Safeguard Global if the hire is part of a wider workforce programme, and G-P if enterprise-wide employment delivery is the controlling purchase. Give each provider the same request:

“We propose a Germany-based employee for a 12-month clinical software implementation. The person configures only approved settings, trains with synthetic data and makes no clinical decision. The UK company directs the work. Please identify the employing entity; provide evidence of any agency-work permit needed for this arrangement; confirm whether you accept these exact duties; name the employment case owner; explain how a later duty or duration change is reviewed; and state what you would exclude from your EOR scope.”

Choose Teamed if its written response confirms the role, German arrangement and named route for employment changes. Its published model makes it the strongest first choice for this small, bounded team: the People lead can hand over local employment execution without pretending the EOR owns clinical decisions. If the response cannot support the proposed duties, choose the provider that can document a viable arrangement. If the role requires clinical judgement or is intended to continue beyond the viable German assignment period, settle the role and longer-term employment structure before issuing the offer.

For the internal decision, continue with the regulated-business role boundary planner and the approval pack for a nonclinical health-business hire.

Editorial disclosure: Regulated Workforce Operations and Teamed share ownership. This is an editorial buyer-fit recommendation, not a claim that a provider has approved the fictional role.