Initial commit with dummy content

Author: vigneshhari

.github/workflows/deploy.yml

@@ -0,0 +1,42 @@
+name: Deploy to GitHub Pages
+
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  build:
+    name: Build Docusaurus
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 20
+          cache: npm
+      - name: Install dependencies
+        run: npm ci
+      - name: Build website
+        run: npm run build
+      - name: Upload Build Artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: build
+
+  deploy:
+    name: Deploy to GitHub Pages
+    needs: build
+    permissions:
+      pages: write
+      id-token: write
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

.github/workflows/test-deploy.yml

@@ -0,0 +1,23 @@
+name: Test deployment
+
+on:
+  pull_request:
+    branches:
+      - main
+
+jobs:
+  test-deploy:
+    name: Test deployment
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 20
+          cache: npm
+      - name: Install dependencies
+        run: npm ci
+      - name: Test build website
+        run: npm run build

.gitignore

@@ -0,0 +1,20 @@
+# Dependencies
+/node_modules
+
+# Production
+/build
+
+# Generated files
+.docusaurus
+.cache-loader
+
+# Misc
+.DS_Store
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*

README.md

@@ -0,0 +1,41 @@
+# Website
+
+This website is built using [Docusaurus](https://docusaurus.io/), a modern static website generator.
+
+## Installation
+
+```bash
+yarn
+```
+
+## Local Development
+
+```bash
+yarn start
+```
+
+This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
+
+## Build
+
+```bash
+yarn build
+```
+
+This command generates static content into the `build` directory and can be served using any static contents hosting service.
+
+## Deployment
+
+Using SSH:
+
+```bash
+USE_SSH=true yarn deploy
+```
+
+Not using SSH:
+
+```bash
+GIT_USER=<Your GitHub username> yarn deploy
+```
+
+If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the `gh-pages` branch.

blog/authors.yml

@@ -0,0 +1,9 @@
+vigneshhari:
+  name: Vignesh Hari
+  title: Engineer @ OHC
+  url: https://linkedin.com/in/vigneshhari
+  image_url: https://github.com/vigneshhari
+  page: true
+  socials:
+    linkedin: vigneshhari
+    github: vigneshhari

blog/tags.yml

@@ -0,0 +1,4 @@
+productdoc:
+  label: Product Documentation
+  permalink: /product
+  description: Product Documentation

concepts/_category_.json

@@ -0,0 +1,9 @@
+{
+  "label": "Concepts",
+  "position": 2,
+  "link": {
+    "type": "generated-index",
+    "title": "Concepts",
+    "description": "Understand what things are in Care. Each concept answers a \"What is…?\" question about the platform, its data model, or clinical primitives."
+  }
+}

concepts/clinical/_category_.json

@@ -0,0 +1,4 @@
+{
+  "label": "Clinical",
+  "position": 1
+}

concepts/clinical/patient.mdx

@@ -0,0 +1,54 @@
+---
+sidebar_position: 1
+---
+
+# Patient
+
+A **patient** in Care is a person who receives care through your facility or program. It is the longitudinal anchor for clinical documentation — every encounter, observation, order, and care plan links back to a patient record.
+
+## What it represents
+
+In Care's FHIR-aligned model, a patient maps to the **Patient** resource. It holds:
+
+- **Identity** — name, date of birth, sex, photo, and government or facility identifiers
+- **Contact** — phone, address, and emergency contacts
+- **Administrative context** — registration status, facility association, and tags used by your deployment
+- **Clinical linkage** — references to encounters, conditions, allergies, and other resources in the record
+
+A patient is not the same as a single visit. One patient can have many encounters over time; the patient record is the container that makes that history coherent.
+
+## Identifiers
+
+Patients are located using one or more identifiers, depending on how your deployment is configured:
+
+| Identifier type | Typical use |
+| --- | --- |
+| Facility MRN | Primary key inside a hospital or clinic |
+| National health ID | ABDM, ABHA, or other national rails |
+| Program ID | Public health or campaign-specific registries |
+
+Identifiers must be unique within the scope your administrator defines. Duplicate detection during registration uses these fields.
+
+## Lifecycle
+
+```
+Register → Active → (optional) Inactive / Deceased
+```
+
+- **Register** — a patient record is created with minimum demographics
+- **Active** — the record is used for encounters and orders
+- **Inactive** — retained for history but hidden from routine search (configurable)
+- **Deceased** — administrative closure; clinical history remains auditable
+
+## Permissions
+
+Who can view or edit patient demographics is controlled by role-based access. Clinical staff typically can read full records; registration staff can create and update demographics; some fields may be restricted by facility or ward.
+
+## Related
+
+- Flow: [Create a patient](../../flows/clinical/create-patient.mdx)
+- Playbook: [Outpatient registration](/deployments/hmis/playbooks/outpatient-registration) (HMIS)
+
+## FHIR reference
+
+Care exposes patients through FHIR R5 `Patient` resources. See your deployment's API base URL for `GET /Patient` and `POST /Patient` when integrating externally.

deployments/hmis/intro.mdx

@@ -0,0 +1,18 @@
+---
+sidebar_position: 1
+slug: /
+---
+
+# HMIS playbooks
+
+Hospital management playbooks wire **flows** into real front-desk and ward scenarios. Each playbook lists the flows involved, the expected operator path, and edge cases specific to HMIS deployments.
+
+## How playbooks relate to core docs
+
+| Layer | Location | Example |
+| --- | --- | --- |
+| Concept | [Core docs](/docs/concepts/clinical/patient) | What is a patient? |
+| Flow | [Core docs](/docs/flows/clinical/create-patient) | How do I create a patient? |
+| Playbook | Here | Outpatient registration with duplicates and walk-ins |
+
+Start from the [documentation home](/docs/intro) if you are new to this structure.