← Back to entities

Moreland 2025 Strategy

project 975e0cc5ed12dcd4

Normalized: moreland 2025 strategy

moreland_contracts

Entity Properties (gold project table)

project_id

975e0cc5ed12dcd4

name

Moreland 2025 Strategy

client_id

—

canonical_metadata

—

created_at

2026-02-12 05:36:54.288209+00:00

updated_at

2026-02-12 05:36:54.288209+00:00

status

—

billable

—

recurring

—

squad

—

qa_partner

—

project_manager

—

lead_dev

—

description

Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes.

state

—

team_name

—

closedate

—

dealstage

—

contract_type

time_and_materials

contract_hourly_rate

—

contract_estimated_hours

350.0

contract_total_fee

—

53%

Moderate — a somewhat similar entity exists

85%

Good match quality

Source Mappings (91)

	Source	Source ID	Display Name	Confidence	Method	Status
	moreland_contracts	TA0MsvJAupmZPQ	Moreland 2025 Strategy	1.00	exact	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name Moreland 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-04T06:05:52.631771+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	R5AJA2bpbXGlKA	Moreland 2025 Strategy	1.00	exact	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name Moreland 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-23T00:05:50.351769+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	YEqa8eDv1njHPA	Moreland 2025 Strategy	1.00	exact	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name Moreland 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-25T12:05:03.521813+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	+1I6a98tLO9EyQ	Moreland 2025 Strategy	1.00	exact	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name Moreland 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-20T18:04:44.009722+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	qpCzGt2YewyHvA	Moreland 2025 Strategy	1.00	exact	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name Moreland 2025 Strategy contact_person Justin contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-22T02:05:18.408433+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	6OpUEA5KkZ4SPQ	Moreland 2025 Strategy	1.00	exact	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name Moreland 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-03T18:05:26.204025+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	IGFCVJNKI2+xMQ	Moreland 2025 Strategy	1.00	exact	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name Moreland 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-02T18:04:44.764845+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	fbL3EVngo+O9iw	Moreland 2025 Strategy	1.00	exact	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name Moreland 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-22T06:04:31.627411+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	PLxX39HAlOd5fw	Moreland 2025 Strategy	1.00	exact	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name Moreland 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-21T06:05:03.950906+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	kniaZ7k95oIkYw	Moreland 2025 Strategy	1.00	exact	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name Moreland 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-05T12:05:27.813106+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	LCv2TX7DwVYwEQ	Moreland 2025 Strategy	1.00	exact	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name Moreland 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-21T00:05:31.777289+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	CmA3RcXU3gOhUA	Moreland 2025 Strategy	1.00	exact	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name Moreland 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-22T02:05:22.719463+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	M54uc8InVLwfIQ	Moreland 2025 Strategy	1.00	exact	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name Moreland 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-26T00:05:11.458858+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	5r3JNsYNd9tlCA	Moreland 2025 Strategy	1.00	exact	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name Moreland 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-06T00:05:08.610118+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	P+Aqh6Z5CbFWgg	Moreland 2025 Strategy	1.00	exact	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name Moreland 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-29T02:05:38.617838+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	c2rzSIcDxmF1dA	Moreland 2025 Strategy	1.00	exact	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name Moreland 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-05T06:04:58.862496+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	LtHVXkZcrUBTNA	Moreland 2025 Strategy	1.00	exact	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name Moreland 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-04-08T21:08:24.296172+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	62E859qwMhd+3w	Moreland 2025 Strategy	1.00	exact	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name Moreland 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-02T17:48:23.547938+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	ceeuLjliQxejAA	Moreland 2025 Strategy	1.00	exact	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name Moreland 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-31T02:06:15.790152+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	mMfITdUVeLMTlA	Moreland 2025 Strategy	1.00	exact	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name Moreland 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-04-15T02:05:39.746917+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	/ODdx5Du7PXWcQ	Moreland 2025 Strategy	1.00	exact	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name Moreland 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-26T02:06:57.174354+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	dsSmQv9gGOKGTg	Moreland 2025 Strategy	1.00	exact	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name Moreland 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-04-09T13:59:14.974936+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	wS8jfb7axAErEw	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-26T06:05:29.799157+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	S4KvtfJSfT/itw	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-26T02:05:22.052969+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	oMA/ec+66k6WDQ	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-25T02:05:10.705017+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	jF6Q+u88dIvK2g	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-22T00:04:45.999557+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	fbjLDIMZ4H6ZiA	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-21T12:04:59.286966+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	+FKmY7u//wCADg	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-22T12:04:58.116345+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	QirIRMS8Wb/nNw	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-19T12:05:33.706221+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	3f50nD5XKkaFQg	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-24T00:04:48.560408+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	5oaIY6NJKSi9nA	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-03T00:04:36.731804+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	HhZHx1j1mijEIA	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-23T02:05:51.217433+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	7czpobyZ80k9Qw	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-25T02:06:41.383780+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	ua6m+BQuRgE5aQ	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control. start_date — extracted_at 2026-04-08T02:05:59.514188+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	XWkh3//Trp1yIw	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and service level agreements. start_date — extracted_at 2026-04-05T02:05:38.417739+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	IwQOYkHCc8YCFA	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-30T02:06:49.636717+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	sakfZyVEQpzdOw	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-27T02:06:15.328195+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	TQjmZzZ1vCPPSg	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-04T02:05:41.089918+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	Mnwx7eOe88pacA	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-02T17:48:35.584890+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	yKhagjOlNEuQNw	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. start_date — extracted_at 2026-03-03T02:05:33.738123+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	ZQ6D+7Mzd3HI5g	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-25T18:05:34.605558+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	2sH+DdODXQ0HyA	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-24T18:05:26.149834+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	ePsW0SUT20mQIA	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-23T18:05:43.390992+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	93e5AHAaPaFaPQ	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Justin contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-23T06:06:03.332920+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	fujW5YyaLSonGg	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-24T02:05:46.754340+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	CXPYYo28Iti7Og	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-04-03T02:05:36.910130+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	tOJigNwRA1qmPw	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-19T03:11:16.543224+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	fdVINZtl64+rCw	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-20T06:05:01.455219+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	3fvcnjAzJwnRsQ	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-20T00:04:34.356036+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	uVmQ0NPuyDbOGw	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-20T12:05:07.545753+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	BDY7vOXSKuW95w	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-24T06:05:01.277544+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	z5P/h4SK2eyrzQ	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-26T18:05:03.336012+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	ntnzD3lvCYBSOQ	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-04-02T02:05:59.384041+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	MWLmSf2EkALpyA	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-05T00:04:32.464134+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	9JlkN72pXmavZQ	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-26T12:05:21.227853+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	Fbpwo0TZUvpEYA	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Justin contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-24T12:05:01.145561+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	nwh6bQ5nXw4WOw	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-19T03:09:09.175197+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	+RFTnxguISJ/iA	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-19T06:05:23.388691+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	t4/qAVPWvsyZnQ	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-20T02:05:55.881101+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	LJhjIcaSD63u2w	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-25T00:04:46.529393+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	Nj2HXLiM8FZpfg	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-19T21:22:02.315258+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	CEvCnPN8xnpjkA	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-24T02:05:50.867928+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	vXiUvL+aVnNeIg	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-04-06T02:05:51.011064+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	FRggP08MI6mT4w	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-04-10T02:06:10.962919+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	1OwiUVU1QHC9uQ	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-04-11T02:05:21.775359+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	CPD8+npiTlxUaA	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-04-12T02:04:49.036502+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	Bux06oZnS3wg0Q	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-04-13T02:05:40.567090+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	+eVUZKO6U15XSA	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-04-14T02:05:45.398238+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	hdMUjta1gV8Fvw	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-04-09T02:05:22.011629+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	LUe9rsYh/m1+ZA	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-21T02:05:32.022017+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	sNzDf86HEkYr7Q	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-06T12:05:08.277334+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	4toqb5zbWCouSg	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-04T18:05:30.900609+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	h6CUt1pbP1666Q	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-04T12:05:04.070387+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	15dVTtBpzFUC2Q	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-25T06:05:21.553882+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	1GUfwD+LbbQ7Ew	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-19T18:05:17.856404+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	btejC6CVHQkWsQ	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-21T18:04:59.601867+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	68ZSTcBw5/O17g	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-23T02:05:27.816053+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	E5F448GY4br3bQ	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-02-23T12:05:00.901300+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	DYZbqVb4gGEpyQ	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-05T02:05:26.173164+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	oWvva3tx1jrU3g	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-19T15:17:04.431250+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	VQCUxaqRqqfQIA	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-20T02:05:37.681922+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	EAI2rT3t1q49rA	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-04-07T02:06:17.645075+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	Jz1NRCBsBYquVw	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-04-04T02:06:14.665426+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	QqMxq1LDsuu38Q	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-04-01T02:06:51.574013+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	kmyC1BSwzIbW+Q	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-28T02:06:23.216849+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	6evqy525gbs5bQ	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-21T02:05:56.391252+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	KPWI+tzxTa+NmQ	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-06T06:04:48.634530+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	nEcQ4wKu4EqtaA	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-06T02:05:21.202595+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	3/T1PC3Fl3n4SQ	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-04T00:05:09.988000+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	gqq8Q3vpEoDo5Q	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person Mitch contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-03T12:03:55.492970+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —
	moreland_contracts	HVsoDpOm2keOGw	2025 Strategy	0.80	fuzzy+embedding	Active
