electronic+Long-Term+Services+and+Supports+(eLTSS)+Pilots

include component="page" wikiName="siframework" page="eLTSS header" flat =eLTSS Dataset Comments and Dispositions=
 * The request for comments on the eLTSS Dataset is now closed. Thank you for all your participation and input! **
 * The final eLTSS Dataset (from Round 1 of Pilots) can be downloaded (as pdf) [[file:eLTSS_Dataset_2016-09-22_Published_Round_1_Dataset.pdf| here]] . **

media type="custom" key="28712666"

=Harmonized Data Elements (Final Dataset - ordered by "Date Discussed")= CT: Risk Mitigation Plan and Agreement form GA: Identified Areas of Risk KY: MWMA K-HAT assessment module or an uploaded assessment document MD: Risk Details MN: Identified risk and choice regarding services FEI: Risk Details || CT: Contact Phone Number in CFC Web Reporting Database KY: Element in uploaded document in MWMA MD: Phone Number MN: Phone Number FEI: Emergency Contact Phone Number || KY: Element in uploaded document in MWMA MD: Name MN: Key contact name FEI: Emergency Contact Name || CT: Contact Relationship in CFC Web Reporting Database KY: Element in an uploaded document in MWMA MD: Relationship MN: Relationship FEI: Contact Type || CT: Captured in CFC Database in Emergency Profile. Backup plans relating to formal/paid assistance is captured in Section 3 (Services to Support Backup Systems) of the CFC Service Tool KY: Element in an uploaded document in MWMA MN: Plan for unforeseen events, Plan for emergency health events, Plan for unavailable staffing that puts you at risk || || CO: Things that NEED TO CHANGE CT: Captured in Universal Assessment. Needs related to Transitional Services, Assistive Technology and Home Modifications are captured in the CFC Service Tool Budget Form KY: Is this service a result of a Service Needs Assessment outcome? MN: What are your strengths and needs? FEI: Clinical Needs and Support Needs that are Important For || CT: CFC Participant Phone # KY: Phone Number MD: Primary Phone # MN: Phone Number FEI: Primary Phone # || KY: Element in "Life Story" or entered narrative in MWMA MD: Strength Detail MN: What are your strengths and needs?, Supports and strengths used to meet this need FEI: Strength Detail || GA: Interventions, Outcome Notes KY: Objective MD: Steps/Actions MN: Support Needed FEI: Steps/Actions || 7/14/2016 7/7/2016 || Goals & Strengths || Goal || A statement of a desired result that the person wants to achieve. || String / Free Text || Y || Definition was modified from the 7/7 description of: A defined outcome that a person wants to achieve. This new proposal was discussed and approved on the 7/21 call. || CT: My Goals - What CFC services would you be using to accomplish this goal CO: Personal Goal, Service Goal GA: Desired Outcome KY: Goal MD: Desired Goals MN: Goal FEI: Desired Goals, Service Goals Desired Outcomes ||
 * **Date Discussed** || **Grouping** || **Data Element Name** || **Data Element Definition** || **Data Element Value Datatype / Format** || **Multiple Values (Y/N)** || **Comments / Discussion / Relevant Slide(s)** || **TEFT Grantee / Pilot Plan Element Mappings** ||
 * 8/4/2016 || Risks || Identified Risk || An aspect of a person’s life, behavior, environmental exposure, personal characteristic, or barrier that increases the likelihood of disease, condition or injury to self or others, or interaction with the criminal justice system. || String / Free Text || Y || [[file:8-04-16 Identified Risk Factor.pptx|Identified Risk Slide]] || CO: Checkboxes + Comments field
 * 8/4/2016 || Emergency Backup Plan || Emergency Backup Phone Number || The primary phone number of the individual or entity identified to provide necessary services and supports to the person in the event of an emergency or interruption to scheduled critical services as reflected in the Emergency Backup Plan. || Number / 111-111-1111 || N || [[file:8-04-16 Backup Contact Phone Number.pptx|Emergency Backup Contact Phone Number Slide]] || CO: Contingency Plan
 * 8/4/2016 || Emergency Backup Plan || Emergency Backup Name || The name of the individual or entity identified to provide necessary services and supports to the person in the event of an emergency or interruption to scheduled critical services as reflected in the Emergency Backup Plan. || String / First Name, MI, Last Name || Y || [[file:8-04-16 Backup Contact Name.pptx|Emergency Backup Contact Name Slide]] || CT: Contact Name in CFC Web Reporting Database
 * 8/4/2016 || Emergency Backup Plan || Non-Paid Emergency Backup Relationship Type || The relationship (e.g., spouse, neighbor, guardian, daughter) of the individual identified to provide necessary services and supports to the person in the event of an emergency or interruption to scheduled critical services as reflected in the Emergency Backup Plan. || String / Free Text || Y || [[file:8-04-16 Backup Contact Relationship Type.pptx|Emergency Backup Contact Relationship Type Slide]] || CO: Contingency Plan
 * 8/4/2016 || Emergency Backup Plan || Emergency Backup Plan Text || The free text description of how to address unforeseen events, emergency health events, emergency events, problems with medical equipment and supplies, and unavailable staffing situations for critical services that put the person’s health and safety at risk. || String / Free Text || Y || [[file:8-04-16 Emergency Backup Plan Text.pptx|Emergency Backup Plan Text Slide]] || CO: Contingency Plan
 * 8/4/2016 || Goals & Strengths || Assessed Needs || The clinical and/or community-based necessity or desire as identified through an assessment that should be addressed by a service. || String / Free Text || Y || 7/28 the community decided to put this in the parking lot. On 8/4 it was revisited. Since most states did capture this information it was decided that this should be core.
 * 7/28/2016 || Beneficiary Demographics || Person Phone Number || The primary phone number of the person whom the plan is for, or his/her legal representative, where applicable. || Number / 111-111-1111 || N || [[file:7-28-16 Person Phone Number.pptx|Person Phone Number Slide]] || CO: Phone
 * 7/28/2016 || Goals & Strengths || Strengths || A favorable attribute of oneself, his/her support network, environment and/or elements of his/her life as depicted by the person. || String / Free Text || Y || [[file:7-28-16 Strengths.pptx|Strengths Slide]] || CT: Captured in Universal Assessment
 * 7/21/2016 || Goals & Strengths || Step or Action || A planned measurable step or action that needs to be taken to accomplish a goal identified by the person. || String / Free Text || Y || [[file:7-21-16 Step or Action.pptx|Step or Action Slide]] || CT: My Goals - What do you hope to accomplish in your home and community with services
 * 7/21/2016
 * 7/7/2016 || Beneficiary Demographics || Person Identifier || A string of character(s) used to identify the person whom the plan is for.

