Frequently Asked Questions
Straight Answers Before You Commit to a Hospital System
Replacing a hospital information system is a decision your team lives with for years. These are the questions hospital directors, IT managers, and medical record teams actually ask us — answered without sales language.
01 / About ASTECH
The company behind the system
Who is ASTECH?
ASTECH is the healthcare technology brand of PT Alfatih Solusindo Technology, an Indonesian company that builds and implements information systems for hospitals, clinics, laboratories, and imaging centres. We are not a reseller of foreign software: the products are designed, built, and supported here.
What makes ASTECH different from other hospital system vendors?
Most facilities end up with a hospital information system from one vendor, a laboratory system from another, and accounting from a third — then pay for years to keep them talking to each other. ASTECH is built as one connected ecosystem, so clinical, diagnostic, and financial data already share the same foundation instead of being stitched together afterwards.
What kind of facilities do you work with?
General and specialist hospitals across class A to D, primary clinics, standalone laboratories, imaging centres, and hospital groups running several sites under one management. Scope and edition are matched to the size of the facility, so a 40-bed hospital is not asked to buy what a 400-bed hospital needs.
Can we speak to hospitals already using the system?
Yes, once a conversation has reached the point where it is useful for both sides. We do not publish customer names without written consent, so reference calls and site visits are arranged individually rather than listed on the website.
02 / Products & Solutions
What you can actually run
What is SIMRS Medicare?
SIMRS Medicare is our hospital information system: registration, outpatient and inpatient care, electronic medical records, pharmacy, billing, and management reporting in one flow. It is the core most facilities start from, and the rest of the ecosystem plugs into it.
Do we have to take the whole ecosystem at once?
No. Almost no hospital does. Most start with the core system, then add modules such as laboratory, imaging, asset, linen, or CSSD once the first phase is stable. Because the modules share one database, adding the second one is configuration work rather than a new integration project.
Do you cover radiology and laboratory as well?
Yes. MediPACS handles imaging storage, viewing, and radiology workflow, while MediSyncLab covers the laboratory chain from order to validated result. Both write back into the patient record automatically, so results are not re-typed.
What supporting operations are covered beyond clinical care?
Medical asset and maintenance tracking, linen circulation, CSSD instrument sterilisation traceability, procurement, finance and accounting, human resources, training, and patient relationship management. These are the areas that quietly consume hospital budget and are usually managed on spreadsheets.
Is there anything for patients themselves?
Yes. Patients can book appointments, see queue position, and access their visit history from a mobile application, which reduces both counter congestion and phone traffic to the registration desk.
Where does AI fit in, and is it safe clinically?
Our AI features support decisions; they do not make them. They surface patterns, flag risks, and prepare summaries for the clinician, who remains the one who decides and signs. Any suggestion is traceable to the data it came from, so it can be checked rather than trusted blindly.
03 / Implementation & Migration
How a rollout actually runs
How long does implementation take?
It depends on the size of the facility and how ready its data and processes are, not on how fast we can install software. A focused rollout at a small hospital moves considerably faster than a multi-site group replacing several legacy systems at once. We give a dated plan after the assessment rather than a number before it.
What are the stages of a project?
Assessment of current processes, blueprint and sign-off, configuration, data migration, user training, parallel run, go-live, and post go-live stabilisation. Each stage has a named owner on both sides, because the stage that usually slips is the one nobody on the hospital side was assigned to.
Can our data from the current system be migrated?
Yes, and it is scoped during the assessment rather than assumed. Patient masters, visit history, medical records, stock, and receivables are the usual candidates. What can be moved cleanly depends on the quality and accessibility of the existing data, which we check before promising it.
Is staff training included?
Yes. Training is delivered by role — registration, nursing, doctors, pharmacy, laboratory, finance, and management each get their own session, not one generic system walkthrough. We also train internal champions so the hospital is not dependent on us for every new employee.
Can we run the old system in parallel during the switch?
Yes, and for most hospitals we recommend it. A parallel period lets staff build confidence and lets both systems be compared on real transactions before the old one is retired. The length of that period is agreed in the plan so it does not drift indefinitely.
Who provides the servers and network?
Either side can. Some hospitals already have infrastructure and internal IT; others prefer us to arrange hosting and take that off their plate. What matters is that the specification is agreed during the blueprint, because undersized infrastructure shows up as slow screens that get blamed on the software.
04 / Integration & Compliance
Talking to the systems you are required to talk to
Is the system integrated with BPJS Kesehatan?
Yes. BPJS integration is part of the architecture, not an add-on module, and its readiness is verified during the blueprint stage against the services your facility actually uses.
Does it send data to SATUSEHAT?
Yes. The system supports SATUSEHAT reporting through the FHIR standard, so encounters and clinical data are submitted from the normal workflow instead of being re-entered into a separate portal by staff at the end of the day.
Can it integrate with systems we already own?
Yes, and this is a common requirement. Laboratory analysers, imaging modalities, accounting software, payroll, banking, and queue displays are the usual ones. Each interface is scoped during assessment, since integration effort depends entirely on what the other system exposes.
Does it help with accreditation and ministry reporting?
Yes. Reporting for accreditation and for the health ministry is generated from the same operational data staff already enter, which is what makes it defensible during a survey. Indicators that cannot be derived from real transactions are flagged rather than estimated.
What happens when a regulation changes?
Regulatory changes affecting the national services we connect to are handled as part of the ongoing support relationship. This is one of the practical reasons hospitals prefer a local vendor: a change announced in Jakarta on a Friday cannot wait on a foreign release cycle.
05 / Security & Data
Who holds the data, and how it is protected
Who owns the data in the system?
The hospital does. Ownership is stated in the agreement, and it includes the right to export your own data in a usable format. We consider a vendor holding data hostage to be an unacceptable way to retain a customer.
How is patient data protected?
Through role-based access so staff only reach what their job requires, encryption of data in transit, and an audit trail of who opened or changed a record. Handling of personal data follows Indonesian personal data protection law, and the controls are part of the implementation design from the start rather than hardened afterwards.
Is there an audit trail?
Yes. Access and changes to clinical and financial records are logged with user, time, and the previous value. This is what allows a disputed entry to be reconstructed instead of argued about.
What about backup and recovery?
Backup schedule, retention, and recovery targets are agreed during implementation and written into the support scope. Restores are tested, because a backup that has never been restored is an assumption rather than a safeguard.
Can the system run on our own servers?
Yes. On-premise, cloud, and hybrid deployments are all supported. Hospitals with policy or connectivity reasons to keep data inside the building can do so without giving up the ability to add modules later.
06 / Licensing, Cost & Support
How it is paid for and supported
What licensing schemes are available?
Three. A cooperation scheme (KSO) with a lighter entry cost and shared risk, a subscription, and a perpetual licence. Which one fits depends less on the size of the hospital than on how it prefers to treat the spend — as operating cost or as capital investment.
How much does it cost?
We do not publish a price list, because a number without scope is misleading in both directions. KSO is charged per patient at a rate designed to stay affordable for facilities that are still growing, and a full estimate is prepared after the assessment, when the modules, users, sites, and integrations are actually known.
What does support include?
A named support channel with agreed response times, help with day-to-day operational questions, corrective fixes, and assistance when regulatory reporting changes. Response commitments are written into the agreement rather than left to goodwill.
Are updates included?
Product updates and regulatory adjustments are covered under an active KSO or subscription, and under maintenance for perpetual licences. Changes specific to your hospital that fall outside the agreed scope are quoted separately, so shared improvements are never billed twice.
What happens if we want to stop?
Exit terms, including data export and a transition period, are part of the agreement from the beginning. A hospital should be able to see how it would leave before it decides to join.
07 / Partnership
Working with us commercially
Can we refer hospitals to ASTECH?
Yes. The affiliate programme is for consultants, professionals, and organisations with access to healthcare decision makers who prefer to introduce us and be compensated for a closed deal, without carrying delivery responsibility.
Can we resell or implement ASTECH products?
Yes. The distributor programme is for companies that want to sell and deliver in their own region, with levels that reflect certification and delivered capability rather than promised volume.
My question is not answered here.
Then it is worth a conversation rather than a longer page. Send it to us and a healthcare consultant will answer specifically, including the parts where the honest answer is that it depends.
Still weighing it up?
A demo answers in forty minutes what a FAQ cannot: whether the system fits the way your hospital actually works.