Hey everyone! Quick question about task management in Medplum - is it possible to create tasks and assign them to a particular AccessPolicy? The use case here is creating tasks that aren't assigned to a specific person, but rather to a role like "Care Coordinator" so that any care coordinator could pick up and work on those tasks. Basically looking for role-based task assignment rather than individual assignment.

How to handle when a doctor needs to correct a mistake in the original questionnaire submission? How to efficiently find and update the related Observation when a QuestionnaireResponse gets modified Whether to store the Observation ID back in the QuestionnaireResponse for easier lookups Best practices for handling corrections in clinical data Whether to process the form data client-side vs using Bots

A developer wants to set up webhook notifications when a specific resource's value changes in Medplum. They already have the webhook endpoint ready on their app side and are looking for the best practice approach to trigger these notifications from Medplum when a doctor changes an Appointment status.

Is it possible for a user to be both a Patient and a Practitioner for example in a given project? Or is this not supported.

Hey Medplum community! 👋 A developer recently needed help restoring a large batch of resources that were accidentally soft-deleted. They had the exact resource IDs and needed to restore: - 1204 Task resources - 111 Encounter resources - 111 Appointment resources

Hey Medplum community! 👋 A developer was working with compartments in Medplum and ran into some issues after the removal of user-defined compartments in v4.0.4. They previously used Organization compartments on Task resources as filters in GraphQL queries. Since Tasks don't have inclusion criteria for the patient compartment, they were looking for the recommended approach to achieve similar functionality. They also mentioned trying _tag as a filter previously, but experienced performance issues.

Hey Medplum community! I'm working on some changes to our insurance records and wanted to get some input on a few scenarios: 1. Flagging Coverage found via insurance lookup - When a patient hasn't uploaded pharmacy insurance or their uploaded insurance isn't accepted at our pharmacies, we use our pharmacy system to automatically look for alternative accepted insurance. What's the best way to flag coverages found through this process? 2. Using CoverageEligibilityRequest/Response - Is it appropriate to create these resources for the insurance lookup process described above? The docs make it sound like these are for tracking requests to insurers specifically. 3. "Archiving" Unaccepted Insurance - If we find a patient's insurance isn't accepted at our pharmacies, we want to "archive" it so our systems don't use it. Would setting Coverage.status to

cancelled

be appropriate, or should we use another approach?

Hey Medplum community! I have an open-ended question about referrals, particularly around tracking "prerequisites" and state for long-lived referrals. Background: When we're referring patients we need to share several data points with them by syncing to their EHR: Basic demographics Vitals Intake forms Lab result PDFs Once we've shared everything, patients can: Pay for the service Book an appointment The Challenge: We need to track what we've already shared and what's still pending (e.g., "Already shared X labs, but still need Y lab" or "All labs shared but intake pending"). We also want to record their invoice number and appointment details for future reference. What I've considered so far: Creating a ServiceRequest for the referral Adding lab results as .supportingInfo references to DiagnosticReport But I'm unclear on: How to annotate which prerequisite each item is meeting How to record external system IDs for uploaded data How to reference intake forms not yet in Medplum How to handle invoice numbers Any suggestions?

We're working on automatically revoking Medplum access when a user gets disabled in our SSO provider. We've tried deleting their ProjectMembership which seems to work - the Project disappears from their login screen and they can't log in anymore. However, we noticed this warning in the docs (https://www.medplum.com/docs/auth/user-management-guide#removing-memberships): "Do not edit or change the ProjectMembership resources directly..." Are we going down the right path by just deleting the ProjectMembership resource, or is there a better way to remove access programmatically?

Hey devs! 👋 A customer was asking about implementing different user roles in their EMR system. They have various roles like Admin, Physician, Registered Nurse, Care Coordinator, and Customer Support. Their main use cases were: Feature permissions (e.g., only physicians can do certain tasks) Task assignment logic (e.g., routing specific messages to nurses) Group filters/CareTeams (e.g., showing tasks assigned to specific roles)

A developer is asking if it's possible to enforce uniqueness on a resource on the Medplum side. They want to ensure only one record is ever created on the Medplum side while still allowing updates to happen.

Just wanted to share a solution for handling supply items in FHIR when integrating with an e-prescribing system. The Problem I needed to add non-medication supply items (like medical supplies) to our system and sync them with an e-prescribing platform. The supplies data looked something like:

SupplyId: 2
SupplyName: Poise Thin-shape Pad
IsRx: FALSE
IsObsolete: FALSE
NDC_UPC_HRI: 36000043127
NDC_UPC_HRI_TypeId: 2