These guides map an industry's concepts onto the objects the platform has today (bouquets, lines, packages, partner accounts, nodes, the API). They are conceptual mappings, not industry-specific features, and a partner account is a delegated account, not an isolated tenant.
Conceptual mapping
Nothing in the panel is called a patient or a ward. The table says which object plays which role; the chapters below set them up in that order.
| In your industry | On the platform | Where in the panel |
|---|---|---|
| Ward line-up | Bouquet: a named set of channels, films or series that a package grants | Bouquets, from Streams and Movies / Series |
| Bed or ward television | Line: one access with its package, bouquets, expiry, connection limit and outputs | Lines → add, or activation codes, or the Reseller API |
| Television channel or information loop | Live channel: a stream with its sources, EPG and output formats | Streams → add a live stream (source URL or RTMP push) |
| Health-education and information videos | VOD catalogue: movies and series with seasons and episodes, categories and metadata | Movies and Series, or the VOD ingest job |
| Access period of a bed | Expiry date of the line, renewed by a package, a credit or the API | The line's expiry date and the package's duration |
| Wing or building node | Streaming nodes: edge servers enrolled from the panel, one per site or building | Servers → add a node, installed over SSH |
| Screens per bed | Max connections of the line: how many devices may watch at once | The line's max connections |
Prerequisites
What to have before installing.
- A server in the hospital data room (Ubuntu 22.04 or 24.04), the installer, and an internal address the bedside and ward televisions can reach.
- The channel feeds the hospital holds rights to, the hospital's information and health-education videos, and the screens (Android TV boxes, MAG or Enigma2 boxes, smart TVs with a player app or a browser).
- A decision on who administers the panel (typically the IT team), how beds and wards are named, and the line-up of each ward type.
Infrastructure deployment
The central server, then a node per wing.
- Run the installer on the central server and set the playback base to the hospital's internal address, so the screens stay on the local network.
- Set the licence key on the server; with no internet on the site, activate it offline on the local network.
- Enrol a node per wing or building from Servers; the panel installs it over SSH and routes that wing's screens to it.
- Create a partner account (reseller) for the IT team of a department, or for a ward administrator, if their work should be separate from the central administrator.
Content organisation
Line-ups per ward, one information bouquet.
- Create one bouquet per line-up (general ward, long-stay rooms, paediatrics) from the licensed channels.
- Create a bouquet of the hospital's information and health-education videos and add it to every package.
- Create one package per ward type with the bouquets it grants and a long duration as the access period, so a bed does not expire between patients.
- Order the channels and give them logos so the menu on the bedside screen reads well.
Partner (reseller) configuration
Usually the IT team alone.
- A single hospital runs the panel with its administrator account; no partner account is needed to switch a bed on.
- Add a partner account with a limited permission group when a ward manager or a department should manage its own screens' lines.
- A hospital group with several sites gets one partner account per site, each with its own lines; it is a delegated account, not an isolated installation.
Bed and ward line configuration
One line per bed or ward television.
- Create one line per screen under Lines → add, named by the bed or ward (for example Ward 4 bed 12), with the ward type's package.
- Set max connections to 1 for a bedside screen, or to the number of screens in a shared room.
- Bind the line to the television's address when the network gives screens fixed addresses.
- Configure the screen once with the line's credentials (Xtream Codes API or M3U, or the MAG / Enigma2 portal); the credentials stay with the bed, so a new patient needs no setup.
Information and health-education videos
The hospital's own library.
- Upload welcome, ward rules and health-education films as movies, and multi-part programmes as series, with a short description and a category per topic.
- Put them in the information bouquet so every ward type receives them.
- Replace a video in the panel when the information changes; the screens see the new version at once.
Television channels and the information loop
Live channels for the wards.
- Add each licensed channel under Streams with its feed; add an EPG source so the guide on the screen shows the programmes.
- For a notice channel, add a looping live stream fed by an encoder in the hospital and put it in the information bouquet.
- Keep channels the hospital may show only in some wards in bouquets that only those wards' packages grant.
Access and expiry
The bed stays on.
- Give a bed's line a long expiry and renew it with its package when it runs low; a bed should not go dark between two patients.
- Disable the line of a bed or a wing that is closed, and enable it again when it reopens.
- Subscribe an internal system to the webhooks if it should know about expiring and disabled lines.
Integration with other systems
Hospital IT drives lines; the panel plays video.
- The panel has no native integration with hospital systems; there is no nurse call, patient record or EHR connection.
- A system of the hospital's own can create, renew, enable and disable lines through the Reseller API with a key and a request id, and receive webhooks on changes.
- There is no single sign-on for viewers; a screen plays with the credentials of its line.
Security considerations
The platform stays inside the building.
- Keep the playback base and the nodes on the hospital network; put the panel behind the reverse proxy with TLS and set TRUSTED_PROXIES so the audit log sees real addresses.
- Two-factor sign-in for every panel account and permission groups, so a ward manager sees only what the role needs.
- Signed and expiring playback links, a connection limit of one per bedside line, and address binding where screens have fixed addresses.
- Encrypted database backups with an off-site copy, and the audit log for every change of lines and catalogue; the panel holds no patient data.
Troubleshooting
The usual first checks.
- A bed has no television: check that its line is enabled and not expired, then the screen's credentials and address.
- A channel is missing on one ward: check the bouquets of that ward type's package.
- A wing buffers: check the wing node's heartbeat and that its screens are routed to it.
- Television stops during an internet outage: check that the playback base and the sources are internal addresses; external feeds depend on the uplink.