Patient Assignment List Project

Managed AssignmentList with Time-based and Filter-based Population Criterion

patient-list-app AssignmentListView

The patient-list-app is the operations console for the Configurable Patient Visit List. It lets users kick off background jobs that affect lists (refresh, recompute membership, export), observe job status, and open the Visit List UI directly with a given list context. It is not the renderer itself; instead, it drives/coordinates the Backbone VisitList screen by sending users to the route with the correct listId and by emitting audit and metrics events.

Technologies Used

Specifications

Stabilize contracts for UI while the domain/DAO layer evolves.

patient-list-war: Backbone/Handlebars UI (AssignmentListView, VisitListView, routers, templates).
patient-list-rest: Spring MVC controllers exposing versioned REST endpoints that accept/return patient-list-api DTOs only.
patient-list-api: Facade interfaces + DTOs (AssignmentListDto, VisitDto, PagingDto, FilterDto).
patient-list-services: Facade implementations, mapping between DTOs and domain entities, validation, transactions, caching.
patient-list-dao: Repositories/queries; isolates persistence (SQL/ORM).

UI (war) → REST (rest) ↔ DTO (api) → Facade (services) → Repository (dao) → DB.

Additive DTOs with /api/v1/* routes, deprecation windows, and mappers contained in services so UI is insulated.

AuthN/Z enforced in patient-list-rest and re-checked inside Facade using user/org scope for list/assignment access.

Render an Assignment List that nests/embeds a VisitList inside the AssignmentListView (e.g., by assignee/role/queue).

Client model mirroring AssignmentListDto (id, name, criteria, owner, counts).

/api/v1/assignmentLists

Returns array of AssignmentModel and paging.

Client model mirroring VisitDto for row rendering.

/api/v1/visits

Extracts items[] and paging.

listId (assignment list), assigneeId/role, page, pageSize, sort, filters

Backbone.Model storing route-bound state (assignmentListId, assignee, page, sort, filters) with toQuery().

Container view that manages assignee tabs/queues and owns one VisitCollection per active context; listens to collection events to show spinners/empty/error and composes VisitListView as a subview.

Subview that renders table rows for the currently selected assignee/segment using VisitCollection.

Shared toolbar for search, filters, bulk actions; emits 'filter:changed', 'action:*'.

Controls page changes; updates AssignmentState and triggers fetch.

Multi-step builder for creating/editing assignment lists; on save, routes back to the AssignmentListView with new listId.

Routes '#/assignments/:id?assignee=RN1&page=1&sort=admitTime,desc&filters=...' to instantiate AssignmentListView with AssignmentState and VisitCollection seeded from query.

AssignmentRouter → AssignmentListView.initialize() → active VisitCollection.fetch({data: state.toQuery()}) → REST returns VisitDto[] + paging → collection.reset(items) → VisitListView.render() (row subviews) → Handlebars templates produce the table inside the AssignmentListView region.

patient-list-war bundles Backbone modules and Handlebars templates; cache-busted filenames. pk-common-ui provides shared widgets.

Server-side pagination/sort/filter, tuned DAO queries to avoid N+1, ETag/If-None-Match, gzip/brotli, client-side debounce on filter/search.

Controller timeouts, service retries for transient DB faults, idempotent prompt job endpoints.

UI emits audit events (assignee switch, filter change, export) to /audit; services log timing and cache hit/miss.

Block Diagram

graph TD;
  WAR[patient-list-war\
Backbone/Handlebars UI] --> REST[patient-list-rest\
Spring Controllers];
  REST --> API[patient-list-api\
Facade + DTOs];
  API <--implements--> SRV[patient-list-services\
Business Logic, Mapping, Validation];
  SRV --> DAO[patient-list-dao\
Repositories/Queries];
  DAO --> DB[(Database)];
  WAR -. static assets .-> ASSETS[Templates JS CSS];

graph TD; WAR[patient-list-war\ Backbone/Handlebars UI] --> REST[patient-list-rest\ Spring Controllers]; REST --> API[patient-list-api\ Facade + DTOs]; API <--implements--> SRV[patient-list-services\ Business Logic, Mapping, Validation]; SRV --> DAO[patient-list-dao\ Repositories/Queries]; DAO --> DB[(Database)]; WAR -. static assets .-> ASSETS[Templates JS CSS];

Component Diagram

graph TD;
  subgraph UI patient-list-war
    AR[AssignmentRouter]
    AS[AssignmentState]
    ALV[AssignmentListView]
    VCOL[VisitCollection]
    VLV[VisitListView]
    TBV[ToolbarView]
    PGR[PaginationView]
    WIZ[WizardView]
    TLIST[assignment-list.hbs]
    TROW[visit-row.hbs]
  end
  subgraph REST/API
    EPV[/GET /api/v1/visits/]
    EPA[/GET /api/v1/assignmentLists/id/summary/]
    DTOv[VisitDto]
    DTOa[AssignmentListDto]
  end
  subgraph Server
    CtlV[VisitController]
    CtlA[AssignmentController]
    Fac[PatientListFacade]
    Svc[Facade Impl]
    Map[DTO Mappers]
    RepoV[VisitRepository]
    RepoA[AssignmentRepository]
    DB[(DB)]
  end
  AR --> AS
  AR --> ALV
  ALV --> TBV
  ALV --> PGR
  ALV --> VCOL
  ALV -->|subview| VLV
  VCOL -->|reset/sync| VLV
  ALV --> TLIST
  VLV --> TROW
  TBV -->|filter:changed| AS
  PGR -->|page:changed| AS
  AS -->|toQuery| VCOL
  VCOL -->|fetch| EPV
  EPV --> CtlV --> Fac --> Svc --> RepoV --> DB
  RepoV --> Svc --> Map --> DTOv --> CtlV --> EPV --> VCOL
  ALV -->|load summary| EPA --> CtlA --> Fac --> RepoA --> DB
  WIZ -->|save list| CtlA

graph TD; subgraph UI patient-list-war AR[AssignmentRouter] AS[AssignmentState] ALV[AssignmentListView] VCOL[VisitCollection] VLV[VisitListView] TBV[ToolbarView] PGR[PaginationView] WIZ[WizardView] TLIST[assignment-list.hbs] TROW[visit-row.hbs] end subgraph REST/API EPV[/GET /api/v1/visits/] EPA[/GET /api/v1/assignmentLists/id/summary/] DTOv[VisitDto] DTOa[AssignmentListDto] end subgraph Server CtlV[VisitController] CtlA[AssignmentController] Fac[PatientListFacade] Svc[Facade Impl] Map[DTO Mappers] RepoV[VisitRepository] RepoA[AssignmentRepository] DB[(DB)] end AR --> AS AR --> ALV ALV --> TBV ALV --> PGR ALV --> VCOL ALV -->|subview| VLV VCOL -->|reset/sync| VLV ALV --> TLIST VLV --> TROW TBV -->|filter:changed| AS PGR -->|page:changed| AS AS -->|toQuery| VCOL VCOL -->|fetch| EPV EPV --> CtlV --> Fac --> Svc --> RepoV --> DB RepoV --> Svc --> Map --> DTOv --> CtlV --> EPV --> VCOL ALV -->|load summary| EPA --> CtlA --> Fac --> RepoA --> DB WIZ -->|save list| CtlA

Sequence Diagram

sequenceDiagram
  participant U as User
  participant R as AssignmentRouter
  participant S as AssignmentState
  participant A as AssignmentListView
  participant VC as VisitCollection
  participant V as VisitListView
  participant T as ToolbarView
  participant REST as /api/v1/visits
  participant CTR as VisitController
  participant FAC as Facade(Service)
  participant DAO as VisitRepository
  participant DB as Database

  U->>R: Navigate #/assignments/42?assignee=RN1&page=1
  R->>S: Initialize state (listId=42, assignee=RN1, page=1, sort, filters)
  R->>A: new AssignmentListView({state:S})
  A->>VC: fetch({ data: S.toQuery() })
  VC->>REST: GET /api/v1/visits?listId=42&assignee=RN1&page=1&sort=...
  REST->>CTR: Dispatch
  CTR->>FAC: findVisitsForAssignment(listId,assignee,paging,filters)
  FAC->>DAO: query(listId,assignee,paging,filters)
  DAO->>DB: Execute SQL
  DB-->>DAO: rows
  DAO-->>FAC: entities
  FAC-->>CTR: List<VisitDto> + paging
  CTR-->>VC: 200 {items:[], paging:{}}
  VC-->>A: reset/sync events
  A->>V: render subview with VC
  V->>V: render rows using Handlebars (visit-row.hbs)
  A-->>U: Assignment list with visits displayed
  U->>T: Change filter/search/assignee
  T-->>S: filter:changed / assignee:changed
  S-->>A: change:*
  A->>VC: fetch() (debounced) with new query
  VC->>REST: GET /api/v1/visits?... (repeat)

sequenceDiagram participant U as User participant R as AssignmentRouter participant S as AssignmentState participant A as AssignmentListView participant VC as VisitCollection participant V as VisitListView participant T as ToolbarView participant REST as /api/v1/visits participant CTR as VisitController participant FAC as Facade(Service) participant DAO as VisitRepository participant DB as Database U->>R: Navigate #/assignments/42?assignee=RN1&page=1 R->>S: Initialize state (listId=42, assignee=RN1, page=1, sort, filters) R->>A: new AssignmentListView({state:S}) A->>VC: fetch({ data: S.toQuery() }) VC->>REST: GET /api/v1/visits?listId=42&assignee=RN1&page=1&sort=... REST->>CTR: Dispatch CTR->>FAC: findVisitsForAssignment(listId,assignee,paging,filters) FAC->>DAO: query(listId,assignee,paging,filters) DAO->>DB: Execute SQL DB-->>DAO: rows DAO-->>FAC: entities FAC-->>CTR: List<VisitDto> + paging CTR-->>VC: 200 {items:[], paging:{}} VC-->>A: reset/sync events A->>V: render subview with VC V->>V: render rows using Handlebars (visit-row.hbs) A-->>U: Assignment list with visits displayed U->>T: Change filter/search/assignee T-->>S: filter:changed / assignee:changed S-->>A: change:* A->>VC: fetch() (debounced) with new query VC->>REST: GET /api/v1/visits?... (repeat)

Managed AssignmentList with Time-based and Filter-based Population Criterion

patient-list-app AssignmentListView

Technologies Used

Specifications

facadeArchitecture

goal

modules

flow

evolution

security

backboneAssignmentListFlow

intent

uiModelsAndCollections

AssignmentModel

AssignmentCollection

url

parse

VisitModel

VisitCollection

url

parse

queryParams

AssignmentState

views

AssignmentListView

VisitListView

ToolbarView

PaginationView

WizardView

router

AssignmentRouter

renderingPipeline

management

assets

performance

reliability

telemetry

Block Diagram

Component Diagram

Sequence Diagram