Cardiology clinic software that computes Mean Arterial Pressure on every visit

When your nurse records systolic and diastolic, the platform derives MAP automatically using diastolic + (systolic − diastolic) ÷ 3, rounded to one decimal, and shows it as its own column on the vitals table with the formula spelled out in the header hint. You never key MAP by hand or reach for a calculator. It appears live as the BP is typed in the vitals form and again on the saved record, so perfusion pressure is there for every cardiology review. This auto-derived MAP is the one thing here a generic EMR does not do.

Every BP and pulse is judged against reference ranges that shift by the patient's age: adult systolic 90–140 and diastolic 60–90, with a distinct child (<12y) BP band and distinct infant (<2y) and child heart-rate bands. A reading below range is coloured with the info style (low), above range with the danger style (high), so a hypertensive 160/100 or a bradycardic 48 bpm is visible at a glance instead of buried in a number grid. The colouring is driven by getVitalStatus, not a human eyeballing the slip. This is the same flagging every clinic gets, useful for cardiology, but not built only for it.

In the block-template builder (on by default) you build one artifact (call it the Cardiac Risk-Factor & BP Log) as a block-database table: one row per visit with columns you define from 23 field types, a date, number columns for systolic, diastolic and pulse, and selects for smoking, diabetes, dyslipidaemia and family history. Conditional formatting paints a cell when its rule fires, for example a 'when' formula like prop("Systolic") > 140 styled danger, so a stage-2 reading turns red on the sheet. Each visit is a new row, so the whole BP history reads as one growing table on the record, though it stays a dated table, not a plotted trend line.

The same builder ships a ~30-function formula engine, so on your BP log you compute pulse pressure as a column (systolic minus diastolic), average a column of systolic readings with avg(), or surface a single headline number in a KPI block. Numbers format the Indian way via formatNumber (en-IN grouping, e.g. 1,20,000) and money via formatCurrency (₹, en-IN) when the sheet doubles as a procedure estimate. It is your math, run on the platform, not a side Excel file the front desk forgets to update.

Prescription search ranks medicines by what your clinic prescribes most, learned per clinic from the last 90 days. The migration that built this names cardiology directly, noting a cardiologist almost never writes Paracetamol so a global ranking would mislead the autocomplete. So amlodipine, telmisartan, atorvastatin and the antiplatelets you use float to the top, custom formulations you stock can be added inline, and every drug is allergy cross-checked at prescribing time. A clinic with no history falls back to alphabetical. Generic prescribing is covered on our prescription page; here the point is the ranking learns your cardiac mix.

Avinya Plus ships no cardiology clinical module: there is no ECG capture, no echo report template, no Framingham or ASCVD risk-score engine, and no BP trend chart or sparkline; blood pressure is stored as dated structured numbers, not plotted on a line graph. We will not pretend otherwise. What is real is that MAP is auto-derived on every visit and you build your own risk-factor and BP log in the configurable builder, run on the same platform (GST billing, scheduling, role-based access, per-clinic (RLS) isolation) every clinic uses. You interpret the cardiac risk; the platform keeps the numbers dated, flagged, and together.