Core HIEBus Concepts

• Record Authority: The Record Authority is what HIEBus uses to scope identifiers. It is similar to HL7’s Assigning Authority or FHIR’s identifier.system. An identifier will be unique within a given Record Authority but an identifier may exist in multiple Record Authorities and may represent different entities in each Record Authority.

• Patient Record: HIEBus incorporates patient data from multiple data sources. Each human being may have data in multiple systems using different identifiers and potentially differing demographics. Each system’s view of each patient is incorporated into HIEBus as a distinct patient record. Patient records are identified by the combination of a Record Authority and an identifier (e.g. MRN).

• Record Group: A Record Group is the end result of the HIEBus record linking system. The Record Group represents the set of patient records associated with a single human being. A Record Group is assigned two ID values, a RecordGroupID and a PersonID. The RecordGroupID is a transient identifier that is changed every time a Record Group is modified. The PersonID is analogous to an MPI identifier and, except in the case of two groups being merged together, can be expected to remain constant.

• Term: A coded element. A term is identified by a code and a coding system. Every coded data property in HIEBus is linked to a term. For example, elements like gender, race, patient class, and patient type are stored as terms in HIEBus

• Term Namespace: The HIEBus Term Namespace is used to provide scoping to Terms. It is equivalent to the “coding system” used in the HL7 CE data type. Term Namespaces in HIEBus may be canonical such as ICD10, RxNorm, or SNOMED-CT but may also represent custom or vendor specific coding sets.