acknowledgements for ansi/nist-itl 1-2011 - NIST Visual Image ...
Share Embed Flag
Download ePaper

acknowledgements for ansi/nist-itl 1-2011 - NIST Visual Image ...

acknowledgements for ansi/nist-itl 1-2011 - NIST Visual Image ... acknowledgements for ansi/nist-itl 1-2011 - NIST Visual Image ...

biometrics.nist.gov
from biometrics.nist.gov More from this publisher
11.07.2015 Views

ANSI/NIST-ITL 1-2011 - UPDATE 2013 DRAFT VERSIONdetails about SRC, SAN, and ORI. For example,• The organization that traced the information about an implanted medical devicefor Field 21.006: Medical device information / MDI would be CON.• The local police department could create the actual ANSI/NIST-ITL 1-2011conformant record. Such an organization’s code would be entered in Field19.004: Source agency / SRC (for example NA54-X) and its name in Field19.993: Source agency name / SAN ( for example New Artichoke Police )In many implementation domains, there are a limited number of transmission organizationsthat can send data. Therefore, the agency listed in SRC may send the transaction to anotherlocation that has access rights to the final destination. This intermediary may addinformation to the transaction, as well. The final transmitting organization code is listed inField 1.008 Originating agency identifier / ORI. Its name may be entered in Originatingagency name /OAN in Field 1.017 Agency names / ANM.[

ANSI/NIST-ITL 1-2011 - UPDATE 2013 DRAFT VERSION8.21.17 Field 21.996: Hash/ HASThis optional field shall contain the hash value of the context representation in the externalfile reference in Field 21.994: External file reference / EFR or the 2D still image or otherdata stored in Field 21.999: Associated context data / DATA of this record, calculated usingSHA-256. See Section 7.5.2.8.21.18 Field 21.998: Geographic sample acquisition location / GEOThis optional field contains the location where the context information was acquired – notwhere it is stored. See Section 7.7.3.8.21.19 Field 21.999: Associated context data / DATAIf this field is used, Field 21.994: External file reference / EFR shall not be set. However,one of the two fields shall be present in all instances of this record type. See Section 7.2 fordetails on this field entry. It is mandatory for a 2D still image.[2013d>]8.22 Record Type-22: Non-photographic imagery data recordThe Type-22 record shall contain and be used to exchange imagery, such as that commonlyused in medical practices that may be of assistance in identification of victims of a massdisaster or other unknown deceased.This record type is often used in conjuction with the Type-12 record for transmission ofimagery stored using DICOM 183 . Specialized medical imagey used for 3D printing of castmodels is another example of data that may be transmitted using this record type. It canalso transmit scanned radiographs, as commonly used in dental treatments.2D images of the human body taken in visible light (i.e. not radiographs, which areincluded in this record type) are transmitted in a Type-10 record (even when intraoral).Images taken in infrared or ultraviolet wavelengths are transmitted in a Type-22 record.Note that the Type-22 record should not be used with Traditional format encoding.Table 103 Type-22 record layout183DICOM stands for “Digital Imaging and Communications in Medicine” and is astandard used in medial imagery issued by the National Electrical ManufacturersAssociation (NEMA).414

ANSI/<strong>NIST</strong>-ITL 1-<strong>2011</strong> - UPDATE 2013 DRAFT VERSION8.21.17 Field 21.996: Hash/ HASThis optional field shall contain the hash value of the context representation in the externalfile reference in Field 21.994: External file reference / EFR or the 2D still image or otherdata stored in Field 21.999: Associated context data / DATA of this record, calculated usingSHA-256. See Section 7.5.2.8.21.18 Field 21.998: Geographic sample acquisition location / GEOThis optional field contains the location where the context in<strong>for</strong>mation was acquired – notwhere it is stored. See Section 7.7.3.8.21.19 Field 21.999: Associated context data / DATAIf this field is used, Field 21.994: External file reference / EFR shall not be set. However,one of the two fields shall be present in all instances of this record type. See Section 7.2 <strong>for</strong>details on this field entry. It is mandatory <strong>for</strong> a 2D still image.[2013d>]8.22 Record Type-22: Non-photographic imagery data recordThe Type-22 record shall contain and be used to exchange imagery, such as that commonlyused in medical practices that may be of assistance in identification of victims of a massdisaster or other unknown deceased.This record type is often used in conjuction with the Type-12 record <strong>for</strong> transmission ofimagery stored using DICOM 183 . Specialized medical imagey used <strong>for</strong> 3D printing of castmodels is another example of data that may be transmitted using this record type. It canalso transmit scanned radiographs, as commonly used in dental treatments.2D images of the human body taken in visible light (i.e. not radiographs, which areincluded in this record type) are transmitted in a Type-10 record (even when intraoral).<strong>Image</strong>s taken in infrared or ultraviolet wavelengths are transmitted in a Type-22 record.Note that the Type-22 record should not be used with Traditional <strong>for</strong>mat encoding.Table 103 Type-22 record layout183DICOM stands <strong>for</strong> “Digital Imaging and Communications in Medicine” and is astandard used in medial imagery issued by the National Electrical ManufacturersAssociation (NEMA).414

logo

products

Resources

Company

Terms of service
Privacy policy
Cookie policy
Cookie settings
Imprint
Change language
Made with love in Switzerland
© 2024 Yumpu.com all rights reserved

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!