bms-session-plugin 1.0.4 → 1.0.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +1 -1
- package/skills/bms-session/SKILL.md +14 -0
package/package.json
CHANGED
|
@@ -29,6 +29,20 @@ Always use `LIMIT` to avoid returning excessive rows. Always use the `pattern` p
|
|
|
29
29
|
|
|
30
30
|
When the user asks to "analyze the database", "show patient data", "query hospital data", or similar — start working immediately by calling the MCP tools. Do not ask unnecessary questions. Use list_tables and describe_table to discover the schema, then write and execute queries.
|
|
31
31
|
|
|
32
|
+
## How Applications Receive bms-session-id
|
|
33
|
+
|
|
34
|
+
HOSxP passes the session ID to destination applications via **URL parameter**:
|
|
35
|
+
|
|
36
|
+
```
|
|
37
|
+
https://your-app.com/?bms-session-id=CB411DB0-B121-43C6-B795-80ADECE6A13C
|
|
38
|
+
```
|
|
39
|
+
|
|
40
|
+
When building apps that integrate with HOSxP:
|
|
41
|
+
- Accept `bms-session-id` from the URL query string
|
|
42
|
+
- The session ID is dynamic — it changes per user and per session
|
|
43
|
+
- After first successful validation, optionally store in a cookie (7-day expiry) for convenience
|
|
44
|
+
- Always validate the session before using it — sessions expire (default 10 hours)
|
|
45
|
+
|
|
32
46
|
## When MCP Server Is Not Available
|
|
33
47
|
|
|
34
48
|
Build queries using the REST API directly. The flow:
|