This may be the Medicaid ID number where applicable. || String / Free Text || N || || CO: SSN CT: Medicaid # GA: Client Social Security Number, Client Medicaid # KY: Social Security Number, MAID# MD: MA# MN: MA# FEI: Medicaid # || || CO: SSN CT: Medicaid # GA: Client Social Security Number, Client Medicaid # KY: Social Security Number, MAID# MD: MA# MN: MA# FEI: Medicaid # || CT: Community Address in CFC Web Reporting Database KY: Address Line 1, Address Line 2, City, State, Zip Code, Zip +4, KY County/ Out of State MD: Current Address, Street Number, Apt number, City, State, Zip MN: Address, City, State, Zip Code, COR FEI: Address, County, Street Number, Apt number, City, State, Zip || CT: Consumer Heading Section of the CFC Web Reporting Database KY: Date of Birth MD: DOB MN: Date of Birth || || CO: First Name MI Last Name CT: CFC Participant Name GA: Client Name KY: First Name MI Last Name MD: Client Name MN: First Name MI Last Name FEI: Person's Name ||
 * 7/7/2016 || Beneficiary Demographics || Person Identifier Type || The type of unique identifier (e.g., Medicaid Number, State ID, Social Security Number) used to identify the person whom the plan is for. || String / Free Text || N || This element is slated to be used in conjunction with Person Identifier.
 * 7/7/2016 || Beneficiary Demographics || Person Address || The address of the person whom the plan is for. || String / Street Address, City, State, Zip Code, County || N || [[file:7-7-16 Person Address.pptx|Person Address Slide]] || CO: Street Address, City, State, Zip Code, County
 * 6/23/2016 || Beneficiary Demographics || Person Date of Birth || The birth date of the person whom the plan is for. || Date / MM/DD/YYYY || N || [[file:6-23-16 Person Date of Birth.pptx|Person Date of Birth Slide]] || CO: DOB
 * 6/23/2016 || Beneficiary Demographics || Person Name || The name of the person whom the plan is for. || String / First Name, MI, Last Name || N || NOTE: Person Name is a Common Clinical Dataset element.
 * 6/23/2016 || Service Information || Service Comment || Additional information related to the service being provided.

This field could capture additional information of the frequency of the service, how the person wants the service delivered and only used when the comment provides additional detail of the service not already handled by another element. || String / Free Text || N || || GA: Service Notes KY: Non-Waiver Service Comments MD: Comment MN: Comments; Support Instructions FEI: Comments || CT: CT’s CFC Service Tool only reflects monies awarded under the CFC program. Funding from other waivers are captured in the CFC Web Reporting Database KY: Source of Payment MN: Payer || KY: Service Subtotal MD: Annual Cost MN: Plan Total FEI: Annual || KY: Rate per Unit, PDS Rate per Units MD: Rate MN: Rate/Unit FEI: Rate || || CO: Service End Date GA: Service End Date KY: Service End Date, PDS Service Actual End Date MD: Frequency MN: Time Period FEI: Frequency || || CO: Service Start Date CT: Plan Date GA: Service Begin Date KY: Service Start Date, PDS Service Actual Start Date MD: Frequency MN: Time Period FEI: Frequency || || CO: Total Units KY: PDS Total Units, Utilized Units ||
 * 6/16/2016 || Service Information || Service Funding Source || The source of payment for the service. || String / Free Text || Y || [[file:6-16 Service Funding-Payment Source.pptx|Service Funding Source Slide]] || CO: Funding Source
 * 6/16/2016 || Service Information || Total Cost of Service || The total cost of a service for the plan. || Number / $ || N || [[file:6-16 Service Cost.pptx|Service Cost Slide]] || CT: Section Total Cost
 * 6/16/2016 || Service Information || Service Rate per Unit || The rate of one unit for a service. || Number / $ || N || [[file:6-16 Service Rate.pptx|Service Rate Slide]] || CT: Table A: Care Attendant Cost Chart Worksheet
 * 6/16/2016 || Service Information || Service End Date || The end date of the service being provided. || Date / MM/DD/YYYY || N || Each service has a start and end date. These dates may or may not align with the start and end date of the service plan itself.
 * 6/16/2016 || Service Information || Service Start Date || The start date of the service being provided. || Date / MM/DD/YYYY || N || Each service has a start and end date. These dates may or may not align with the start and end date of the service plan itself.
 * 6/16/2016 || Service Information || Service Total Units || The total number of units for each service for the duration of the plan. || Number / Numeric || N || This is the total number of units authorized per service. It is important for the beneficiary to know how much they started with, that way they can manage their services appropriately.
 * 6/16/2016 || Service Information || Service Unit Quantity || The numerical amount of the service unit being provided for a frequency.

This element is slated to be used in conjunction with Service Quantity Interval and Unit of Service Type elements to form a full description of how often a service is provided.

For example, a service being provided 7 units per week, the Service Unit Quantity = "7". For a service being provided 8 hours a day, the Service Unit Value = "8". || Number / Numeric || N || || Includes element values from all Grantees (CO, CT, GA, KY, MD, MN, FEI) ||
 * 6/16/2016 || Service Information || Unit of Service Type || A named quantity in terms of which services are measured or specified, used as a standard measurement of like services.

