10.46243/jst.2022.v7.i01.pp22-40 registered
Discussion About Gap Between Necessary Healthcare Trends and Apps Used
Resolves to https://www.jst.org.in/index.php/pub/article/view/327
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jst.2022.v7.i01.pp22-40
Registered 29 Sep 2026 via crossref · record version 2 · last change 29 Sep 2026, 11:59 PM · record sha256 6792e7f0a205a014…
Resolve ⬇ Record (JSON) ⬇ Kernel Metadata Declaration (XML) Compare with Crossref Cite (APA · BibTeX · RIS · CSL)
Also as schema.org JSON-LD · Turtle · RDF/XML · DataCite XML · Crossref UNIXREF · Crossref UNIXSD — the formats of the DOI content-negotiation service, from this record (which carries what).
What the DOI identifies
JournalArticle — an article in a journal · Digital · Visual · en
Discussion About Gap Between Necessary Healthcare Trends and Apps Used (PrincipalTitle · en)
Published 2023-07-26
Part of Journal of Science & Technology · ISSN 2456-5660 · volume 7 · issue 1 · pages 22–40
Agents
- Mansi Kartik Ambalam Mansi Kartik Ambalam (author)
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jst.2022.v7.i01.pp22-40
Abstract · en
The fast pace of technological improvement and the rapid development and adoption of healthcare applications present crucial challenges for clinicians, users and policy makers. [39] Pandemic forced everyone to explore options that require minimal human interaction. This brought a surge in medical and health related app development. When initially conceived, these mobile medical applications performed basic functions e.g., BMI calculator, accessing reference materials etc; however, increasing complexity offers clinicians and patients a range of functionalities. [2] With more awareness amongst people, the apps started incorporating more features pertaining to healthcare. Even with the increase in medical apps usage today, it cannot be determined if the apps are enough to replace real doctors and adopt a completely app-dependent system for healthcare. In this paper, all the new trends that became increasingly popular related to medical apps have been explored. Then, these trends have been discussed and also what distinguishes them compared to the already existing features. We then take a look at the data of 130 existing apps that provide support for the mentioned trends in one way or another from a list of most used apps of last year in the Indian android market. With the analysis of the features in the apps, we take a look at what support is already provided. We then take a look at what could be done further to improve the already existing apps. With the combination of apps analysis and discussion on improvements, we can also draw a conclusion if the treatment of real doctors can be substituted with such apps.
System metadata — ISO 26324:2025, Annex B · DOI Handbook 10.1
Each element by the standard's name (Annex B: reference elements, then administrative) and the Handbook's (in grey), read off the record above.
| Element | Value | In the record |
|---|---|---|
| DOI Name DOI name | 10.46243/jst.2022.v7.i01.pp22-40 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | Discussion About Gap Between Necessary Healthcare Trends and Apps Used (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | author: Mansi Kartik Ambalam Mansi Kartik Ambalam publisher: Longman Publishers published: 2023-07-26 part of: Journal of Science & Technology · ISSN 2456-5660 · vol. 7 · no. 1 · pp. 22–40 language: en form: Digital · Visual · Language | agents, dates, container, language, structural_type, modes, characters |
| Referent Identifier(s) alternateIdentifier(s) | none besides the DOI | identifiers, relations (IsSameAs) |
| Registration Authority registrationAuthorityCode | Crossref — issued by Crossref (member 25296); held here as a copy | record.source_agency (our code, ra_doi_name, for names issued here once appointed) |
| Created Date issueDate | 2024-02-16 | record.registered (when the DOI name was first registered) |
| relatedIdentifiers | none needed — the descriptive metadata is in this record | container, relations (only where the descriptive metadata lives at another identifier) |
complete Every System Metadata element is here, with the basic metadata a journal article needs.
The System Metadata Declaration (JSON) · the Kernel Metadata Declaration (XML) · what each sub-type needs
Cited by — in this registry
No record held in this registry cites this DOI.
Counts only records held in this registry; a citation from a work held elsewhere is not seen here. The list as JSON
References with DOIs
The record lists 45 references; 17 carry a DOI.
| # | Reference | DOI | Held here |
|---|---|---|---|
| 1 | ref1 Esmita Charani, Enrique Castro-Sánchez, Luke SP Moore and Alison Holmes, "Do smartphone applications i n healthcare require a governance and legal framework? It depends on the app… | 10.1186/1741-7015-12-29 | not held here |
| 2 | ref2 M. McHugh and D. Lillis, “The Impact of Regulatory Changes on the Development of Mobile Medical Apps”, World Academy of Science, Engineering and Technology: International Journal … | 10.5281/zenodo.1124381 | not held here |
| 8 | ref8 Nazar Kvartalnyi, “Healthcare Mobile Apps Trends in 2021, Inoxoft, https://inoxoft.com/blog/healthcare-mobile-apps-trends-in-2021/, 2021 | 10.3389/fpubh.2021.685439 | not held here |
| 31 | ref31 Thomas Lorchan Lewis, “A Systematic Self-Certification Model for Mobile Medical Apps”, J Med Internet Res 2013;15(4):e89, available at doi:10.2196/jmir.2446 | 10.2196/jmir.2446 | not held here |
| 32 | ref32 Stoyan R Stoyanov, Leanne Hides, David J Kavanagh, Oksana Zelenko, Dian Tjondronegoro and Madhavan Mani, “Mobile App Rating Scale: A New Tool for Assessing the Quality of Health M… | 10.2196/mhealth.3422 | not held here |
| 33 | ref33 Paul Wicks and Emil Chiauzzi, “‘Trust but verify’ - five approaches to ensure safe medical apps”, BMC Med 13, 205 (2015), pp. 2-4, available at https://doi.org/10.1186/s12916-015-… | 10.1186/s12916-015-0451-z | not held here |
| 34 | ref34 Silva BM, Rodrigues JPC, Canelo F, Lopes IC and Zhou L:, “A data encryption solution for mobile health apps in cooperation en vironments”, J Med Internet Res 2013, 15(4):e66 avail… | 10.2196/jmir.2498 | not held here |
| 35 | ref35 Perry Foley, Dori Steinberg, Erica Levine, Sandy Askew, Bryan C. Batch, Elaine M. Puleo, Laura P. Svetkey, Hayden B. Bosworth, Abigail DeVries, Heather Miranda, Gary G. Bennett, “… | 10.1016/j.cct.2016.03.006 | not held here |
| 36 | ref36 Dimiter V. Dimitrov, “Medical Internet of Thin gs and Big Data in Healthcare”, Healthcare Informatics Research 2016; 22(3): 161, available at https://synapse.koreamed.org/articles… | 10.4258/hir.2016.22.3.156 | not held here |
| 37 | ref37 Rivera J, McPherson A, Hamilton J, Birken C, Coons M, Iyer S, Agarwal A, Lalloo C and Stinson J, “Mobile Apps for Weight Management: A Scoping Review”, JMIR Mhealth Uhealth 2016;4… | 10.2196/mhealth.5115 | not held here |
| 38 | ref38 Anirudh Kotlo, Pradeep M Muragundi, Virendra S Ligade and N Udupa, "Regulation of the mobile medical apps in India: Need of the hour." Journal of Current Pharma Research 5, no. 4 … | 10.1016/j.jval.2015.03.568 | not held here |
| 39 | ref39 Errol Ozdalga, Ark Ozdalga and Neera Ahuja, “The Smartphone in Medicine: A Review of Current and Potential Use Among Physicians and Students”, J Med Internet Res 2012;14(5):e128, … | 10.2196/jmir.1994 | not held here |
| 40 | ref40 Chan SR and Misra S., “Certification of Mobile Apps for Health Care”, JAMA. 2014;312:1155–6 available at https://doi.org/10.1001/jama.2014.9002 | 10.1001/jama.2014.9002 | not held here |
| 41 | ref41 Anjan K Banerjee, Sally Okun, I. Ralph Edwards, Paul Wicks, Meredith Y. Smith, Stephen J. Mayall, Bruno Flamion, Charles Cleeland and Ethan Basch, “Patient-Reported Outcome Measur… | 10.1007/s40264-013-0113-z | not held here |
| 42 | ref42 Zarin DA, Tse T, Williams RJ, Califf RM, Ide NC. The ClinicalTrials.gov results database–update and key issues. N Engl J Med. 2011;364:852–60 | 10.1056/nejmsa1012065 | not held here |
| 44 | ref44 Dave K. Apple’s App Store review process is hurting users, but we’re not allowed to talk about it. Medium. 2015. https://medium.com/@krave/apples-app-store-review-process-is-hurti… | 10.1111/j.1559-8918.2005.tb00005.x | not held here |
| 45 | ref45 Boulos, Maged N Kamel et al. “Mobile medical and health apps: state of the art, concerns, regulatory control and certification.” Online journal of public health informatics vol. 5… | 10.5210/ojphi.v5i3.4814 | not held here |
Relations
The record states no relation, and no record held here states one with this DOI.
Funding
The record names no funder.
Each funder's page lists every work held here that names it. ROR IDs open at ror.org; Funder Registry IDs resolve at doi.org.
History — the ledger
Every change to this DOI, in order, as it was recorded. Entries are only ever added, never changed or removed.
| # | When | What | By | Changes |
|---|---|---|---|---|
| 1 | 29 Sep 2026, 10:00 PM | register registered at Crossref; record read from api.crossref.org | Administrator (admin) | 159 fields set · sha256 98690621527e… |
| 2 | 29 Sep 2026, 11:59 PM | update record re-read from api.crossref.org | Administrator (admin) | container.titles.0.value: |
Machine-readable: the history as JSON, with the full record after each change.
Changes made at Crossref through DOI Doctor
Every deposit Smart Scholars' DOI Doctor made for this DOI, oldest first, with Crossref's own answer. Each fingerprint is the SHA-256 of its entry and of the fingerprint before it, so a change to any earlier entry changes every fingerprint after it.
| When | What changed | Crossref | Fingerprint |
|---|---|---|---|
| 07 Oct 2026, 07:37 | Metadata completed abstract (256 words) · licence | ● accepted by Crossref | 062254d3006d… |
| 07 Oct 2026, 08:47 | Read back: Crossref's record shows it | ● confirmed | 68ba4a639571… |
2 entries · the last fingerprint 68ba4a639571c69db2ad4a472c509a595551bd433828d0a1b85fd3c6a1141162 · the history as JSON, each entry with the fingerprint before it, to check them yourself.



