10.46243/jst.2022.v7.i05.pp131-147 registered
A Unified Approach to Cloud based Integrated Health Care Service Management System: Bhubaneswar Smart City as a Case study
Resolves to https://www.jst.org.in/index.php/pub/article/view/508
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jst.2022.v7.i05.pp131-147
Registered 29 Sep 2026 via crossref · record version 2 · last change 29 Sep 2026, 11:59 PM · record sha256 632375785a3bade7…
Resolve ⬇ Record (JSON) ⬇ Kernel Metadata Declaration (XML) Compare with Crossref Cite (APA · BibTeX · RIS · CSL)
What the DOI identifies
JournalArticle — an article in a journal · Digital · Visual · en
A Unified Approach to Cloud based Integrated Health Care Service Management System: Bhubaneswar Smart City as a Case study (PrincipalTitle)
Published 2023-07-18
Part of Journal of Science & Technology · ISSN 2456-5660 · volume 7 · issue 5 · pages 131–147
Agents
- Dillip Kumar Mahapatra Dillip Kumar Mahapatra (author)
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jst.2022.v7.i05.pp131-147
Abstract
The cost of health care has been steadily increasing. Evaluate an organization's success by ensuring the overall effectiveness of the sector. There has been a rapid change in patient treatment. IoT-enabled integrated management systems are used in smart city hospitals to manage patient data. Because of the geographic diversity, technical inconsistency, socio-economic adaptability, and cultural or climatic differences, it can be difficult to share patient data between hospitals for improved treatment, especially in smart cities like Bhubaneswar. We'd like to enhance the flow of data via the HMS. This is the result of centralized hospital management. For important patient transfers, this architecture enhances information flow. It allows patients to visit nearby hospital doctors if transportation is impractical or impossible. Aim of this work is to model a healthcare management system that is both efficient and secure. As faulty models can cause delays and increase costs. There is a chance of inefficiency. Since, UML ensures the correctness of all planning models; hence software and its functions are described using objectoriented modeling. It also demonstrates how the logical and physical components of a healthcare database management system may be described using a Unified Modeling Language to develop software with object-oriented features
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.i05.pp131-147 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | A Unified Approach to Cloud based Integrated Health Care Service Management System: Bhubaneswar Smart City as a Case study (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | author: Dillip Kumar Mahapatra Dillip Kumar Mahapatra publisher: Longman Publishers published: 2023-07-18 part of: Journal of Science & Technology · ISSN 2456-5660 · vol. 7 · no. 5 · pp. 131–147 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
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) | 103 fields set · sha256 7a9339f83f47… |
| 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.
