Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Abdm M3 #6487

Closed
wants to merge 34 commits into from
Closed

Abdm M3 #6487

wants to merge 34 commits into from

Conversation

khavinshankar
Copy link
Member

@khavinshankar khavinshankar commented Oct 25, 2023

https://drive.google.com/file/d/1UVWtAnLy7RNVO4rZIawQZz9jWyMg53SX/view?usp=sharing

This PR covers all the ABDM M3 features,

  • raising a consent request
  • getting patient's data after approval
  • showing the patient data
  • removing the access to the data once the consent is expired or revoked

@vercel
Copy link

vercel bot commented Oct 25, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
care-storybook ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 8, 2024 6:11am

@netlify
Copy link

netlify bot commented Oct 25, 2023

Deploy Preview for care-egov-staging ready!

Name Link
🔨 Latest commit 5c3c156
🔍 Latest deploy log https://app.netlify.com/sites/care-egov-staging/deploys/65c470759185c6000733a82f
😎 Deploy Preview https://deploy-preview-6487--care-egov-staging.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@github-actions
Copy link

👋 Hi, @khavinshankar,
Conflicts have been detected against the base branch. Please rebase your branch against the base branch.


This message is automatically generated by prince-chrismc/label-merge-conflicts-action so don't hesitate to report issues/improvements there.

@github-actions github-actions bot added the merge conflict pull requests with merge conflict label Oct 25, 2023
Copy link

github-actions bot commented Nov 2, 2023

Hi, This pr has been automatically marked as stale because it has not had any recent activity. It will be automatically closed if no further activity occurs for 7 more days. Thank you for your contributions.

@github-actions github-actions bot added the stale label Nov 2, 2023
Copy link

github-actions bot commented Nov 9, 2023

Hi, @gigincg, @nihal467, @khavinshankar, @mathew-alex, This pr has been automatically closed because it has not had any recent activity. Thank you for your contributions. Feel free to repopen the pr.

@github-actions github-actions bot closed this Nov 9, 2023
@khavinshankar khavinshankar added merge conflict pull requests with merge conflict and removed merge conflict pull requests with merge conflict stale labels Dec 6, 2023
@khavinshankar khavinshankar reopened this Dec 6, 2023
Copy link
Member

@Ashesh3 Ashesh3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, just fix the unintentional hostname change

@github-actions github-actions bot added the merge conflict pull requests with merge conflict label Jan 31, 2024
Copy link

👋 Hi, @khavinshankar,
Conflicts have been detected against the base branch. Please rebase your branch against the base branch.


This message is automatically generated by prince-chrismc/label-merge-conflicts-action so don't hesitate to report issues/improvements there.

Comment on lines +473 to +639

export const linkViaQR = (abha_details: any, patientId?: string) => {
return fireRequest("linkViaQR", [], {
...abha_details,
patientId,
});
};

export const linkCareContext = (
consultationId: string,
data: { name?: string; gender?: "M" | "F" | "O"; dob?: string }
) => {
return fireRequest("linkCareContext", [], {
consultation: consultationId,
...data,
});
};

export const getAbhaCard = (patient: string, type: "pdf" | "png") => {
return fireRequest("getAbhaCard", [], {
patient,
type,
});
};

export const getHealthInformation = (artefactId: string) => {
return fireRequest("getHealthInformation", [], { artefactId });
};

export const healthFacilityActions = {
list: (params: object) => {
return fireRequest("listHealthFacilities", [], params);
},

create: (data: object) => {
return fireRequest("createHealthFacility", [], data);
},

read: (id: string) => {
return fireRequest(
"getHealthFacility",
[],
{},
{ facility_id: id },
undefined,
true
);
},

update: (id: string, data: object) => {
return fireRequest("updateHealthFacility", [], data, {
facility_id: id,
});
},

partialUpdate: (id: string, data: object) => {
return fireRequest("partialUpdateHealthFacility", [], data, {
facility_id: id,
});
},

registerService: (id: string) => {
return fireRequest(
"registerHealthFacilityAsService",
[],
{},
{ facility_id: id }
);
},
};

export const consentActions = {
list: (params: object) => {
return fireRequest("listConsents", [], params);
},

create: (data: object) => {
return fireRequest("createConsent", [], data);
},

read: (id: string) => {
return fireRequest("getConsent", [], {}, { id });
},

status: (id: string) => {
return fireRequest("checkConsentStatus", [], {}, { id }, undefined, true);
},
};

export const patientsActions = {
find: (params: object) => {
return fireRequest("findPatients", [], params);
},
};

export const listAssetAvailability = (params: object) =>
fireRequest("listAssetAvailability", [], params);
export const getAssetAvailability = (id: string) =>
fireRequest("getAssetAvailability", [], {}, { id });

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was this added accidentally by a bad resolve of merge conflict?

Also, I see only consentActions redux action that is being newly used by useDispatch in this PR. Can we migrate that to useQuery instead?

Rest of the newly added redux actions can be removed since they are not referenced nor used by useQuery.

@github-actions github-actions bot removed the merge conflict pull requests with merge conflict label Feb 1, 2024
Copy link

github-actions bot commented Feb 6, 2024

👋 Hi, @khavinshankar,
Conflicts have been detected against the base branch. Please rebase your branch against the base branch.


This message is automatically generated by prince-chrismc/label-merge-conflicts-action so don't hesitate to report issues/improvements there.

@github-actions github-actions bot added the merge conflict pull requests with merge conflict label Feb 6, 2024
netlify.toml Outdated Show resolved Hide resolved
@github-actions github-actions bot removed the merge conflict pull requests with merge conflict label Feb 8, 2024
@khavinshankar
Copy link
Member Author

Closing this pr and creating a new pr with the same branch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants