Open Dental Forum

Posted: **Wed Oct 01, 2025 2:23 pm**

On the ProcedureLogs POST (create) I have noticed an oddity where the AptNum is being silently ignored. When I look documentation I see an oddity where the AptNum is being referenced as the PatNum on the appointment table vs the actual AptNum. Is this a typo on the documentation or in the backend API coding where it might be a mixup that is causing things to be ignored?

https://www.opendental.com/site/apiprocedurelogs.html

PatNum: Required. FK to patient.PatNum.
ProcDate: Required. String in "yyyy-MM-dd" format.
ProcStatus: Required. Either TreatmentPlanned (TP), Complete (C), or ExisitingOtherProvider (EO). (Added in version 25.1.14) Existing Current Provider (EC), Referred Out (R), or Condition (Cn).
CodeNum: (Added in version 25.2.21) This or procCode is Required. FK to procedurecode.CodeNum.
procCode: This or CodeNum is Required. This should be a valid D code, example: D0120. CodeNum is set automatically.

AptNum: Optional. FK to appointment.PatNum.
ProcFee: Optional. If none is given this will default to the procedurecodes default, with consideration of the patient's insurance.
Priority: Optional. Definition.DefNum where definition.Category=20. Default is the first definition in that Category. If Priority is used, then priority will be set automatically.

Posted: **Wed Oct 01, 2025 2:54 pm**

laborspy wrote: Wed Oct 01, 2025 2:23 pm On the ProcedureLogs POST (create) I have noticed an oddity where the AptNum is being silently ignored. When I look documentation I see an oddity where the AptNum is being referenced as the PatNum on the appointment table vs the actual AptNum. Is this a typo on the documentation or in the backend API coding where it might be a mixup that is causing things to be ignored?

https://www.opendental.com/site/apiprocedurelogs.html
PatNum: Required. FK to patient.PatNum.
ProcDate: Required. String in "yyyy-MM-dd" format.
ProcStatus: Required. Either TreatmentPlanned (TP), Complete (C), or ExisitingOtherProvider (EO). (Added in version 25.1.14) Existing Current Provider (EC), Referred Out (R), or Condition (Cn).
CodeNum: (Added in version 25.2.21) This or procCode is Required. FK to procedurecode.CodeNum.
procCode: This or CodeNum is Required. This should be a valid D code, example: D0120. CodeNum is set automatically.

AptNum: Optional. FK to appointment.PatNum.
ProcFee: Optional. If none is given this will default to the procedurecodes default, with consideration of the patient's insurance.
Priority: Optional. Definition.DefNum where definition.Category=20. Default is the first definition in that Category. If Priority is used, then priority will be set automatically.

Hello laborspy,

“appointment.PatNum” was a typo in the API documentation and has since been fixed to reflect “appointment.AptNum”, thank you for pointing that out. Regarding the behavior you described, the backend correctly uses AptNum from the payload to attach a procedurelog to an appointment. Are you able to provide more information so that we can investigate further?

Thanks!

Open Dental Forum

ProcedureLogs POST (create) --- Possible Error in logic?

ProcedureLogs POST (create) --- Possible Error in logic?

Re: ProcedureLogs POST (create) --- Possible Error in logic?