Source Record bronze_moreland_contracts_ma_project_contracts file_hash 43ce1f1aaf61561a261faccd71f3f027 file_name RiskLD 2025.docx file_path https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B9D7C4FC5-6115-49CF-AB2E-3AC5AF7D42FC%7D&file=RiskLD%202025.docx&action=default&mobileredirect=true company RiskLD project_name 2025 Strategy contact_person — contract_type time_and_materials hourly_rate — estimated_hours 350.0 total_fee_estimate — brief_project_description Implementation and maintenance of multiple systems including Hackensack and BJC, along with support and enhancements to software version control and quality control processes. start_date — extracted_at 2026-03-03T06:04:34.467535+00:00 raw_text_preview RiskLD and Moreland 2025 Strategy Item 1: New 2025 rollouts Throughout 2025, RiskLD anticipates completion and maintenance of Hackensack and BJC along with the implementation of Temple and two to four other systems. Moreland will modify its team structure to support this growth activity. Create dedicated implementation teams for each 4-6 week rollout. Mitch + 0.5 developer TBD lead + 0.5 developer Justin to oversee all rollout efforts with less day-to-day engagement Manage the transition from implementation to Turbo Team Support Estimated effort per implementation is 350 hours Item 2: Support/SLA Satisfaction The RiskLD contracts include support and service level agreements. Many of the items are software-related and supported by the Moreland team. Moreland will use the Turbo Team support group to triage, complete, or assign trouble tickets. Moreland will communicate contract requirements to the Moreland Turbo Team and will create necessary 24x7 support staffing. Moreland will implement Bold Desk or Zendesk with the four severity levels and automated responses required by the SLAs Moreland will provide support statistics to the RiskLD team after the close of each week. Item 3: Version Control RiskLD has asked Moreland to make improvements to software version control to maintain a single version of the RiskLD software while affording each system to apply system-specific configurations. Each hospital within a system is expected to run in the same way. Moreland will develop a cloud-hosted central system that contains all hospital configuration data and apply modifications to the RiskLD system to reference the configurations The configurations anticipated include SQL based alerts, changes to checklist, changes to thresholds The cloud configuration will be white-listed to ensure access only from RiskLD Moreland will commit to completing an estimate and plan by early January and to build the configuration platform (without main system integration) by the end file_created_at 2025-02-26T02:12:36+00:00 file_modified_at 2025-02-26T02:12:36+00:00 created_by Jeff Kavlick modified_by Jeff Kavlick _dlt_meta —

Moreland 2025 Strategy

Source Mappings (91)

Reassign Source Record

Add Source Mapping