MENU
If you don't want to use Identity, a Translation Table can be used instead to map patient IDs.
Suggested Answer: B
Get Premium EDI101 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
In Epic, Identity is the required framework for mapping record-level identifiers, especially for patients. Translation Tables are intended for mapping 'Category Lists' (like Gender, Race, or Marital Status) where there are a limited number of static values. Because patient IDs are unique to every record and number in the millions, they cannot be managed via a simple translation table.
15 comments · newest first
CA
Catina
1 month ago
Still, I feel B has its merits. Identity ensures uniqueness.
JU
Junita
2 months ago
Exactly! Less confusion with patient IDs.
ED
Eden
2 months ago
True, but a Translation Table simplifies mapping.
CA
Catina
2 months ago
But what if it’s B? Identity is crucial for accuracy.
JU
Junita
2 months ago
I agree, A seems right. Identity can complicate things.
ED
Eden
2 months ago
I think it's A. Makes sense to use a Translation Table.
DU
Dulce
2 months ago
I've never heard of that approach before.
OT
Otis
3 months ago
Sounds right to me!
HA
Hannah
3 months ago
Wait, are we sure about that?
LA
Larae
3 months ago
I disagree, Identity is more reliable.
AD
Adelle
3 months ago
That's true, a Translation Table can work.
NO
Novella
3 months ago
I definitely recall something about using Translation Tables, but I can't remember if it was specifically for patient IDs.
RO
Rosalind
4 months ago
I'm leaning towards false, but I feel like there might be exceptions where a Translation Table could work.
CH
Cheryl
4 months ago
I remember a similar question about patient ID mapping, and I think we concluded that Identity is usually preferred.
CA
Carmela
4 months ago
I think it's true because we discussed using Translation Tables in class, but I'm not entirely sure.