Facilities API V2 post_api data with new Service location fields

[omahane]

User Story or Problem Statement

As a consumer of the Facilities data, I need to know about Service delivery options and which appointment text belongs with a given service now that each service location can have its data for these fields.

Context

Previously, the VAMC Facility Health Service delivery options and appointment instructions were not explicitly described at the Service location level.

Per this Slack conversation from 29 Jan 2024, because the Facility Locator is the only consumer of this data and there are no immediate plans to show any of this data in the Facility Locator, this is not a blocker to getting VBA pilot out.

Questions

When can Lighthouse work on incorporating these fields? Confirmed that this is V2.

Acceptance Criteria

• [ ] The data model for the added data is created
• [ ] Lighthouse approves the changed data model
• [ ] Office visits data are in the post_api payload for a Service location
• [ ] Virtual support data are in the post_api payload for a Service location
• [ ] Appointment text is in the post_api payload for a Service location
• [ ] Requires Content Model Documentation

Implementation steps

Changes will need to be made here: docroot/modules/custom/va_gov_post_api/src/Service/PostFacilityServiceVamc.php

Design principles

Veteran-centered

• [x] Single source of truth: Increase reliability and consistency of content on VA.gov by providing a single source of truth.
• [ ] Accessible, plain language: Provide guardrails and guidelines to ensure content quality.
• [ ] Purposely structured content: Ensure Content API can deliver content whose meaning matches its structure.
• [ ] Content lifecycle governance: Produce tools, processes and policies to maintain content quality throughout its lifecycle.

Editor-centered

• [ ] Purpose-driven: Create an opportunity to involve the editor community in VA’s mission and content strategy goals.
• [ ] Efficient: Remove distractions and create clear, straightforward paths to get the job done.
• [ ] Approachable: Offer friendly guidance over authoritative instruction.
• [x] Consistent: Reduce user’s mental load by allowing them to fall back on pattern recognition to complete tasks.
• [ ] Empowering: Provide clear information to help editors make decisions about their work.

Team

Please check the team(s) that will do this work.

• [ ] CMS Team
• [ ] Public Websites
• [x] Facilities
• [ ] User support

[xiongjaneg]

@omahane @swirtSJW If this needs to be done in next sprint along with the other related tickets, please refine and size and I'll get it on the sprint plan. Thank you!

[xiongjaneg]

Hey team! Please add your planning poker estimate with Zenhub @swirtSJW @omahane

[xiongjaneg]

We can start to get agreement on the data model sooner. This could potentially be broken into separate tickets (agreement and planning could come first).

[xiongjaneg]

@xiongjaneg Bring to next Lighthouse sync for more info on timing.

[xiongjaneg]

Blocked on Lighthouse capacity

[davidmpickett]

Moving to National Rollout epic as this is not blocking for Staging Review