FCM also supports importing data in an "Activity File" format, which is designed to match the specifications used by the BTQ Portal system wherever possible. Currently supported activity types are:
- Activity Type 2: Outreach Activity
- Activity Type 3: Discontinue Outreach
- Activity Type 5: Enrolled Service
- Activity Type 6: Discontinue Enrolled Service
The following activity types are not currently supported:
- Activity Type 0: Reject
- Activity Type 1: Transfer
- Activity Type 4: Signed Consent
- Activity Type 7: Pend Enrolled Service
- Activity Type 9: Demographic Update Only
The effects of these activities are as follows:
Activity Type 2 (Outreach Activity):
- Creates the patient if the patient does not already exist in FCM
- Creates a new outreach segment starting at the beginning of the month of the activity date if a segment covering the activity date does not already exist in FCM
- Creates an encounter on the specified activity date, assigning encounter types and core services using the "Outreach Methods" column and the following rules:
Outreach Methods |
||||
---|---|---|---|---|
ID | Description | Encounter Type created | Successful contact assumed? | Core Service assigned? |
1 | Mail/Email Outreach | No | No | |
2 | Phone/Text | Phone/Text Outreach | No | Yes: Comprehensive Care Management |
3 | In Person | In-Person Outreach | No | Yes: Comprehensive Care Management |
100 | Successful Face-To-Face | Successful Face-To-Face Outreach | Yes | Yes: Comprehensive Care Management |
Activity Type 3 (Discontinue Outreach)
- Adds an end date to an outreach segment that is active as of the activity date
- Adds the end date reason code specified in the activity file
Activity Type 5 (Enrolled Service)
- Creates the patient if the patient does not already exist in FCM
- Creates a new enrolled segment starting at the beginning of the month of the activity date if an enrolled segment covering the activity date does not already exist in FCM
- If an outreach segment is open as of the activity date, the outreach segment is ended
- Creates an encounter on the specified activity date, assigning encounter types and core services using the "Enrolled Service Delivery" and "Enrolled Service Method" columns along with the following rules:
Enrolled Service Delivery | ||||
---|---|---|---|---|
ID | Description | Encounter Type created | Successful contact assumed? | Core Service assigned? |
1 | No | No | ||
2 | Phone/Text | Telephone - Contacted | Yes | Yes, if an Enrolled Service Method is specified |
3 | In Person | In-Person Enrolled Activity | Yes | Yes, if an Enrolled Service Method is specified |
101 | Unsuccessful | Unsuccessful Enrolled Activity | No | No |
Enrolled Service Method | |
---|---|
ID | Description |
1 | Comprehensive Care Management |
2 | Care Coordination and Health Promotion |
3 | Comprehensive Transitional Care |
4 | Patient and Family Support |
5 | Referral to Community and Social Support Services |
Activity Type 6 (Discontinue Enrolled Service)
- Adds an end date to an enrolled segment that is active as of the activity date
- Adds the end date reason code specified in the activity file