That said, there are different ways to create UUIDs that get so close to statistically unique that one must ask how close to tangent must one get. Not that there is ever a way to prove that any Unique ID is absolutely unique, but UUID is a fixed size and without a structure that tries to guarantee uniqueness. These are not absolutely unique, but statistically unique. ![]() There are 2 types of unique identifiers discussed here: Any attempt to see if it is close to the ID you want will only result in trouble down the line. But also that when 'using' a unique ID one compares the whole thing to determine if it is the unique ID you want or not. Meaning that the structure of the unique ID is important when creating a new one, to assure you are truly creating a new one that doesn't exist today or in the future. Some Unique Identifiers are hierarchical and one could possibly determine something about the object by looking at the identifier but this should NOT be relied on, it should be worried about (Risks to Privacy-Security). It should also be made clear that a Unique Identifier is an opaque identifier meaning it is either identifying the object or it is not - True or False. ![]() Like homeCommunityId, RepositoryUniqueId, etc. ![]() To a computer a communications protocol, these are just a Unique Identifier of an Object. ![]() This goes for things like Patient Identifiers, DICOM Study Instance (DICOM calls these a UID), and CDA Documents.
0 Comments
Leave a Reply. |