This ICP smart contract allows Patient to manage access to their medical History to doctors and hospitals. It manages doctors and their assignments to hospitals, and patient-doctor interactions. It has functions to update patient history and assign patients to doctors. The error handling is expanded to cover unauthorized access and payload validation issues. The Candid interface is updated to reflect the changes in functionality.

• Attributes:
  • id, name, password, hospital_id, patient_ids.
• Represents information about a doctor involved in the blood donation drive.

• Attributes:
  • doctor_id, patient_id, doctor_password, new_history.
• Represents a payload structure for updating a patient's medical history.

• Attributes:
  • name, doctor_id, hospital_id, doctor_password, hospital_password.
• Represents a payload structure for editing doctor attributes.

• Attributes:
  • name, hospital_id, password, hospital_password.
• Represents a payload structure for adding a new doctor.

• Introduces a new DOCTOR_STORAGE using StableBTreeMap to store doctor-related information.

• Assigns a patient to a doctor and adds the patient to the doctor's hospital.

• Updates a patient's medical history by a doctor.

• Adds a new doctor to the system.

• Helper function to add a doctor to a hospital.

• Edits doctor attributes and assigns the doctor to a hospital.

• Retrieves a doctor by ID.

• Retrieves patient information by patient ID and doctor password.

• Helper function to add a doctor to storage.

• Helper function to add a patient to a hospital.

• Extends the Error enum with new variants (AlreadyInit, Unauthorized).

• Exports the Candid interface for seamless interaction with the Internet Computer.

To learn more before you start working with patient_records, see the following documentation available online:

• Quick Start
• SDK Developer Tools
• Rust Canister Devlopment Guide
• ic-cdk
• ic-cdk-macros
• Candid Introduction
• JavaScript API Reference

If you want to start working on your project right away, you might want to try the following commands:

cd patient_records/
dfx help
dfx canister --help

If you want to test your project locally, you can use the following commands:

# Starts the replica, running in the background
dfx start --background

# Deploys your canisters to the replica and generates your candid interface
dfx deploy

Once the job completes, your application will be available at http://localhost:4943?canisterId={asset_canister_id}.

If you have made changes to your backend canister, you can generate a new candid interface with

npm run generate

at any time. This is recommended before starting the frontend development server, and will be run automatically any time you run dfx deploy.

If you are making frontend changes, you can start a development server with

npm start

Which will start a server at http://localhost:8080, proxying API requests to the replica at port 4943.

If you are hosting frontend code somewhere without using DFX, you may need to make one of the following adjustments to ensure your project does not fetch the root key in production:

• setDFX_NETWORK to production if you are using Webpack
• use your own preferred method to replace process.env.DFX_NETWORK in the autogenerated declarations
  • Setting canisters -> {asset_canister_id} -> declarations -> env_override to a string in dfx.json will replace process.env.DFX_NETWORK with the string in the autogenerated declarations
• Write your own createActor constructor