This part of ISO 21549 is applicable to situations in which clinical data additional to the limited clinical data defined in ISO 21549-3 is recorded on or transported by patient healthcare data cards compliant with the physical dimensions of ID-1 cards defined by ISO\/IEC 7810.<\/p>\n
This part of ISO 21549 specifies the basic structure of the data contained within the data object extended clinical data, but does not specify or mandate particular data sets for storage on devices.<\/p>\n
In order to facilitate interoperability, whenever an application is built for use in the healthcare domain in compliance with this part of ISO 21549, data items required for that application are drawn from the list of objects (some of which are extensible) as provided in Clause 5. These are used in conjunction with other data defined in other parts of this International Standard.<\/p>\n
The detailed functions and mechanisms of the following services are not within the scope of this part of ISO 21549, (although its structures can accommodate suitable data objects elsewhere specified).<\/p>\n
The encoding of free text data.<\/p>\n<\/li>\n
Security functions and related services which are likely to be specified by users for data cards depending on their specific application, for example: confidentiality protection, data integrity protection, and authentication of persons and devices related to these functions.<\/p>\n<\/li>\n
Access control services which may depend on active use of some data card classes such as microprocessor cards.<\/p>\n<\/li>\n
The initialisation and issuing process (which begins the operating lifetime of an individual data card, and by which the data card is prepared for the data to be subsequently communicated to it according to this part of ISO 21549).<\/p>\n<\/li>\n<\/ul>\n
The following topics are therefore beyond the scope of this part of ISO 21549:<\/p>\n
physical or logical solutions for the practical functioning of particular types of data cards;<\/p>\n<\/li>\n
how the message is processed further \u2018downstream\u2019 of the interface between two systems;<\/p>\n<\/li>\n
the form which data takes for use outside the data card, or the way in which such data are visibly represented on the data card or elsewhere.<\/p>\n<\/li>\n<\/ul>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 4<\/td>\n | Foreword <\/td>\n<\/tr>\n | ||||||
| 6<\/td>\n | Foreword <\/td>\n<\/tr>\n | ||||||
| 8<\/td>\n | Introduction <\/td>\n<\/tr>\n | ||||||
| 11<\/td>\n | Section sec_1 Section sec_2 1\tScope 2\tNormative references <\/td>\n<\/tr>\n | ||||||
| 12<\/td>\n | Section sec_3 Section sec_3.1 Section sec_3.5 Section sec_3.9 Section sec_4 Section sec_5 Section sec_5.1 3\tTerms and definitions 4\tSymbols and abbreviated terms 5\tBasic data object model for a healthcare data card 5.1\tPatient HDC data object structure <\/td>\n<\/tr>\n | ||||||
| 13<\/td>\n | Figure fig_1 Section sec_5.2 Section sec_5.2.1 Section sec_5.2.2 Section sec_5.2.3 5.2\tBasic data objects for referencing <\/td>\n<\/tr>\n | ||||||
| 14<\/td>\n | Section sec_5.2.4 Section sec_6 Section sec_6.1 Section sec_6.2 Section sec_7 Section sec_7.1 6\tFunctional requirements on card information for extended clinical data 6.1\tOverview of supported uses 6.2\tClinical message transfer between healthcare parties 7\tExtended clinical data 7.1\tGeneral <\/td>\n<\/tr>\n | ||||||
| 15<\/td>\n | Figure fig_2 Table tab_1 Section sec_7.2 Figure fig_3 7.2\tThe clinical event description <\/td>\n<\/tr>\n | ||||||
| 16<\/td>\n | Table tab_2 Section sec_7.3 Figure fig_4 7.3\tThe mapped clinical message <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | Table tab_3 <\/td>\n<\/tr>\n | ||||||
| 18<\/td>\n | Annex sec_A Annex\u00a0A \n(normative)<\/p>\n ASN.1 Data definitions <\/td>\n<\/tr>\n | ||||||
| 19<\/td>\n | Annex sec_B Annex sec_B.1 Figure fig_B.1 Annex\u00a0B \n(informative)<\/p>\n Rationale of extended clinical data structure <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | Figure fig_B.2 Annex sec_B.2 <\/td>\n<\/tr>\n | ||||||
| 21<\/td>\n | Figure fig_B.3 <\/td>\n<\/tr>\n | ||||||
| 22<\/td>\n | Figure fig_B.4 <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | Annex sec_C Annex sec_C.1 Annex sec_C.2 Table tab_C.1 Annex\u00a0C \n(informative)<\/p>\n Type and subtype of clinical event <\/td>\n<\/tr>\n | ||||||
| 25<\/td>\n | Annex sec_C.3 Table tab_C.2 <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | Reference ref_1 Reference ref_2 Reference ref_3 Reference ref_4 Reference ref_5 Reference ref_6 Reference ref_7 Reference ref_8 Reference ref_9 Reference ref_10 Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Health informatics. Patient healthcard data – Extended clinical data<\/b><\/p>\n |