FAQ
Frequently asked questions
Short answers, including the ones that are a plain no.
Scope and availability
Can I sign up or start a trial?
No. There is no self-serve sign-up, trial or demo account. Environments are configured only after a scope discussion and an agreement with the organisation.
What is the current platform status?
Implementation-led delivery. PulseArc is delivered as a configured implementation for healthcare organisations. Modules, integrations and scope are agreed with each organisation in writing, and every environment is configured for that organisation alone. PulseArc supports administrative and operational work only — it does not provide medical advice, diagnosis, treatment or emergency response.
Does PulseArc provide any clinical function?
No. PulseArc does not provide medical advice, diagnosis, treatment, triage, clinical decision-making, emergency response, patient monitoring or prescription management.
Is PulseArc compliant with a specific healthcare or privacy regulation?
PulseArc does not claim compliance with, or certification against, any healthcare, privacy, payment-card, cybersecurity or medical-device standard. Regulatory obligations that apply to an organisation are that organisation's own, and any specific arrangement is confirmed in writing during implementation.
Where is data hosted?
No hosting-location claim is published on this website. Hosting arrangements, including any cross-border processing, are documented for each organisation during implementation.
Does PulseArc integrate with my existing system?
Not unless it has been assessed and confirmed for your organisation. No integration is listed or implied on this website.
Can patients use PulseArc?
No. The platform is used by an organisation's own authorised staff. There is no patient portal and no patient-facing account.
Does PulseArc take payments or issue receipts?
No. The platform does not process patient payments or issue receipts, and PulseArc is not a payment institution or merchant of record.
Why is there no pricing page?
Commercial packages, tax treatment, contractual scope and support commitments are not finalised for publication. Pricing is discussed directly with the organisation.
Can I see a customer reference?
No customer reference is published. Implementation examples are shared during a suitable organisation-level discussion, subject to confidentiality and approval.
Working with us
How does an engagement usually start?
With a scope conversation, not a demonstration. We ask how your administration currently runs, who owns each step and where you would not want technology involved. If the answers put the work outside the current platform scope, we say so in that conversation.
Who from our side needs to be involved?
An executive sponsor who can approve scope, an operations owner who knows how the workflow really runs, and a nominated administrator who will manage user access afterwards. Where a source system is in question, its internal owner joins the data and access assessment.
What do we receive in writing?
A discovery summary, a scope and responsibility statement, a data and access assessment, a configuration record, a validation sign-off and an administrator handover pack. Each has a named owner and is held by both sides.
How long does an implementation take?
No timeline is published, because it depends on how quickly the organisation can confirm scope, ownership and data authority. Any dates that apply to a specific engagement are set in the applicable agreement.
Can we change the configuration after handover?
Yes, through the documented change-request route. Changes are recorded so there is a single history of what was requested, approved and applied.
What happens if the platform is not the right fit?
We decline the work. Shaping a proposal around a capability that does not exist creates a problem for your organisation and for ours.
Data, access and security
What data does PulseArc hold about our organisation?
Enquiry details submitted through this website, account and user administration data for named staff, the operational records your own users create in the configured environment, and technical logs such as sign-in and administrative events.
Do you need access to clinical records?
No. Clinical record systems are treated as out of scope unless a separate assessment, privacy review and written agreement are completed for that organisation.
Who decides which of our staff can see what?
Your organisation does. You nominate administrators, maintain the user list and set cross-site visibility rules. PulseArc supplies the tools, not the decisions.
How do we report a security concern?
Email management@pulsearc.online with what you observed, when, and any reference you have. Do not include patient information in the report.
Something not answered here? Email management@pulsearc.online.
Ask the question directly.
If the answer is not published, ask for it and we will answer in writing.