Coming soon
The Trusted Exchange Framework and Common Agreement (TEFCA) uses object identifiers (OIDs) to designate unique organizations and records belonging to network participants. An OID is a globally unique identifier of the International Organization for Standardization (ISO). Learn more about OIDs.
Using an existing OID
You must use (and we provide for you) three OID types within TEFCA:
OID type | Description | OID structure |
|---|---|---|
Organization | Corresponds to your organization within TEFCA. | 2.16.840.1.113883.3.6147.450..1.X.XXXX.X.X.1 |
Patient | Corresponds one-to-one with your Master Patient Indexes (MPIs). We create the first one for you, but if you have multiple MPIs, you should create as many patient OIDs to equal the number of MPIs in our system. | 2.16.840.1.113883.3.6147.450..1.X.XXXX.X.X.2 |
Document | Corresponds one-to-one with each document exchanged. You must have a document OID for every document you exchange. This can be either Redox-generated OID followed by your ID (e.g., …3.1^12345) or a version 4 UUID. Learn more about version 4 UUIDs. | 2.16.840.1.113883.3.6147.450..1.X.XXXX.X.X.3 |
To break down the OID structure:
OID segment | Notes |
|---|---|
2.16.840.1.113883.3.6147.450 | This is Redox. |
X | The first X represents the Redox deployment: 0: local development 1: AWS non-production 2: AWS production 3: GCP non-production 4: GCP production |
XXXX | This segment should be populated with your Redox organization ID. |
X | The second X represents the environment type: 0: development 1: staging 2: production |
X | The third X represents a number assigned to the partner site. This can be omitted if there's only 1 site. |