Values include: unit(s), minute(s), 8 hour(s), quarter hour(s), hour(s), half day(s), full day(s), day(s), week(s), month(s), dollar(s), meal(s), mile(s), visit(s)/session(s), installation(s), none, other (free text).

This element is slated to be used in conjunction with Service Unit Quantity interval and Service Unit Quantity elements to form a full description of how often a service is provided.

For example, a service being provided 7 units per week, the Unit of Service Type = "units". For a service being provided 8 hours a day, the Unit of Service Type = "hours". || String / List of Values || N || || Includes element values from all Grantees (CO, CT, GA, KY, MD, MN, FEI) ||
 * 6/16/2016 || Service Information || Service Unit Quantity Interval || A period of time corresponding to the quantity of service(s) indicated.

Values include: per day, per week, per month, per year, one time only, other (free text).

This element is slated to be used in conjunction with Unit of Service Type and Service Unit Quantity elements to form a full description of how often a service is provided.

For example, a service being provided 7 units per week, the Service Unit Quantity Interval = "per week". For a service being provided 8 hours a day, the Service Unit Quantity Interval = "per day". || String / List of Values || N || || CO: Frequency KY: Service Frequency, Total Prior Authorized Frequency, Total NOT Approved Frequency, PDS Service Frequency, Non-Waiver Frequency MD: Frequency Type MN: Frequency || GA: Care Coordinator Name KY: Case Manager First name, MI, Last Name MN: Case Manager/Care Coordinator Name FEI: Case Manager Name || CT: CFC Budget Form Support & Planning Coach Phone # GA: Care Coordinator Phone Number MD: Support Planner Phone Number in LTSS system Client Profile MN: Case Manager/Care Coordinator Phone Number FEI: Case Manager Phone || || CT: UCM Phone # GA: Provider Site Phone KY: PDS Provider Primary Phone Number, Non-Waiver Provider Primary Phone Number, CDO Representative Information || 6/2/2016 || Service Provider Name & Other Identifiers || Service Provider Name || The name of the entity or individual providing the service.
 * N/A || Service Provider Name & Other Identifiers || Support Planner Name || The name of the person (e.g., Case Manager, Care Coordinator, Plan Coordinator) who helped develop the plan. || String / First Name, MI, Last Name || N || This element was added in response to a comment. We originally stated that the Support Planner Printed Name could be used for this element, but realize that could be confusing for implementers. So, we are adding Support Planner Name as its own element to accompany the Support Planner Phone Number element. || CO: Case Manager Name
 * 6/16/2016 || Service Provider Name & Other Identifiers || Support Planner Phone Number || The primary phone number of the support planner. || Number / 111-111-1111 || N || [[file:6-16 Case Manager.pptx|Support Planner Phone Number Slide]] || CO: Case Manager Phone
 * 6/9/2016 || Service Provider Name & Other Identifiers || Service Provider Phone Number || The primary phone number of the service provider. || Number / 111-111-1111 || N || It was agreed that the beneficiary or support planner needs to decide when they want a phone number displayed for a service provider. It may only be needed or beneficial to have for certain service providers.
 * 6/9/2016

For paid services use the organization/agency name, for non-paid services use the first and last name of the individual providing the service. || String / Free Text || N || || CO: Provider (CO) CT: Universal Care Manager Name; Access Agency of UCM; Support and Planning Coach Name; if Agency Based, name of Agency KY: PDS Employee Name, Provider Name, PDS Provider Name, Non-Waiver Provider Name MD: Provider Name MN: Provider FEI: Provider Name || KY: PDS Employee Relationship MN: Provider ||
 * N/A || Service Provider Name & Other Identifiers || Non-Paid Service Provider Relationship Type || The relationship (e.g., spouse, neighbor, guardian, daughter) of the individual providing a non-paid service or support to the person. || String / Free Text || N ||  || CO: Provider
 * 6/2/2016 || Service Information || Service Name || Identifies the paid or non-paid services provided to a person.

