Data Mapping
- Sanket Shrestha
Analytics
Meshed and PRISMS Data Mapping
Meshed PRISMS API integration allows the users to map data between the two systems so that there is data consistency and integrity. The API gets data from PRISMS in real time and the user can link data individually or in bulk. This data mapping is required to create CoEs using API.
There are 3 types of data mappings available in this integration:
Agent Mapping
Venue Mapping
OSHC Provider Mapping
To navigate to the PRISMS Data Mapping page, go to the PRISMS icon on the homepage >> PRISMS Data Mapping
Key Features of the PRISMS Data Mapping Page:
The page provides real-time data for Agents and Venues based on their corresponding PRISMS records.
The list of OSHC Providers displayed on the mapping page is derived from the validated list of OSHC Providers accepted by PRISMS. This is a standardized list and is not specific to any college or education provider.
The grid features dropdown menus that enable users to select a matching record for each data entry in the Meshed system.
Multiple Meshed records for Agents, Venues, or OSHC Providers can be mapped to a single PRISMS record.
In cases where a Meshed Agent, Venue, or OSHC Provider record automatically matches a PRISMS record, the system highlights the match with a default selection.
Upon successful mapping, the PRISMS Agent ID, PRISMS Venue ID, and PRISMS OSHC Provider ID are recorded in the Meshed system.
It is essential that the user has a valid token or active authentication with PRISMS before initiating the data mapping process. If the user’s authentication has expired and the token has not been renewed, the data mapping page will display the error message.
Page Icons and Filters
Icons
The PRISMS Data Mapping page consists of three pages i.e., Agent, Venue, and OSHC Provider to map the data.
Following are the icons and filters available on the 3 pages:
Filters
On all 3 data mapping pages, the filters Matched, Not Matched and All are available. These filters are used to differentiate records that have a matching PRISMS record.
Matched - The Matched filter brings any record where the data in the Meshed system matches the data from PRISMS. If the data matches automatically, the system shows the matched data in green colour with a default matching value. The user can keep the default selection or change the value from the dropdown and click the save button to save the data mapping. Once any record is mapped by the user, it starts to appear under Matched with the relevant selection and ID.
Not Matched – This filter brings records where there is no match found or no data mapping is done between Meshed and PRISMS records.
All – This filter brings a combination of Matched and Not Matched data in the grid.
1) Agent Mapping
Standard 4 of the National Code of Practice for Providers of Education and Training to Overseas Students 2018 (National Code 2018) mandates that all registered providers keep a record of their education agents' information in PRISMS for each agent they engage with and have a formal agreement in place.
This implies that agent data recorded in the Meshed system must match the PRISMS agent data for the successful creation of a CoE.
To map Meshed Agent Data with PRISMS, go to PRISMS Data Mapping Page and select Mapping Type as Agent. The API will display the Provider Agent List from PRISMS in the Meshed system for mapping data.
The Agent Mapping page has the following options that can be used to filter data in the grid:
Agent Name – This filter can be used to search for a specific agent name in the Meshed system.
Email – Search for any agent using their Email.
Status – Agent data can be further filtered based on the status of agents in the system.
Note – Principal Agent or Agent ID (1) does not appear on the Agent Data Mapping page.
Auto Data Matching:
For the system to match the Meshed Agent records with PRISMS agent records automatically, the following needs to match:
Agent Name – The Agent Name in the Meshed system must match the Provider Entered Business Name in PRISMS.
Email- The Email for the agent in the Meshed system must match the Agent Email Address field in PRISMS for the selected agent.
If the values above match, the system shows the matching record as a default selection which the user can confirm and save.
Not Matched Data
If the data is not matching with PRISMS automatically, the Matched column will display No and the user will need to select data from the list to map.
1.1) Save/Update PRISMS Agent Mapping
To Save/Update PRISMS agent mapping, click on the save button with the relevant selection from the dropdown. Once the user clicks the action button, the selected record is saved in the system with the relevant PRISMS Agent ID.
For auto-matched records:
For not matched records:
Once the data is mapped, it will start to appear under the Matched filter. The user can also do a bulk selection and map multiple agent records at once.
Similarly, the mapping can be updated to a different PRISMS agent record using the same action buttons.
1.2) Delete PRISMS Agent Mapping
To delete PRISMS agent mapping, the user can click on the delete button and this will remove the PRISMS Agent ID stored for that agent in the Meshed system. The record will then appear as a new record which can be mapped again.
1.3) Agent List
The agent list under Marketing tab in the system can also indicate if the agent record is mapped with PRISMS or not.
Any agent record that is mapped to PRISMS agent and has a PRISMS agent ID will have 
If the agent is not mapped with PRISMS yet,
icon will appear next to that record indicating that the mapping is not yet done.
Once the user clicks on this icon, it will open a new window redirected to the PRISMS Data Mapping Page where the agent can be mapped.
2) Venue Mapping
A provider’s CRICOS registered delivery locations appear in PRISMS and these are the delivery locations that are used to manage CoEs.
This implies that venue data recorded in the Meshed system must match the PRISMS venue data for the successful creation of a CoE.
To map Meshed Venue Data with PRISMS, go to the PRISMS Data Mapping Page and select Mapping Type as Venue. The API will display the Provider Locations from PRISMS in the Meshed system for mapping data.
The Venue Mapping page has the following options that can be used to filter data in the grid:
Campus – If there are more than 1 campus locations for a provider, the campus dropdown can be used to filter data for a particular campus.
Venue Code – This filter can be used to search for a Venue Code in the Meshed system.
Venue Description – Search for any venues using the venue description.
Status – Venue data can be further filtered based on the status of venues (active/inactive) in the system.
Auto Data Matching:
For the system to match the Meshed Venue records with PRISMS location records automatically, the following needs to match:
Venue Address- The combination of Address, Suburb, State, Country, and Postcode in the Meshed system must match the location name in PRISMS.
If the values above match, the system shows the matching record as a default selection which the user can confirm and save.
Not Matched Data
If the data is not matching with PRISMS automatically, the Matched column will display No and the user will need to select data from the list to map.
2.1) Save/Update PRISMS Venue Mapping
To Save/Update PRISMS venue mapping, click on the save button with the relevant selection from the dropdown. Once the user clicks the action button, the selected record is saved in the system with the relevant PRISMS Venue ID.
Once the data is mapped, it will start to appear under the Matched filter.
The user can also do a bulk selection and map multiple agent records at once.
Similarly, the mapping can be updated to a different PRISMS agent record using the same action buttons.
2.2) Delete PRISMS Venue Mapping
To delete PRISMS venue mapping, the user can click on the delete button and this will remove the PRISMS Venue ID stored for that venue in the Meshed system. The record will then appear as a new record which can be mapped again.
2.3) Venue List
The venue list under the manage venue page in the system can also indicate if the venue record is mapped with PRISMS or not.
Any venue record that is mapped to PRISMS venue and has a PRISMS venue ID will have 
If the venue is not mapped with PRISMS yet,
icon will appear next to that record indicating that the mapping is not yet done.
Once the user clicks on this icon, it will open a new window redirected to the PRISMS Data Mapping Page where the venue can be mapped.
3) OSHC Provider Mapping
PRISMS has a standard list of Overseas Health Cover (OSHC) Providers which is required to be mapped with the Meshed OSHC Provider data. The list of OSHC Providers as provided by PRISMS:
Australian Health Management OSHC
BUPA Australia
Medibank Private
OSHC by Allianz Care
NIB OSHC
CBHS International Health
The OSHC Provider Mapping page has the following options that can be used to filter data in the grid:
Provider Name – This filter can be used to filter the list of OSHC Provider based on the Provider Name in the Meshed system.
Auto Data Matching:
For the system to match the Meshed Venue records with PRISMS location records automatically, the following needs to match:
OSHC Provider Name – The OSHC Provider name in the Meshed system must match the OSHC Provider name as per the PRISMS list for the system to auto-match the data.
If the value above matches, the system shows the matching record as a default selection which the user can confirm and save.
Not Matched Data
If the data is not matching with PRISMS automatically, the Matched column will display No and the user will need to select data from the list to map.
3.1) Save/Update PRISMS OSHC Provider Mapping
To Save/Update PRISMS OSHC Provider mapping, click on the save button with the relevant selection from the dropdown. Once the user clicks the action button, the selected record is saved in the system with the relevant PRISMS OSHC Provider.
Once the data is mapped, it will start to appear under the Matched filter.
The user can also do a bulk selection and map multiple OSHC provider records at once.
Similarly, the mapping can be updated to a different PRISMS OSHC record using the same action buttons.
3.2) Delete PRISMS OSHC Provider Mapping
To delete PRISMS OSHC Provider mapping, the user can click on the delete button and this will remove the PRISMS OSHC record stored for that venue in the Meshed system. The record will then appear as a new record which can be mapped again.