I will discuss in the answer some ways and recommend one.
1. Using slugs (recommended)
I mention this in these answers:
The principle is to use another parameter to identify the person and pass it on the route. The CPF, for example, is a good candidate. The name may be another candidate, but there you have to choose some way to undo ambiguities in case of double name.
2. Using POST
This is not a good way because in order to access a record, you will always have to submit a form, validate it, in order to only forward the user to the edit screen.
3. Using an Encoded Variable
This remembers method 1, but implies some more implementation. The idea is a URL like this:
/PessoaFisica/Acao/?codigo=A2B7649C100DB2F641
Using some reversible encryption algorithm, you can mask the Id and the action to be performed within the encrypted variable.
Although it works, it is more disadvantageous than slug because it is not intuitive.