Include the code and display name plus any modifiers when a coding system (e.g., Healthcare Common Procedure Coding System (HCPCS), Home Health Revenue Codes) is used. || Text / display name, code, modifier || Y || || CO: Service CT: Step 2: “Understanding the Services and Supports CFC Offers” of the CFC Service Tool guide GA: Waiver Services, Service Type KY: Service Name MD: POS Service MN: Service FEI: Service || KY: I certify that I have made an informed choice when selecting the providers/employees to provide each service, The Individual understands that under the waiver programs, they may request services from any Medicaid provider qualified to provide the service and that a listing of currently enrolled Medicaid providers may be obtained from Medicaid Services MD: A checkbox that indicates that the client has been given choice in their providers MN: I was offered a choice of providers for services I am receiving. (Yes/No), I agree with the services, supports, and providers in my plan. (Yes/No) FEI: As the person this Plan of Services and Supports is being developed for, I agree that by signing this I was presented with all of my service options under this program. I also acknowledge that for the services selected, I was provided with all of the available providers of those services and authorize that I have selected the providers listed in this Plan of Services and Supports. || CT: If you are not interested in services in this section initial here: KY: This is to certify that Individual/Legal Representative have been informed of waiver services. Consideration for waiver program as an alternative to institutional placement is requested. MD: A checkbox that indicates that the client has they participated in making the plan, and that they agree with the requested services. MN: : I was given choices of different types of services that could meet my assessed needs as indicated on the Community Support Plan Worksheet I received and through discussion with my case manager. (Yes/No), I agree with the services, supports, and providers in my plan. (Yes/No) FEI: As the person this Plan of Services and Supports is being developed for, I agree that by signing this I was presented with all of my service options under this program. I also acknowledge that for the services selected, I was provided with all of the available providers of those services and authorize that I have selected the providers listed in this Plan of Services and Supports. || 5/12/2016 || Financial Information || Plan Funding Source || The source(s) of payment for the plan. || String / Text || Y || Continued discussion from 5/12. The community agreed that this should be a core element. It was decided that the list of values will vary by state and implementation. The funding source at the specific service level (e.g., Funding Source (CO)) will be addressed when we discuss service-specific elements in a few weeks. || KY: Source of Payment MN: Funding the Plan || || CO: Signature of Case Manager Date CT: CFC Budget Form Support & Planning Coach Signature Date in the CFC Service Tool Budget Approval Form KY: Case Manager E-Signature Date MD: Signature Date MN: Signature of Person Who Developed This Plan Date FEI: Signature Date || || CO: Signature of Legal Guardian Date CT: Guardian/Legal Representative Signature Date in future revision of the CFC Service Tool Budget Approval Form KY: Individual E-Signature Date MD: Signature Date (with an indicator stating that the person signing is not the client) MN: Signature of Person or Guardian / Legal Representative Date || || CO: Signature of Client Date CT: Participant signature date in the CFC Service Tool Budget Approval Form KY: Individual E-Signature Date MD: Signature Date MN: Signature of Person or Guardian / Legal Representative Date FEI: Signature Date || || CT: Annual Budget in the CFC Service Tool Budget Approval Form KY: Total Prior Authorized Amount MD: Recommended Flexible Budget || KY: Total Prior Authorized Amount MD: Total POS Cost MN: Total Plan Cost FEI: Total PSS Cost || 5/5/2016 || Plan Signatures || Person Printed Name || The printed or typed name of the person. || String / Free Text || N || || CT: Participant Name in the CFC Service Tool Budget Approval Form KY: Signature Name MD: Signature Name FEI: Signature Name || 5/5/2016 || Plan Signatures || Guardian / Legal Representative Printed Name || The printed or typed name of the guardian/legal representative. || String / Free Text || Y || || CT: Guardian/Legal Representative Name in a future revision of CFC Service Tool Budget Approval Form KY: Signature Name MD: Signature Name FEI: Signature Name || 5/5/2016 || Plan Signatures || Support Planner Printed Name || The printed or typed name of the support planner. || String / Free Text || N || || MD: Signature Printed Name FEI: Signature Name || || CO: Client Signature CT: Participant Signature in the CFC Service Tool Budget Approval Form KY: Individual's Signature MD: Client Signature MN: Signature of Person or Guardian/Legal Representative FEI: Person Signature || CT: Guardian/Legal Representative Signature field in a future revision of CFC Service Tool Budget Approval Form KY: Individual, Authorized Representative and/or Legal Guardian has signed the Plan signature sheet (Yes, No) MD: Client Signature (with an indicator stating the person signing is not the client. MN: Signature of Person or Guardian/Legal Representative, Other Signature || CT: CFC Budget Form Support & Planning Coach Signature in the CFC Service Tool Budget Approval Form GA: Care Coordinator Signature KY: Case Manager Signature MD: Support Planner Signature MN: Signature of Person Who Developed This Plan FEI: Case Manager Signature || || CO: HCBS Waiver Program / Program CT: captured in CFC web reporting data base and used to calculate total CFC budget GA: Program Name KY: Program MD: Program Type MN: Program FEI: Person is Enrolled In ||
 * 5/26/2016 || Service Preferences || Person Service Provider Choice Indicator || States whether or not the person was offered a choice of providers and made an informed choice in selecting the provider for each service. || Boolean / Yes, No || N || [[file:Service Provider Preferences - Person Service Provider Choice Indicator.pptx|Person Service Provider Choice Indicator Slide]] || CO: Client has been offered or given a resource list of qualified providers, Client has been informed of the availability and right to select among qualified providers, Client has been informed of his/her right to change providers at any time, Client has been informed that providers have the right to accept or deny the request for services, Client has been informed of any potential conflict of interest
 * 5/26/2016 || Service Preferences || Person Service Agreement Indicator || States whether or not the person was given a choice of services and participated in the selection of and agrees to the services outlined in the plan. || Boolean / Yes, No || N || [[file:Service Preferences - Person Service Agreement Indicator.pptx|Person Service Agreement Indicator]] || CO: I have participated in the development of this plan and I agree with the services outlined., Client/Guardian indicates that he/she is in agreement with the information in the Service Plan and agrees to receive services accordingly., Client has been informed of his/her choice of available long term care programs and services
 * 5/19/2016
 * 5/19/2016 || Plan Signatures || Support Planner Signature Date || The date the support planner signed the plan. || Date / MM/DD/YYYY || N || Every signature type on the plan will be accompanied by a date.
 * 5/19/2016 || Plan Signatures || Guardian / Legal Representative Signature Date || The date the guardian/legal representative signed the plan. || Date / MM/DD/YYYY || N || Every signature type on the plan will be accompanied by a date.
 * 5/19/2016 || Plan Signatures || Person Signature Date || The date the person signed the plan. || Date / MM/DD/YYYY || N || Every signature type on the plan will be accompanied by a date.
 * 5/12/2016 || Financial Information || Total Plan Budget || The total allotment of funds for services and supports approved or authorized for a plan. || Number / $ || N || Grantees agreed that Total Plan Budget should be a core element. Each implementation will arrive at that total budget amount from calculating "miscellaneous budget elements".
 * 5/12/2016 || Financial Information || Total Plan Cost || The estimated total cost of all services and supports for a plan. || Number / $ || N || [[file:5-12 Total Plan Costs.pptx|Total Plan Cost Slide]] || CT: Total of All CFC Services in the CFC Service Tool Budget Approval Form
 * 5/12/2016
 * 5/12/2016
 * 5/12/2016
 * 5/5/2016 || Plan Signatures || Person Signature || The depiction of the person's signature as proof of identity and intent for the plan. || String / Signature || N || Conforms to person-centered planning guidance regulations.
 * 5/5/2016 || Plan Signatures || Guardian / Legal Representative Signature || The depiction of the guardian or legal representative's signature as proof of identity and intent for the plan. || String / Signature || Y || [[file:5-5 and 5-12 Plan Signatures – Who.pptx|Plan Signatures Slide]] || CO: Legal Guardian
 * 5/5/2016 || Plan Signatures || Support Planner Signature || The depiction of the support planner's signature as proof of identity and intent for the plan. || String / Signature || N || [[file:5-5 and 5-12 Plan Signatures – Who.pptx|Plan Signatures Slide]] || CO: Case Manager Signature
 * 4/28/2016 || Financial Information || Program Name || The state-administered funding source (e.g., Medicaid) in which the person is enrolled. || String / Free Text || Y || Core element for the eLTSS Plan, but each implementation will have a different list of values specific to their state/pilot.
 * 4/21/2016 || Plan Period / Plan Effective Dates || Plan Effective Date || The date upon which the plan goes into effect.

