Patient List Project

Physician-Focused Patient-list with Time-based and Filter-based Population Criteria.

patient-list-app

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 UI contracts while allowing domain and DAO evolution.

patient-list-war: Backbone/Handlebars UI, routers, views, templates, static assets.
patient-list-rest: Spring Web controllers that only accept/return patient-list-api DTOs.
patient-list-api: Facade interfaces and DTOs (VisitDto, VisitListDto, PagingDto, FilterDto).
patient-list-services: Implements the Facade; mapping between DTOs and domain; validation; transactions; caching.
patient-list-dao: Persistence repositories/queries; no API types leak upward.

UI (war) → REST controller (rest) ↔ DTOs (api) → Facade service (services) → Repository (dao) → DB.

DTO↔Domain mapping occurs only inside patient-list-services via MapStruct or manual mappers.

Additive DTO changes with versioned REST routes (/api/v1/*), deprecations flagged in Facade; UI remains stable.

Client-side model mirroring VisitDto fields used by the UI (id, mrn, name, admitTime, location, provider, status, flags).

/api/v1/visits

Extracts array and paging metadata from {items:[], paging:{...}}.

Supports query params for listId, search, filters, sort, page, pageSize.

Backbone.Model that stores route-bound state (listId, page, sort, filters); converts to query string with toQuery().

Owns lifecycle and layout; listens to VisitCollection events 'request','sync','reset','error' to toggle spinner, render rows, show empty/error.

Renders a single visit row; rerenders on model change.

Search box, filter chips, bulk actions; emits 'filter:changed', 'search:typed', 'action:export'.

Changes page → updates VisitListState → triggers fetch.

Multi-step builder/manager for patient lists; saves via /api/v1/visitLists and then routes to VisitList with the new listId.

Routes '#/visits?listId=123&page=1&sort=admitTime,desc&filters=...' to instantiate VisitListView with a VisitCollection and VisitListState seeded from the query.

VisitRouter → VisitListView.initialize() → collection.fetch({data: state.toQuery()}) → REST returns VisitDto[] + paging → collection.reset(items) → VisitListView.render() → for each model new VisitItemView({model}).render() → Handlebars templates produce the table.

patient-list-war bundles Backbone modules, templates (.hbs), and pk-common-ui widgets; versioned static paths to enable long-lived caching with cache-busting.

Spring Security in patient-list-rest validates JWT/session; per-list authorization enforced in Facade based on user/org/role.

Controller timeouts, service-level retries for transient DB faults, idempotent job endpoints for PromptJob.

Server-side pagination/sort/filter, DAO query tuning (indexes, joins to avoid N+1), HTTP caching with ETag/If-None-Match, compressed assets.

UI emits audit events (route, filter change, export) to /audit; services log query timings; PromptJob publishes progress to a job-status endpoint.

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)
    Router[VisitRouter]
    State[VisitListState]
    Coll[VisitCollection]
    ListView[VisitListView]
    ItemView[VisitItemView]
    Toolbar[ToolbarView]
    Pager[PaginationView]
    Wizard[WizardView]
    TList[visit-list.hbs]
    TRow[visit-row.hbs]
  end
  subgraph REST/API
    EP[/GET /api/v1/visits/]
    EPlist[/GET /api/v1/visitLists/{id}/visits/]
    DTO[VisitDto]
  end
  subgraph Server
    Ctl[VisitController]
    Fac[VisitFacade]
    Svc[VisitServiceImpl]
    Map[VisitMapper]
    Repo[VisitRepository]
    DB[(DB)]
  end
  Router --> ListView
  Router --> State
  ListView --> Toolbar
  ListView --> Pager
  ListView --> Coll
  Coll -->|reset/sync| ListView
  ListView -->|each model| ItemView
  ListView --> TList
  ItemView --> TRow
  Toolbar -->|filter:changed| State
  Pager -->|page:changed| State
  State -->|toQuery()| Coll
  Coll -->|fetch| EP
  EP --> Ctl --> Fac --> Svc --> Repo --> DB
  Repo --> Svc --> Map --> DTO --> Ctl --> EP --> Coll
  Wizard -->|save list| Ctl

graph TD; subgraph UI (patient-list-war) Router[VisitRouter] State[VisitListState] Coll[VisitCollection] ListView[VisitListView] ItemView[VisitItemView] Toolbar[ToolbarView] Pager[PaginationView] Wizard[WizardView] TList[visit-list.hbs] TRow[visit-row.hbs] end subgraph REST/API EP[/GET /api/v1/visits/] EPlist[/GET /api/v1/visitLists/{id}/visits/] DTO[VisitDto] end subgraph Server Ctl[VisitController] Fac[VisitFacade] Svc[VisitServiceImpl] Map[VisitMapper] Repo[VisitRepository] DB[(DB)] end Router --> ListView Router --> State ListView --> Toolbar ListView --> Pager ListView --> Coll Coll -->|reset/sync| ListView ListView -->|each model| ItemView ListView --> TList ItemView --> TRow Toolbar -->|filter:changed| State Pager -->|page:changed| State State -->|toQuery()| Coll Coll -->|fetch| EP EP --> Ctl --> Fac --> Svc --> Repo --> DB Repo --> Svc --> Map --> DTO --> Ctl --> EP --> Coll Wizard -->|save list| Ctl

Sequence Diagram

sequenceDiagram
  participant U as User
  participant R as VisitRouter
  participant V as VisitListView
  participant S as VisitListState
  participant C as VisitCollection
  participant T as ToolbarView
  participant H as Handlebars Templates
  participant REST as /api/v1/visits
  participant CTR as VisitController
  participant FAC as VisitFacade(Service)
  participant DAO as VisitRepository
  participant DB as Database

  U->>R: Navigate #/visits?listId=123&page=1
  R->>S: create from query (listId,page,sort,filters)
  R->>V: new VisitListView({state:S, collection:C})
  V->>C: fetch({data: S.toQuery()})
  C->>REST: GET /api/v1/visits?listId=123&page=1&sort=...
  REST->>CTR: Dispatch controller
  CTR->>FAC: findVisits(listId,paging,filters)
  FAC->>DAO: query(listId,paging,filters)
  DAO->>DB: Execute SQL
  DB-->>DAO: rows
  DAO-->>FAC: entities
  FAC-->>CTR: List<VisitDto> + paging
  CTR-->>C: 200 JSON {items:[], paging:{}}
  C-->>V: reset/sync events
  V->>H: Render visit-list.hbs + visit-row.hbs
  H-->>V: HTML table
  V-->>U: Patient visit list displayed
  U->>T: Change filter/search
  T-->>S: event filter:changed
  S-->>V: change:*
  V->>C: fetch() (debounced) with new query
  C->>REST: GET /api/v1/visits?... (repeat)

sequenceDiagram participant U as User participant R as VisitRouter participant V as VisitListView participant S as VisitListState participant C as VisitCollection participant T as ToolbarView participant H as Handlebars Templates participant REST as /api/v1/visits participant CTR as VisitController participant FAC as VisitFacade(Service) participant DAO as VisitRepository participant DB as Database U->>R: Navigate #/visits?listId=123&page=1 R->>S: create from query (listId,page,sort,filters) R->>V: new VisitListView({state:S, collection:C}) V->>C: fetch({data: S.toQuery()}) C->>REST: GET /api/v1/visits?listId=123&page=1&sort=... REST->>CTR: Dispatch controller CTR->>FAC: findVisits(listId,paging,filters) FAC->>DAO: query(listId,paging,filters) DAO->>DB: Execute SQL DB-->>DAO: rows DAO-->>FAC: entities FAC-->>CTR: List<VisitDto> + paging CTR-->>C: 200 JSON {items:[], paging:{}} C-->>V: reset/sync events V->>H: Render visit-list.hbs + visit-row.hbs H-->>V: HTML table V-->>U: Patient visit list displayed U->>T: Change filter/search T-->>S: event filter:changed S-->>V: change:* V->>C: fetch() (debounced) with new query C->>REST: GET /api/v1/visits?... (repeat)

Physician-Focused Patient-list with Time-based and Filter-based Population Criteria.

patient-list-app

Technologies Used

Specifications

facadeArchitecture

purpose

modules

callFlow

mapping

evolution

backboneVisitListFlow

uiModelsAndCollections

VisitModel

VisitCollection

url

parse

behavior

VisitListState

views

VisitListView

VisitItemView

ToolbarView

PaginationView

WizardView

router

VisitRouter

renderingPipeline

managementOfPatientListApp

assets

security

reliability

performance

telemetry

Block Diagram

Component Diagram

Sequence Diagram