Pulse Lite Conversion FAQs

Modified on Mon, 23 Oct 2023 at 03:53 PM

The Pulse Lite Conversion option is estimated for release in November 2023. Availability and mechanics of this tool are subject to change, pending official development completion.

What is the Pulse Lite Conversion?

The Pulse Lite Conversion is a versatile and user-friendly data conversion option designed to transform data from various source PIMS into Pulse as long as the data owner can provide it according to our specified requirements. This tool serves as a bridge between different data formats, making the transition to Pulse possible no matter where your data lives today.

Key Features

Data Source Agnostic: Pulse Lite Conversion works with data from any source, making it highly adaptable to diverse data ecosystems and proprietary PIMS.

Flexible Data Input: Users can supply data in any format, as long as it adheres to the predefined formatting guidelines. This allows for seamless conversion from a wide range of source systems.

Error Handling: Pulse Lite Conversion includes error detection and handling mechanisms to identify issues during the conversion process, ensuring data quality and consistency.

Data Validation: Before and after conversion, the tool offers data validation options to confirm that the transformed data meets the specified requirements.

Audit Trail: Pulse Lite Conversion maintains a comprehensive audit trail, logging all conversion activities behind the scenes of Pulse for traceability and accountability.

Pulse Lite Conversion is a valuable solution for organizations looking to make the switch to Pulse from previously "unsupported" sources, providing flexibility and control over the data transformation and maintaining data integrity.

Who is eligible for Pulse Lite Conversion?

Any customer currently using an unsupported source PIMS or other method of data recording is eligible for the Pulse Lite Conversion, as long as they can provide data in the predefined format.

I'm interested! How can I begin preparing for my Pulse Lite Conversion?

Thank you for your interest in the Pulse Lite Conversion offering! This document provides preliminary guidelines for using the tool. Please note that the information presented here is subject to change upon the official release of the tool. We appreciate your understanding and flexibility during this development phase.

Important Points to Emphasize

Draft Status: The guidelines and technical requirements outlined in this document are in draft form. They are intended to give you an early understanding of the tool's capabilities and requirements but may undergo revisions and refinements before the official release.

No Formatting Support: Pulse Lite Conversion is designed for users who can provide data in the exact formatting we require as specified in this document. We regret to inform you that, during the draft phase and upon official release, we do not offer support or assistance for formatting your data to meet these guidelines.

Data Validation: If the data you provide is flagged as improperly formatted during the conversion process, it will be returned to you for correction. To ensure a smooth data conversion, we encourage you to thoroughly review and comply with the formatting requirements as per this draft documentation.

Suggestions for Users

To ensure a successful data conversion process and avoid any potential issues, we recommend the following:

Thoroughly review this draft documentation to understand the formatting requirements.
Verify that your data conforms to the specified guidelines before initiating the conversion process.
- Can you find this data in the reports offered by your source PIMS?
- Do you understand the formatting guidelines and feel comfortable manipulating your data contents and formatting in a spreadsheet?
Double-check your data for accuracy and formatting compliance to prevent unnecessary delays.

Feedback and Collaboration

We welcome your feedback and collaboration in this early phase of development. Your input can help us improve the tool and the documentation for the official release. If you have suggestions or encounter any challenges while using Pulse Lite Conversion, please feel free to reach out to us.

Draft Documentation - Pulse Lite Conversion

Data Schema

The standard Pulse Lite Conversion data schema includes the data entities and fields defined below. This is the data schema you must provide to successfully convert to Pulse.
The files must be returned precisely as defined or the data will be returned for correction.
- File and column names cannot be changed.
- Columns that do not have corresponding PIMS data may be deleted or left blank.
- PIMS data may be combined into one column but will appear in Pulse as it was received.
  - For example, Spouse Full Names may be submitted in field Client.SpouseLastName, but will appear only in the Spouse Last Name field in Pulse.
The file format to be returned is CSV (Comma-Separated Value), with double quotes at the start and end of all fields.
Sample CSV files will be included in the entity documentation with the required double quotes. Open the files with a text editor, such as Notepad, to preserve formatting.