Start date is required, end date is optional. || Interval of Dates / MM/DD/YYYY -MM/DD/YYYY || N || || CT: Plan Date GA: Care Plan Period KY: Proposed Start Date, Level of Care End Date MD: POS Effective Date MN: Time Period Covered by the CSSP Start Date, Time Period Covered by the CSSP Start Date FEI: Effective Date ||

=Parking Lot Data Elements=
 * **Date put in Parking Lot** || **Grouping** || **Element Area** || **Elements of Interest** || **Discussion** ||
 * 8/11/2016 || Risks || Risk Mitigation Plan Text || MN: Plan/agreement reached to address the identified risks || Draft Definition: An attached description of the options and actions to reduce the likelihood that a risk will occur and/or reduce the effect of a risk if it does occur.

Discussed on 8/4/2016. It was decided that this should be included; however it was proposed that instead if a free text it should be a yes or no question. On 8/11 it was decided to put this element in the parking lot. Grantees do have a risk mitigation plan but only MN includes it inside the service plan. Other grantees include the risk mitigation plan as an addendum to the service plan. CMS did state that it is okay for the plan to just reflect that a rick mitigation plan exists somewhere and that an indicator would be sufficient. || 07/28/2016 || Goals & Strengths || Perceived Needs || MN: Description of need; Support Needed || A description of whatever the person believes is important to living in the community.
 * 8/4/2016

On 7/28/2016 It was said that Perceived Needs should be a core element. After reviewing the recording and notes from the meeting, it was decided that we need to revisit this element.

On 8/4 it was decided that since MN is the only grantee that has element this element it will be placed in the parking lot. || Amanda Hill believes it is in reference to those who are implementing the plan and signing an agreement but will do some researching on that. ACL Guidance states: “All persons directly involved in the planning process must receive a copy of the plan or portion of the plan, as determined by the participant or representative“. || || || ||
 * 6/23/2016 || Service Planning & Coordination || Plan Recipients || MN: My CSP / CSSP can be shared with the following people and/or providers for planning and coordination and I have signed release(s) of information to allow this sharing || PCP regulations state the plan must “Be distributed to the individual and other people involved in the plan”. What does “other people involved in the plan” mean – who exactly? Does this mean the List of people who should receive the plan be listed on the plan? Or can this “list of recipients” be captured somewhere else?
 * 6/23/2016 || Service Planning & Coordination || Plan Participants || CO: Plan Participant Name; Plan Participant Title || CO currently captures the names and titles (roles) of the people who helped develop the plan. MN has checkboxes indicating if the person was able to invite who they wanted to be involved in the planning process. It is understood that the PCP rules indicates that the person has a choice, but the rule is not prescriptive on how this should be captured in the plan. The Plan Participants could already be covered by the eLTSS core elements related to plan signatures.
 * 5/19/2016 || Service Planning & Coordination || Plan Signatures || Provider Signature || This element is only captured by MD currently, so we will revisit when current harmonization phase is complete and additional Person Centered Planning elements are discussed. If Provider Signature is included as a core element, include Provider Signature Printed Name and Provider Signature Date to be consistent with other signature elements. We also need to discuss whether or not the Service that the Provider delivered needs to accompany the signature (MD currently does this).
 * 5/26/2016 || Service Planning & Coordination || Person's Choice in Setting (residence) || N/A || This is not currently captured by Grantees, but is written in the Person Centered Planning regulations. This was briefly discussed in conjunction with service delivery preference elements, but since this element is not currently captured, we will revisit after this phase of harmonization. Grantees agreed that service delivery setting usually equals residence setting (since the eLTSS plan is for home and community based services).

=Non-Core eLTSS Data Elements - (Consensus)=
 * **Date Discussed** || **Element Name** || **Comments** ||
 * 8/4/2016 || Measure to Minimize Risk || Precautionary steps used to reduce the likelihood, or to manage the severity of a possible risk to personal safety, health and behavioral risk.

Maps to: Alternative measure that may be implemented (MN)

Grantees decided that measures to minimize risk could be included in the risk mitigation plan and there was no need for two separate elements. ||
 * 8/4/2016 || Date the Risk was Created || The date the risk was put on the plan.

Maps to: Date Created (Risks) (MD)(FEI)

This date is pre-populated based on the date that InterRai assessment was performed or the date the risk is added to the plan which would be the same as the Plan Created Date. ||
 * 7/21/2016 || Goal Completed Date || The date on which the goal was achieved.

Maps to: Target /Actual Objective Completed Dates (KY), Target Date (MN)

This is not core since the majority of the grantees did not track or capture the completion of the goal. Currently, grantees’ plans are static in nature. If a goal is completed before the annual plan review date, most grantees will create a new plan with new goals. ||
 * 7/21/2016 || Goal Created Date || The date on which the goal was created by the person.

Maps to: Date (CT ), Date Objective Developed (KY), Date Created (MD, FEI)

This is not core since the grantees that do collect this date state that the date the goal is created is usually the same as the date the plan was created. ||
 * 7/21/2016 || Goal Status || The condition or state of a goal at a particular time.

Maps to: Status (GA), Objective Status (KY), Progress (FEI)

This is not core since the status of goals is not captured directly in the plan by all grantees. Currently, grantees’ plans are static in nature. If there is a change in status, a new plan is generated rather than a status being updated. ||
 * 7/21/2016 || Outcome || The actual endpoint of the goal.

Maps to: Outcomes (CT)

This is not core since the majority of the grantees currently do not have this level of “case management tracking” in their service plans. Some grantees collect this information at the end of the plan and is not captured directly on the plan. ||
 * 6/23/2016 || Service Reason || Need to follow-up with MD and what is typically included for their Reason for Service/Details element. In the meantime, this element is being marked as not core. KY uses their reason elements for internal tracking purposes only and are specific to delays in services being provided.

Maps to: Reason for Service/Details (MD), Specify reason for delay, Delay Reason Comments, Specify Reason Service End (KY), Support Needed (MN) ||
 * 6/23/2016 || Service Status || KY and MN are the only grantees who currently capture the status of each service being provided. They both mentioned that they see this as something that is important for their planning process, but should not be listed as a core eLTSS element.

Maps to: Service Status (KY), Status (MN) || 6/9/2016 || Service Provider Qualifications || Service Provider Qualifications will not be a core element on the eLTSS Plan. There is nothing specifically stated in the PCP regulations that Provider Qualifications need to be captured in the plan. Currently only CT captures qualifications of service providers in their plan. CT requires that providers have certain qualifications and this is a criteria based on certification. This information collected is similar to what would be found on a resume. MN no longer captures "qualifications" in their plan, but instead the individual states their needs in a "Support Instructions" field and then providers are selected (from provider enrollment information) based on those needs.
 * 6/16/2016

Maps to: PCA Qualifications, Documentation of how employee (PCA) meets qualification (CT), Qualifications of staff implementing the support plan, Support Instruction (MN) ||
 * 6/16/2016 || Service Delivery Days of the Week || Service Delivery Day should not be included as a core element. This information is negotiated between the provider and beneficiary and may change frequently which would make plan management and revisions impossible to maintain.

Maps to: Days of Service Delivery (KY), Mon, Tue, Wed, Thu, Fri, Sat, Sun (GA) ||
 * 6/9/2016 || Service Provider Identifier || The Grantees currently use Service Provider Identifier for billing and service authorization purposes. It is not something needed for sharing the plan.

Maps to: Provider DMA No. (GA), Provider Number (KY) (MD), Provider NPI (MN) ||
 * 6/9/2016 || Service Provider Address || Service Provider Address will not be a core element on the plan. KY states this information is pre-populated for traditional (paid) services. MD captures the provider's address for their emergency back-up plans only. MN's county of service is brought over from the assessment and not considered core to the plan.

Maps to: County of Service, PDS Employee Address (KY), COS (MN) ||
 * 6/2/2016 || Exceptions for Service || Each Grantee who captured Exceptions for Service had a unique way of capturing and displaying this element on their plan. It was agreed that these elements could not be harmonized as a core component.

Maps to: Requested One Time Expense (CT), Exceptional Rate Request, Exceptional Rate per Unit, Reason for Exceptional Rate Request (KY), Personal Assistance, Home-Delivered Meals, Other Items that Substitute for Human Assistance, Reason for Exceptional Rate Request (MD), EW Conversion Request (MN) ||
 * 6/2/2016 || Type of Service Provided || The 3 Grantee / Pilot who utilized the element service type captured data that was very different and state specific. There were no commonalities in the values for this element. It was agreed that these elements could not be harmonized as a core component.

Maps to: Service type ( GA) (KY) (MD) ||
 * 6/2/2016 || Service Category || Each Grantee / Pilot has a unique way of capturing and displaying service category on their plan. It was agreed that these elements could not be harmonized as a core component.

Maps to: Natural Supports, Third Party Resources, State Plan Benefits, Home Health, Long Term Care Service Plan (CO), CFC Services for assistance with hands-on Care/Cueing/Supervision, CFC Services to assist with managing budget, service planning etc., CFC Service to Support Back Up Systems, CFC Service to assist with increasing independence in health related tasks… (CT), Cognition, Functional, Client, Clinical, Social (GA), Cognitive and Behavioral Supports, Prevention of Abuse and Neglect, Supportive Services, Home Management, Caregiver/Parent Support, Personal Assistance, Communication, Health-Related/Medical, Training/Skill Building, Personal Security, Case Management, Other Informal Supports (MN) ||
 * 5/26/2016 || Address to Receive Services - Miscellaneous Elements || These miscellaneous elements related to the address or setting where services are delivered are assessment in nature. They are important to know, but are not be core to the eLTSS plan.

Maps to: Current Living Situation (CO), Lives with Family, Home Type, Home Setting (MD), Number of People in Home, Lives with? (FEI) ||
 * 5/26/2016 || Service Delivery Setting Type || Services under the eLTSS plan will be delivered in a home or community setting. Some Grantees do not distinguish between home and community, they are treated as the same. Grantees/Pilots agreed that services will be received in the individual’s home or community setting. Many grantees see home = community so there is no need for a distinction.

Maps to: Will this service be provided at the individual's home?, Setting (KY), Address Type (MD) ||
 * 5/26/2016 || Service Delivery Location Preferences || Services under the eLTSS plan will be delivered in a home or community setting. It is understood that is where the individual prefers to receive services (rather than in an institution-based setting).

Maps to: Is Setting Chosen by the participant?, Is setting chosen by Guardian of Person? (MD), I was given a choice between received services in the community or in an institution. (MN), Is Setting Chosen by the participant?, Is setting chosen by Guardian of Person? (FEI) ||
 * 5/26/2016 || Service Delivery Address || Services under the eLTSS plan will be delivered in a home or community setting. Some Grantees do not distinguish between home and community, they are treated as the same. KY stated that the address for delivery of services will most likely vary. For example, a community club may meet at various locations each week. MN captures the person's address as the "service delivery location". GA captures the service delivery location as the person's address or from the DMA No. CT is not prescriptive on where services are completed, just so that they are delivered in a home or community setting.

Maps to: Service Delivery Address, Address Line 1, Address Line 2, City, State, Zip, Zip +, County (KY), Service Delivery Address (MD), County (MN), Service Delivery Address (FEI) ||
 * 5/26/2016 || Emergency Contact Information || Elements related to a general emergency contact (i.e., contact this person if something happens to the individual) are collected at the assessment level and will not be eLTSS core components. Any contact information that is collected specifically for an Emergency Backup or Contingency Plan will be discussed later this summer.

Maps to: Emergency Contact Name, Emergency Contact Relationship (CO), Guardian of Person (MD), Emergency Contact Name, Emergency Contact Phone Number, Emergency Contact Relationship, Parent/Guardian Name and Phone Number, Physician/Healthcare Provider Name and Phone Number (MN), Guardian of Person (FEI) ||
 * 5/12/2016 || Financial Information: Miscellaneous Budget Elements || Each Grantee / Pilot has a unique way of capturing and displaying various budgets on their plan. It was agreed that these elements could not be harmonized as a core component.

Maps to: CFC Total Budget Allocation, CFC Monthly Budget Allocation (CT), CDPSS Budget (Monthly), Liability (GA), CFC Fixed Budget Total, CFC Flexible Budget Total (MD), EW/AC Case Mix Monthly Maximum Budget, EW/SIS Waiver Obligation, CDCS Annual Budget, Participant Contributions (Waiver Obligation / AC Fee), Authorized Daily Amount for CAC, CADI, BI, or DD Waiver, Authorized Monthly Amount for CAC, CADI, BI, or DD Waiver (MN), Cost Neutrality Limit (FEI) ||
 * 5/12/2016 || Financial Information: Miscellaneous Cost Elements || Each Grantee / Pilot has a unique way of capturing and displaying various costs on their plan. It was agreed that these elements could not be harmonized as a core component.

Maps to: Sections 1 - 4 Total Costs, Projected Annual Cost of Service, Annual Cost of All Waiver Services, Annual Cost of Husky Home Services (CT), Total Traditional Services Cost, Total Participant Directed Services Cost, Total Plan of Care Cost Requested (KY), Annual Waiver Services Total, Annual State Plan Services Total, Annual Non-Medicaid Services Total, MFP Flexible Funds Total (MD), AC Fee (MN), Waiver Services Total Cost (FEI) ||
 * 5/12/2016 || Plan Signatures: Signature Type/Signature on File || These are administrative in nature and should not be a core component of the eLTSS Plan.

Maps to: Legal Guardian Signature on file, Clients Signature on file, Additional Legal Guardian Signature on file, Case Manager Signature on file (CO), Individual, authorized Rep, and/or legal guardian has signed the plan signature sheet, The Case Manager has signed the plan signature sheet (KY), Signature Type (FEI) ||
 * 5/5/2016 || Plan Signatures || Other optional or state-specific signatures.

Maps to: DSS CO Staff (CT), Care Coordinator Collaborator Signature (GA), Emergency Backup Signature (MD), Backup Provider Signature (FEI) ||
 * 4/28/2016 || Plan Comments/Narrative Text || Grantees/pilots currently use this field for administrative purposes or any items from assessments that can't be put in another field.

Maps to: Overall Comments (KY), Narrative (MD), Overview Comments (FEI) ||
 * 4/28/2016 || Plan Status || These elements are administrative in nature and are largely used for internal purposes.

Maps to: Plan Status (KY), POC Status (MD) ||
 * 4/28/2016 || Plan Type/Category || These elements are administrative in nature and are largely used for internal purposes.

Maps to: Service Plan Type (CO), Care Plan Type (GA), Category of Plan (KY), Plan of Service Type (MD), PSS Type (FEI) ||
 * 4/21/2016 || eLTSS Plan Created Date || Include as an Optional element. This is an administrative element (mostly used for audit and tracking purposes) and is defined differently via the Grantees and Pilots. This could be the date the plan was entered into a system or the date the plan is considered complete (or both).

Maps to: Date (CT), Date Entered (CO), Care Plan Visit Date (GA), Created Date (MD), Date Support Plan was mailed/given on (MN), Created Date (FEI) ||

=Tentative Meeting Schedule= For details on how to join the meeting, click here to return to the homepage -- Dataset Review and Comment Period || Risk Management Plan --- N/A || Plan/agreement reached to address the identified risks (MN) -- N/A || Should the risk mitigation plan element be a yes or no question instead of a free text? Does this belong as a core element? --- Timeline and process for providing comments on the eLTSS Dataset ||
 * **Date to be Discussed (TENTATIVE)** || **Core Component** || **Element Area** || **Elements of Interest** || **Discussion Points** ||
 * 8/11/2016 || Risks
 * 8/25/2016 ||  ||   ||   || ** Meeting is cancelled. ** Use this time to work internally to review and provide comments on the eLTSS Dataset. ||
 * 9/01/2016 ||  ||   ||   || Office Hours are being held for the TEFT Grantees ||
 * 9/06/2016 ||  ||   ||   || All comments on the working draft eLTSS Harmonized Dataset are due by 6pm ET (3pm PT) today ||
 * 9/08/2016 - ** Meeting Cancelled ** ||  ||   ||   || Office Hours are being held for the TEFT Grantees ||
 * 9/15/2016 ||  ||   ||   || eLTSS Dataset Comment Disposition Review ||
 * 9/22/2016 ||  ||   ||   || Final eLTSS Dataset published on wiki and Kick-Off Round 2 of Pilots ||

=Pilot Introduction= The electronic Long-Term Services & Supports (eLTSS) Initiative is a ONC-CMS partnership that is working towards the identification and testing of electronic standards that can enable the creation, exchange and re-use of interoperable service plans for use by health care and community-based long-term services and supports providers, payers and the individuals they serve. These plans can help to improve the coordination of health and social services that support an individual’s mental and physical health.

