You do not need a second system to separate local patients from international patients referred by an agency. The real requirement is to keep their different operational details visible within one data structure. With the right separation layers in Zoho, teams can work in one environment while keeping source, pricing, currency, reporting, and access requirements distinct.
The model is straightforward: a picklist defines the patient stream, layouts accommodate different information needs, price books carry commercial terms, and record currency preserves monetary context. Visibility belongs in the ownership and sharing model. This prevents one field from being overloaded with source, pricing, exchange rate, and access meanings that should remain independently controlled.
What breaks when both patient streams share one list
A local patient and an international patient do not follow identical operational paths. The latter may bring additional context about flights, accommodation, and an intermediary agreement. If both groups complete the same ambiguous form, those details stop being structured data. They migrate into notes, personal reminders, and scattered explanations exchanged within the team.
Two patients appear beside each other in the same list. One arrives from within the city, while the other's file awaits a flight date and accommodation plan. When the team uses one form for both, the flight detail is entered in a note and stays there. The problem is missing structure, not shared visibility.
The loss extends beyond daily operations. If patient source is not classified clearly, commercial conditions, team responsibility, and outcome analysis become entangled. When the distinguishing information sits in free text, consistent wording soon disappears. Managers must interpret individual explanations instead of working with data that can be filtered, compared, and reused across routine reporting.
Choose the right layer for separation
The first decision concerns three architectural options: a picklist within one layout, separate layouts in the same module, or a separate module. A picklist may be enough when source is the only distinction. Separate layouts become more meaningful when the fields collected and the values presented differ between the two operational streams.
Zoho can give layouts in one module different fields, mandatory settings, and picklist values. Creating an additional layout requires Enterprise or a higher edition, together with permission to customize the CRM. If either condition is missing, the multiple-layout design is unavailable, so the intended separation must use a structure supported by the current environment.
Creating a layout also produces the system Layout field. It can support custom views, assignment rules, approval processes, automated follow-up rules, and workflow criteria. Reports and dashboards can also be organized by layout. A separate module would expand the data boundary, while this approach deliberately keeps both patient streams inside the existing module.
How each intake channel selects a layout
Users can select a layout when creating a record manually or during an import. A web form uses its configured default layout. For an API-created record, omitting the Layout ID sends the record to the Standard layout. Defining the source field is therefore insufficient unless layout selection is also configured clearly for every intake channel.
Records created through Visitor Tracking and Zoho Survey also enter the Standard layout. If this behavior is overlooked, fields prepared for the international stream may not appear when the record first opens. Selecting another layout later does not replace a disciplined intake design. Channel defaults alone do not provide a dependable separation between the two patient streams.
An assignment rule does not run for a manually created record. It applies only to records created through import, web form, or API, and each rule entry accepts no more than 25 criteria. The user profile must also include permission to manage assignment rules and their thresholds. Channel and layout decisions should respect these limits together.
Keep pricing differences in price books
Instead of embedding local and international pricing inside the source field, maintain separate lists in the Price Books module. The same product can have different list prices for different customer types or agreement terms. Products in a single deal can come from only one price book, so the appropriate list must be selected before adding them.
If an amount must use another currency, Zoho can enable multiple currencies. Activation adds the system-defined Currency and Exchange Rate fields to records, and the feature cannot later be disabled. Report, analysis, and forecast totals use the rate stored on the record rather than today's rate. That choice directly shapes the interpretation of historical figures.
The Exchange Rate field points in a less intuitive direction. Its value expresses how many units of the record currency equal one unit of the home currency. Converting an amount back to the home currency therefore requires division by the rate. Price book selection, record currency, and rate direction should remain separate documented controls.
Use a picklist to separate reporting
Category columns and report breakdowns work only with picklist and numeric field types. Storing patient source as free text makes reliable separation of direct and agency records difficult. Defining it as a picklist from the beginning standardizes the available values and lets reports use that field directly as a consistent category for comparison.
Dashboard filters accept only User, Date, Date Time, and picklist fields. They also operate only within the Analytics tab. A picklist for the patient stream can therefore support both report categories and dashboard filtering. Free-form explanations cannot perform the same role in either structure, even when their wording appears consistent to the people entering them.
At month end, the revenue report shows one combined total. The agency's share and the amount remaining from the clinic's direct patients have dissolved into the same row, and nobody can separate the table manually. Standardized source values let the report split the streams, while monetary records retain their own pricing and currency context.
Visibility follows ownership
Restricting international patient files to a specific team is not a layout decision. Role-based access follows the record owner. The source field and the access model should therefore remain distinct. A picklist states which stream the record belongs to, while ownership determines its visibility through the role hierarchy that applies to the responsible users.
Access for someone who is neither above nor below the owner can be provided through a user field on the record, record-level sharing, a data sharing rule, or territory management. The appropriate method depends on whether access concerns one record, defined conditions, or territorial responsibility. Layout controls operations, while ownership and sharing establish authorization boundaries.
Territory management is available only in Enterprise and Ultimate. Access design must therefore be evaluated against the edition in use. A lower edition should not be planned as though territory management were present. The other documented ownership and sharing paths can be considered separately according to the scope and form of access the clinic needs.
Building the same separation on a lower edition
In Standard, use one patient-source picklist within a single layout instead of multiple layouts. Report categories and Analytics dashboard filters can use that field to separate direct and agency records. Clear field names and team working discipline then govern which additional details are completed for each stream, without pretending that a second layout exists.
The thresholds belong in one view: multiple layouts require Enterprise or higher; price books are available in Professional, Enterprise, and Ultimate; territory management is limited to Enterprise and Ultimate. Sources conflict on the edition required for multiple currencies, so no threshold should be asserted. Verify that feature directly in the customer's own Setup screen.
The lower-edition foundation is patient-source separation through a picklist, report categories and Analytics filters, separate price books where the paid edition supports them, and ownership-based access. When the team selects the source consistently, chooses the correct price book for each deal, and evaluates visibility independently, Zoho can keep both streams readable without requiring a second system.
