Have something to say?

Tell PracticeHub how they could make the product more useful to you.

Table Talk Notifications - or API access to Total Visit numbers

Gone are the days where you can teach someone Chiropractic once at a ROF and they are patients for life. Table Talk is an opportunity every visit to re-engage, teach, and “re-sell” the Chiropractic model of health. In high-volume, principled, multi-doc environments you want a communication system that is reproducible and trackable. If we had a simple visit number based subtle notification system that shows in the clinical area or whichever screen is pulled up by the doctor at the adjusting table. They could be triggered as to what to talk about on that visit. This makes patient education for the doc systematized and lower effort as you don’t need to think about what to educate them on today, and you would know that they hadn’t heard that before in a previous visit. I’m completely willing to build this myself through a data pull and windows notification trigger, however would need API access to Total Visit numbers on a patients account.

Brock Jaeb about 18 hours ago

1

💡 Feature Request

How do we use this feedback area in a way that matters?

Totally get the focus is on building Flow which is awesome! Just wanted to know where we can put feature requests that are going to be seen? This posting area actually looks amazing with ability to upvote, see the status, etc, however there’s multiple dozens of posts that are over a year old and still in review with no comments whether a team member has put eyes on it. I’m a little confused as to what we can contribute here in terms of upvoting or giving you data so that the software can get better for the majority. As a high volume systems and procedure driven practice I can completely understand there are features and requests that 1) cost a lot of time/money and aren’t a huge ROI to build. 2) Other ones that are simple and high ROI 3) and ones that everyone wants regardless of how hard they are to build. However it seems the area has been cluttered, disorganized and only gets worse if we the clients don’t know what is happening with the posts or feedback we provide. Speaking for myself only, I would almost think it would be better for me if I had a flat out no answer on something I suggest rather than have it sit seemingly in limbo with hopes the product gets better for 1+ years. I’m just a newcomer here loving the current product and wanting it to be even better! All the best

Brock Jaeb about 18 hours ago

💡 Feature Request

API Feature Request — Patient Communication & Recall Preference Fields

Hi PracticeHub Support, I hope you're well. I'm writing to submit a feature request regarding the PracticeHub API. We have built a custom recall management system that integrates with PracticeHub via your API. The system sends recall emails to patients and includes an unsubscribe link, allowing patients to opt out of future reminders. When a patient opts out, we would like to automatically update their PracticeHub record to reflect this. However, we have found that the following fields are not supported as updatable attributes via the POST /patients/{patientId} endpoint: recall_status blocked communication_preferences (marketing.email, marketing.sms etc.) All three return an "unsupported attribute" error when included in a patient update payload, despite being visible in the PatientRead schema and accessible via GET requests. We would like to formally request that one or more of these fields be made writable via the API, specifically to support the following use cases: Setting a patient as "Do Not Contact" (blocked) when they unsubscribe from recall emails Setting recall_status to 0 when a patient opts out Updating communication_preferences.marketing.email when a patient unsubscribes This would allow practices like ours to build fully automated, GDPR-compliant opt-out flows without requiring manual intervention in the PracticeHub UI after each unsubscribe. Please let me know if you need any further information or if this can be logged as a feature request. Many thanks, Jo Kennedy The Sparkle Fairy Limited

Joanne Kennedy 6 days ago

💡 Feature Request

Notifications for Overview updates

It would be extremely helpful to have the option to enable automatic email notifications whenever a patient’s Overview section is updated (specifically when a new note is added). For example, when a staff member adds a follow-up or phone call note to the patient overview, a notification could be sent to a nominated email address with: the patient name a snapshot/preview of the note and a link to view the full update in PracticeHub. This would help improve internal communication and reduce the need for verbal updates between team members, particularly for follow-up calls, patient check-ins, and general correspondence. It would also allow practitioners or managers to quickly review important patient interactions at a glance without needing to manually check each profile

lauradoherty13 13 days ago

💡 Feature Request