RNpad

Last reviewed: July 2026

Overview

Integuru's RNpad integration provides production-ready HTTP API access to RNpad, the nursing documentation platform used by skilled nursing and home care agencies at my.rnpad.com, covering 8 actions across patient management, medication records, allergy tracking, clinical section writing, and hospitalization logging. All 8 actions carry full richer documentation. Integuru connects via direct HTTP requests rather than browser automation, so calls complete in under 3 seconds with a 99.9%+ success rate.

Documentation-first nursing platform. RNpad is built around structured clinical sections: each write operation targets a named section of the patient record rather than a generic field. Integuru's write_patient_section action reflects this model directly, letting you pass a section name and a section-specific data object so your integration maps cleanly to how RNpad organises nursing documentation.

The integration covers the full patient documentation lifecycle: roster retrieval and search via get_patients and find_patient, patient creation via create_patient, demographic updates via update_patient_basic_info, clinical documentation via write_patient_section, allergy management via create_allergy, medication records via create_medication, and hospitalization logging via create_patient_hospitalization. See the Wellsky integration for another home health clinical platform, or browse the full integrations catalogue.

---

Use Cases

Integuru's RNpad integration covers the nursing documentation and patient management workflows that skilled nursing and home care tech teams need to automate.

• Patient roster retrieval: Call get_patients with optional search (minimum 2 characters), statuses array, page/per_page pagination, sort (prefix with - for descending), and date-range filters (created_date_from, created_date_to) to retrieve a filtered, paginated patient list. Filter by responsible_managers array to scope results to specific care managers.
• Patient lookup: Call find_patient with any combination of personal_information, address, and contracts objects (all fields optional) to locate a patient record by demographic or contract details.
• Patient creation: Call create_patient with the required personal_information object (including first_name, last_name, contact details, and medicaid_id/medicare_id), address object, and at least one contracts entry.
• Demographic updates: Call update_patient_basic_info with patient_id and a changes object containing only the fields to update (sex, zip, city, email, state, languages, last_name, first_name). Fields omitted from changes are preserved as-is.
• Clinical section writing: Call write_patient_section with patient_id, section (the target documentation area), and a data object matching that section's schema. Pass record_id to update an existing record in sections like emergency_contacts or medications; omit it to create a new entry.
• Allergy recording: Call create_allergy with patient_id and either allergy_id (catalog lookup, skips name search) or allergy_name (e.g., 'penicillin'). When the allergy is 'other' (catalog ID 7123), description is required.
• Medication recording: Call create_medication with patient_id, as_needed (boolean), dosage_with_unit, medication_route, and medication_dosage_form. For PRN medications (as_needed: true), provide reason; for scheduled medications (as_needed: false), provide schedule. Use icd_10_code or purpose (not both) for diagnosis context.
• Hospitalization logging: Call create_patient_hospitalization with patient_id, date (YYYY-MM-DD), and reason to record a hospitalization event. The reason field accepts predefined values or custom free text.

---

Setup Notes

Integuru's RNpad integration authenticates against https://my.rnpad.com/login. Configure credentials once during Integuru setup; Integuru manages authentication and session handling automatically.

All 8 actions carry richer documentation available via the Integuru dashboard after setup. Actions that accept object parameters (create_patient, find_patient, write_patient_section) have section-specific sub-field schemas documented there. For create_medication, medication_route_comment is required when medication_route is 'Other'. For create_allergy, description is required when creating an 'other' allergy (catalog ID 7123). Full parameter documentation is available for actions marked with the docs badge in the table above.