I agree with glork on this but want to add just a bit.
If, indeed, you are deferring the fix until some time after launch and this is well-known and understood, I think it would be wise to document "known issues" in your release documentation and do a risk analysis to show that it's not going to adversely affect safety or efficacy. If it does affect efficacy, then maybe additional mitigations; e.g., some user training, is require to work around the issue.
Good question - hopefully there will be some more discussion.