Published at: 2025-10-30
Healthcare/Manufacturing - Medical Information Inquiry
Disclaimer
Data is updated annually from publicly available sources. The information provided is for reference only and does not guarantee accuracy or real-time validity.
Activation Method
Contact ShareCRM Support or your company’s account manager to activate the “Medical Information Query” service.
Administrator Configuration
After activation, CRM administrators must perform initial configurations based on the company’s actual business needs.
Step 1: Enable the Feature
Navigate to Admin Console > Business Rule Management and locate the new Medical Information Settings menu. Toggle the switch to enable the feature.
Select the applicable Record Type (e.g., “Hospital”) to ensure the service is only used for this data type (currently mutually exclusive with business registration queries). Non-hospital records (e.g., Distributors) will continue using the default business registration query.
Choose the data auto-fill method.
Click Save.
picture coming soon:
Step 2: Configure Field Mapping Rules
Navigate to Admin Console > Business Rule Settings > Object Mapping Rules.
Map fields from the Hospital dataset to corresponding Account fields. A default rule is provided, but administrators must adjust it based on actual field requirements.
For departments created automatically under hospitals, map Department fields to Account fields.
Important Notes:
- Ensure mandatory fields for department-type accounts are mapped to avoid validation errors during batch creation.
- Changes to Account fields may impact existing mappings.
picture coming soon:
picture coming soon:
picture coming soon:
Step 3: Configure Permissions
To disable batch department creation, navigate to Admin Console > Preset Object Management > Account > Buttons and deactivate Save and Create Departments.
To enable, assign this action to relevant Roles.
picture coming soon:
User Guide
Scenario 1: Create/Edit Hospitals via Medical Database
During creation/editing, enter a name keyword to match standard hospitals from the database. Selecting a match highlights the “Med” badge.
If auto-fill is configured, fields populate per mapping rules. Alternatively, manually fill fields via the Medical Details page.
picture coming soon:
picture coming soon:
Accounts filled via medical data display the “Med” badge. Click it to view hospital details.
To show hierarchical relationships (e.g., hospital-department), ensure the Account Hierarchy feature is enabled.
picture coming soon:
Click a department name to view its details and doctors. (Batch doctor creation is unsupported; only viewing is available.)
picture coming soon:
Users with Save and Create Departments permission can batch-create departments under the hospital.
Scenario 2: Batch-Create Departments While Creating a Hospital
Create a hospital account and click Save and Create Departments.
Select departments to batch-create. The system auto-links departments to hospitals via the Parent Account field.
Note:
- Hospitals/departments created via the medical database are flagged by the Medical Registration field (default: “Yes”). Add this field to layouts/lists if needed.
- Green labels indicate previously created departments.
picture coming soon:
picture coming soon:
Scenario 3: Batch-Create Departments for Existing Hospitals
From the Account Details page, click the “Med” badge and select Batch Create Departments in the department list.
picture coming soon:
Department Naming:
To concatenate department names with hospital names (e.g., “Hospital A + Cardiology”), use APL in the Account Creation post-action.
Field Descriptions
Hospital Fields Example:
picture coming soon:
Department and Doctor Fields:
picture coming soon:
Daily Query Limits
Each search, click on “Med” badge, or batch creation consumes query quotas:
- Hospitals: 2,000/day
- Departments: 5,000/day
- Doctors: 5,000/day
Bulk Data Cleansing/Initialization
Activate the Bulk Medical Data Add/Update Function Package (independent of the Medical Information Query app).
Call medical database APIs via functions to cleanse data.
Specify target objects (typically Accounts or custom objects).
Up to 5 packages can be purchased. Each hospital + department query counts as 1 (e.g., 1 hospital + 10 departments = 11 queries).
Data Cleansing (Update Hospital Data)
Request
Path: Fx.hospital.updateHospital()
Parameters
| Parameter | Type | Required | Description |
|——————–|———|———-|————————————–|
| objectApiName | String | Yes | Object API name |
| objectIds | List | Yes | Data ID list |
| mappings | Map | Yes | Hospital-to-Account field mappings |
| isUpdateNull | Boolean | Yes | Update null values? |
| medicalRegister | String | Yes | Medical registration field API name |
| levelMapping | Map | No | Hospital grade mappings |
Response
Data ID list (List).
Groovy Example
groovy // Hospital grade mappings (0-12) Map levelMappings = [ "0":"NX0f3im1Q", "1":"zbgZAGOF0", ..., "12":"sqamVsQ00" ] List dataIdList = ["642645d0bca58400013719a3"] Map mappings = ["name":"url"] APIResult result = Fx.hospital.updateHospital("AccountObj", dataIdList, mappings, true, "is_hospital_register", levelMappings) log.info(result)
Initialize Hospitals
Request
Path: Fx.hospital.initHospital()
Parameters
| Parameter | Type | Required | Description |
| ---- | ---- | ---- | ---- |
| hospitalObjectApiName | String | Yes | Hospital API name |
| recordType | String | Yes | Record Type |
| mappings | Map | Yes | Field mappings |
| medicalRegister | String | Yes | Medical registration field API name |
| levelMapping | Map | No | Hospital grade mappings |Response
Initialized record count (int).
Groovy Example
groovy Map mappings = [ "level":"field_Zi8Pw__c", "name":"name", ... ] Map levelMappings = ["0":"NX0f3im1Q", ..., "12":"4kzl2BbpE"] APIResult result = Fx.hospital.initHospital("AccountObj", "record_PRkkc__c", "4", "北京市", null, null, null, mappings, "is_hospital_register", levelMappings) log.info(result)
Initialize Departments
Request
Path: Fx.hospital.initDepartment()
Parameters
| Parameter | Type | Required | Description |
|----|----|----|----|
| hospitalObjectApiName | String | Yes | Hospital API name |
| departmentObjectApiName| String | Yes | Department API name |
| recordType | String | Yes | Record Type |
| objectId | String | Yes | Hospital data ID |
| mappings | Map | Yes | Field mappings |
| medicalRegister | String | Yes | Medical registration field API name |
| parentApiName | String | Yes | Parent lookup field API name |Groovy Example
groovy Map mappings = ["name":"name", "classification":"field_56YfM__c"] Map classificationMappings = ["0":"0", ..., "17":"17"] APIResult result = Fx.hospital.initDepartment("AccountObj", "AccountObj", "record_PRkkc__c", "6440f25a8d392e00011ffbfb", null, mappings, "is_hospital_register", classificationMappings, "parent_account_id") log.info(result)