Quick summary
Medication orders in the Headed Web SDK generate structured medication lists from an ambient session and display them in the built-in Medication orders note section UI of the Headed Web SDK note page.
To enable this capability, add the LOINC code
52471-0 in the ambientOptions.sections array. After the provider submits the note, the SDK returns an orders JSON payload that your application can send to the EHR.Configuration requiredTo enable the Medication orders capability, you must provide the LOINC code
52471-0 in the ambientOptions.sections array. Learn more in Enable Medication orders.Prerequisites
Before enabling Medication orders, confirm the following:- Problems in the session - To link orders to problems in the note, enable Problem-Based Charting (PBC) by passing an Assessment & Plan, Assessment, or Plan LOINC section and marking one section with
isPBNSection: true. - Ambient session - Create and start an ambient session using Create session.
Payload structure
After the provider reviews the orders and submits the note, the Web SDK returns the generatedorders object in the standard note submission payload. The JSON response body includes the following parameters:
Structured orders returned on note submission. Includes medication details, dosage instructions, duration, linked problems, and more.
The Web SDK does not submit orders directly to the EHR. Your application is responsible for validating and submitting orders to the EHR, the same way you persist note
contents. Refer to Medication orders payload structure for the note submission payload and field definitions.Key features
Ambient-Based Order Generation
The Web SDK automatically identifies and generates orders from the clinician’s spoken conversation during an ambient clinical session.
Built-in Review UI
Providers review and complete generated orders within a dedicated, built-in section on the clinical note page.
Inline Validation for Missing Fields
When required ordering data is missing, the Web SDK displays inline dropdown menus within the interface. This allows the provider to complete all necessary details before submitting the final note.
Automatic Deduplication
The Web SDK automatically deduplicates generated orders against existing encounter orders from your Electronic Health Record (EHR) pre-charting data. The system removes exact matches based on medication name, form, and strength before displaying the list to the provider.
Problem-Based Linking
Providers can associate a medication order directly with a specific problem section within the clinical note when you enable Problem-Based Charting (PBC).
Simple Configuration via LOINC
You can activate this feature for any clinical session. To turn on Medication orders, pass the LOINC code
52471-0 in the ambientOptions.sections array.Structured JSON Payload
The Web SDK returns the orders in the same note submission payload as
noteId, encounterId, and contents so you can parse and save the data to your EHR easily.Use cases
Use Medication orders for the following Web SDK workflows:Ambient Medication Orders Generation
A provider wants to automatically generate medication orders purely from their clinical conversation during a standard ambient session. Pass the LOINC code
52471-0 in the ambientOptions.sections array when initializing the session.The Web SDK identifies the mentioned medications, generates the list, and displays them in the Medication orders section. When the provider selects submit, the Web SDK delivers structured JSON data in your note submission payload.Incomplete Orders Handling
A generated medication order is missing required clinical infrastructure data, such as a specific RxCUI code or a linked diagnosis. The Web SDK flags the omission and displays inline dropdown menus directly within the Medication orders interface.The provider uses the dropdowns to finish the order before submitting. Upon submission, your application receives the orders data: fully completed orders arrive in the
values array, while any remaining incomplete orders arrive in the partial_values array.Problem-Based Charting with Orders
A clinic uses Problem-Based Charting (PBC) and wants providers to explicitly link new medication orders to active patient problems during the ambient session. Pass a PBC configuration object containing
isPBNSection: true alongside the LOINC code 52471-0 in the same sections array.The Web SDK generates both problem sections and medication orders simultaneously. The provider can then visually associate a medication order with a specific problem section directly in the user interface before submitting.Session Re-Ambienting and Updates
A provider needs to restart or rerun the ambient recording feature within an encounter that already contains generated medication orders. The provider initiates a re-ambient session. The Web SDK automatically reviews the entire existing note context, including the previously generated orders, during its regeneration process.The SDK returns an updated payload. Your application must be configured to either replace or merge this new payload with the prior order state for that encounter within your EHR workflow.
Enable Medication orders
To enable the Medication orders capability in the Suki Web SDK, pass the LOINC code52471-0 in the ambientOptions.sections array. You can pass this parameter when you mount the Web SDK or when you call the AmbientOptions method. The section name displays as Medication in the user interface.
Test Medication orders
To test this feature in the Web SDK Playground, navigate to the Ambient tab and add{ "loinc": "52471-0" } to the Sections field.
Alternatively, you can configure this directly in your application code using the following code configurations:
Combine the LOINC code
52471-0 with your other note sections and a PBC section when you need Problems in the same session.Provider workflow
After the ambient session completes, the Web SDK displays a Medication section on the clinical note page. If you enable Problem-Based Charting (PBC), this section appears below the problem sections. This user interface is built directly into the headed Web SDK note page. During the review process, providers can perform the following actions:- Review medications from the visit: View medication orders that the Web SDK generates from the ambient session clinical conversation.
- Link orders to problems: Use the problem selector to associate a medication order with a specific problem section in the note.
- Complete missing fields inline: Use inline dropdown menus within the Medication orders section to fill in missing required data.
- Submit the note: Select the submit button to send the note. When the provider submits the note, the SDK returns the note contents and structured order data directly to your application.
Inline editing
Each generated medication order can include an RxNorm RxCUI value in themedication_code parameter. The presence of this code determines whether a provider can edit the order details inline:
| RxCUI status on the order | Provider can edit the order inline |
|---|---|
| Present | No |
| Missing or empty | Yes |
Non-edit workflow
The Web SDK uses a non-edit workflow by default. The interface does not include a full-screen editing panel. Providers must complete all missing fields using the inline controls within the Medication orders section.
Error handling
If order generation fails or orders are missing required fields, the Web SDK returns theORD_SDK_001 or ORD_SDK_003 error codes. Refer to Medication orders error codes for the error codes and descriptions.