The first version of Care 3.0 will target at building the minimum required flow for an hospital to support an OP consultation.

graph LR
    A[Registration] --> B[Billing for Registration]
    B --> C[Consultation Request]
    C --> D[Token Issued]
    D --> E[Consultation Starts]
    D --> F[Vitals Recorded]
    F --> E
    E --> G[Service Requests]
    E --> H[Prescription Issued]
    E --> I[Inpatient Admission]

The minimum viable product will require the following features.

Basic EMR of a Patient in OP flow

The Patient Management system will have the following key element.

Patient Registration

  1. Basic details
  2. Social Profile

Patient Health Profile

  1. Past Medical History

    1. Diagnosis

      code: SNOMED CT code for the diagnosis

      description: Description of the diagnosis (derived from the code)

      date: Date of diagnosis

      status: Current status of the diagnosis (e.g., ongoing, resolved)

    2. Procedures

      code: SNOMED CT code for the procedure

      description: Description of the procedure (derived from the code)

      date: Date of the procedure

    3. Ongoing Medications

      code: SNOMED CT code for the medication

      description: Description of the medication (derived from the code)

      dosage: Dosage of the medication

      frequency: Frequency of administration

    # With SNOMED CT the object would possibly look like this. 
    {
      "diagnosis": [
        {
          "code": "38341003",
          "description": "Hypertension",
          "date": "2018-03-15",
          "status": "ongoing"
        }
      ],
      "procedures": [
        {
          "code": "80146002",
          "description": "Appendectomy",
          "date": "2016-08-10"
        }
      ],
      "ongoing_medication": [
        {
          "code": "389012000",
          "description": "Lisinopril",
          "dosage": "10mg",
          "frequency": "once daily"
        }
      ]
    }
    
  2. Health Information

Consultation

OP Setting

IP Setting