Formatting with double quotes is the last step in the process because Excel does not readily handle double quote formatting.

Entity documentation includes the expected Excel field types in double quotes.
Field type format assumptions are noted in the entity documentation and must be corrected as needed for the specified data set.

Data Details and Notes

The file format to be returned is CSV (comma-separated value) file with double quotes at the start and end of each field. This will require custom formatting based on the Excel assumed field type.

Data Field Type	Recommended Excel Field Format
Character	\"@\"
Integer	\”0\”;\"-0\"
Currency	\"0.00\";\"-0.00\"
Date	\"m/d/yyyy\"

Sample CSV files assume ClientAccountIDs are integers with column formatting set to \"0"\. If the ClientAccountIDs are alphanumeric (including GUIDs), the column formatting will need to be changed to \"@\"

Embedded double quotes must be proceeded by the "quoting character," typically a backslash.
Cells that do not contain data are denoted by two double quotes.
Required fields are noted in the entity documentation.
Conditional field dependencies are noted in the entity documentation.

Once the data is populated, check each column by setting a filter and reviewing each entry for the required double quotes at the start and end of the field. You must select specific cells and use custom formatting on those cells, as described above, to correct them. An example is the Clients.Address2 field that may contain "Apt 202" or just "202." The default formatting will work for the former but not the latter, as Excel will treat it as an integer.

Example - Client Entity

This entity represents all Clients configured for the practice which can include referral hospitals and referral doctors. The attached contains the required format for the Client.CSV with a sample record.

The Type defines how the sample file handles the CSV data type to produce the double quote delimiters for each field. Make sure to change the custom field format if any if the fields noted as “integer” contain alphanumeric data.

Fields:

Field Name	Type	Required	Description
AccountId	“string”	Y	Unique record ID
FileNumber	“integer”		Identifier for physical file. Typically an integer.
ClientTypeCode	“string”		Client type assigned in the PIMS typically for alert and/or discount purposes. Examples are ‘A’ for Active regular clients, ‘S’ for Senior citizen discount.
Salutation	“string”		Dr, Mrs, Ms, Miss, etc
LastName	“string”	Y	Cient last name
FirstName	“string”		Client first name
MiddleName	“string”		Client middle name or initial
Address1	“string”		Address line 1
Address2	“string”		Address line 2
City	“string”		City
State	“string”		State abbreviation
Zip	“string”		Zip code
Country	“string”
County	“string”
Language	“string”		Language or locale
Email	“string”		Primary email address
Phone1AsIs	“string”		1^st phone number as recorded
PhoneType1	“string”		1^st phone number type – Cell, Home, Work etc
Phone2AsIs	“string”		2^nd phone number as recorded
PhoneType2	“string”		2^nd phone number type – Cell, Home, Work etc
Phone3AsIs	“string”		3^rd phone number as recorded
PhoneType3	“string”		3^rd phone number type – Cell, Home, Work etc
Employer	“string”		Employer name
SpouseNameFirst	“string”		Spouse/partner first name
SpouseNameLast	“string”		Spouse/partner last name
Alert	“string”		Text to be presented in alert pop-up window
Balance	“decimal”		Client balance due
DiscountType	“string”		Discount type assigned in the PIMS (may be ClientType)
DiscountPct	“decimal”		Discount percentage associated with the DiscountType
flgInactive	“bool”		true = Client is marked inactive in the PMS
flgSuspendReminders	“bool”		true = Client does not receive pet reminders
flgReferralHospital	“bool”		true = This client record is a referral hospital
flgReferralDoctor	“bool”		true = This client record is a referral doctor
ReferralId	“string”		ID denoting how client heard about practice, website, referral, paper, etc
ReferralName	“string”		Name of referring client
Comments	“string”
Branch	“integer”	Y*	Sites.Id

*Branch is required for multi-site data sets.

Attachments (1)

csv

Client.csv
1.03 KB