Opening catalogue record…
Loading its scope, linked MicroERPs and implementation progress.
ERP ATLASAPPNEURALOperationsP2Reference
Patient Records & Follow-up
Full nameClinic Patient Records and Follow-up Micro ERP
Profile history, visits, attached evidence and approved plans need a consistent record.
Application configurations3
Extension mappings6
LifecycleReference
About this erp
Purpose and scope
Profile history, visits, attached evidence and approved plans need a consistent record.
Connected workflows
- Patient profiles
- visit notes
- approved files
- follow-up actions
- Source
- ERP_Full_Hierarchy_Catalogue.html
- Family
- Client and case records
- Family ID
- records
- Configuration scope
- Industry operations
- Standalone scope
- Own clients, authorized providers, record types, case ids. Run patient profiles, visit notes, approved files, follow-up actions. Maintain record history and role permissions.
- Core records
- Clients, authorized providers, record types, case IDs
- ERP connections
- Appointments, services, documents, billing
- Primary workflow
- Patient profiles → visit notes → approved files → follow-up actions
- Readiness
- Source-defined reference configuration; runtime unverified.
AI brief
What it is, when to use it, how to start
Written by Claude from this ERP's record. Check the details before you rely on them.
Connected catalog
Explore the composition
Follow each relationship to its full catalog record.
3 linked records
Application
Patient Records & Follow-up: Practitioner Records
Full nameClinic Practitioner Records App
Maintain structured case history and approved plans.
ApplicationPatient Records & Follow-up: Records Assistant
Full nameClinic Records Assistant App
Register profiles, attach supporting files and request missing details.
ApplicationPatient Records & Follow-up: Client Records
Full nameClinic Client Records App
View shared records, approved plans and required follow-up actions.