A pilot is a feasibility study or experimental trial launched on a relatively small scale to help an organization learn how a larger-scale project might work in practice. The eLTSS Pilot Program is driven by the functional requirements contained with the eLTSS Community identified eLTSS Use Case. Please refer to the eLTSS Timeline for activity dates.

The purpose of the eLTSS Pilot phase is to validate evolving technology in real-world situations and aid in learning the policies that will be required for an operational system, identify barriers for implementation, and revise harmonized specifications based on real-world lessons learned. The pilot demonstrations will be transitioned to open source communities for future reference implementations and long term sustainment.


 * We are seeking organizations who may be interested in participating as a Pilot Site.** Please fill out the form found on the eLTSS Pilot Interest Survey page if your organization is interested in becoming a Pilot Site for eLTSS.

If you have not already done so, please take a moment to SIGN UP HERE as a member of the eLTSS Initiative.

=Past Pilot Presentations= ||= || ||=  || ||=  || ||=  || ||=  || ||=  || ||=  ||
 * = **TEFT** ||= **NON-TEFT** ||
 * = Arizona
 * = Colorado
 * = Connecticut
 * = Georgia
 * = Kentucky
 * = Maryland
 * = Minnesota
 * =  ||= [[file:elTSS Pilot Planning Template National Disability Institute_10.21.15.ppt|National Disability Institute]] ||
 * =  ||= [[file:elTSS Pilot Presentation 11.12.15 Final Peer Place.ppt|Peer Place]] ||
 * =  ||= [[file:Pilot Slideshow Final-new Logo (revised).pptm|Therap Services]] ||

=Pilot Starter Kit= Please start here with the ReadMe before you continue.
 * < **Document Name** || **Description** ||
 * [[file:eLTSS Pilot Guide Readme for Pilot Guide_2015.09.30.docx|eLTSS Pilot ReadMe]] || This Readme document serves as a high-level overview of the contents of the eLTSS Pilot Guide, which is comprised of the Three-Tiered Pilot Approach, the Functional Requirements Matrix and information on how to best leverage them to support Pilot success. ||
 * [[file:eLTSS Tiered Approach for Pilot Guide_2015.09.29.docx|Tiered Approach For Pilot]] || A document that provides a detailed description of the incremental tiers for eLTSS pilot implementation. ||
 * Functional Requirement Matrix || Functional requirements for creating, sharing and administering an eLTSS plan that have been previously defined as part of the eLTSS Use Case work. ||
 * [[file:eLTSS Dataset Fillable Worksheet 1.25.16 final.pdf|eLTSS Dataset Worksheet]] || To further assist the piloting process, this fillable form will help to capture necessary data elements and values. Please be as detailed as possible and feel free to send multiple pages if needed.

This power point will provide guidance on how to save the RTM form locally to afford the user the capability to save answers as the form is being worked on and completed. Note: you cannot save on the browser. For further support, if the form will not save properly you may need to update your Adobe Reader. ||
 * RTM Troubleshooting Guide**:
 * [[file:eLTSS round 2 Pilot Planning template v2.pptx|Round 2 Pilot Planning PPT Template]] || A PowerPoint template for potential round 2 pilots to use to present their Pilot Team; Goal of the Pilot; Pilot Ecosystem; Pilot Workflow; Standards and Technologies Under Consideration; Timeline; Definition of Success; and Risks & Challenges of their pilot. ||
 * [[file:elTSS Pilot Planning Template v1.1 11.12.15.ppt|Pilot Planning PPT Template]] || A PowerPoint template for potential pilots to use to present their Pilot Team; Goal of the Pilot; Tier of Interest; Use Case Scenario and Actors/Systems; Minimum Configuration; Timeline; Success Criteria; In Scope/Out of Scope; and Risks & Challenges details of their pilot. ||
 * [[file:eLTSS Pilot PPT Word Template V4.doc|Pilot Plan Word Template]] || (An alternative to the Pilot Planning PPT) A word template for potential pilots to use to present their Pilot Team; Goal of the Pilot; Tier of Interest; Use Case Scenario and Actors/Systems; Minimum Configuration; Timeline; Success Criteria; In Scope/Out of Scope; and Risks & Challenges details of their pilot. ||
 * [[file:eLTSS Round 1 Pilot Checklist (1).docx|eLTSS Round 1 Pilot Artifact Checklist]] || Please submit this checklist to the eLTSS Pilot Support Team katiya.shell@esacinc.com. All items must be checked to complete the artifact submission phase for Round 1 Pilots. ||

=Pilot Resource Materials=
 * **Document Name** || **Description** ||
 * [[file:eLTSS Pilot Two-Pager.docx|Pilot Overview Document]] || An overview of the eLTSS Pilots Workgroup including a Value Statement for Participating Entities, Benefits of Participation as an eLTSS Pilot Site and steps for How to Get Started. ||
 * Pilots Overview Presentation || A presentation for potential pilots that provides an overview of the electronic Long-Term Services and Supports Pilot Planning, Activities, Artifacts and Evaluation ||
 * [[file:eLTSS All Hands 2015-08-13.pptx|Institute for Healthcare Improvement: A Guide for Idealized Design]] || The purpose of this guide is to describe the new Idealized Design process and details around its use. An overall principle used in developing the guide is to better manage the uncertainty that is associated with new ideas for system redesign that are to be developed and tested. ||
 * [[file:eLTSS Domain Harmonization Matrix_20150817.xlsx|Domain Harmonization Matrix]] || eLTSS community defined set of domains/subdomains and exemplar question/answer sets that an eLTSS Plan would need to include. ||

=Pilot Timeline=

=Pilot Team=
 * **Initiative Coordinator** || Evelyn Gallego || evelyn.gallego@emiadvisors.net ||
 * **Project Management** || Lynette Elliott || lynette.elliott@esacinc.com ||
 * **Pilot Management** || Jamie Parker || jamie.parker@esacinc.com ||
 * **PM Support / Use Case and Functional Requirements** || Becky Angeles || becky.angeles@esacinc.com ||

include component="page" wikiName="siframework" page="space.template.inc_contentleft_end" 