ICD-10 Code E83.824: ABCC6 deficiency causing pseudoxanthoma elasticum
What is this code?
ICD-10 codes are diagnosis classification codes used in healthcare records, reporting, coding workflows, and billing support. This code sits within the broader ICD-10 area for Endocrine, nutritional and metabolic diseases (E00-E89).
šClinical overview
E83.824 is the specific entry for ABCC6 deficiency causing pseudoxanthoma elasticum, or PXE. The selected NLM reference describes mineral deposition in elastic tissues, with possible skin, eye and vascular manifestations that vary between individuals. This is distinct from automatically assigning ABCC6-related GACI or interpreting every arterial calcium finding as PXE. A code alone supplies no skin examination, retinal finding, vascular result or degree of impairment. This explanation adds context about that named phenotype while retaining official descriptions, existing exclusions and related-code navigation.
When is it used?
- May be used when a clinician documents abcc6 deficiency causing pseudoxanthoma elasticum in a patient's medical record.
- May appear in hospital records, claims, referrals, and clinical documentation.
- This code can be used as a clinically usable diagnosis entry in standardized coding workflows.
What it does not mean
- A code alone does not explain severity, treatment plan, or outcome.
- A medical code should not be treated as a substitute for a doctor's diagnosis or advice.
š©ŗClinical context
- Skin, eye and blood-vessel involvement are possible aspects of PXE, not a checklist that establishes the condition in someone reading the page. The selected research places PXE and GACI within overlapping biology, but the US code here still specifies an ABCC6-related PXE phenotype. Shared mechanisms do not make neighboring labels interchangeable or demonstrate that every organ is affected. Ask what the diagnostic account actually establishes, which findings have been assessed and how any genetic report was interpreted. No variant, family carrier state or personal prognosis is supplied by the classification.
- E83.824 is a complete billable terminal code under the unchanged nonbillable E83.82 parent. All nine saved local coding-note arrays are empty. The GACI leaves' code-also examples for heart failure and secondary hypertension are not local instructions on this PXE page. Higher-level E83 exclusions remain at their original scope, and none are turned into reader diagnoses. The literature does not revise source metadata, coding guidance or clinical-review flags. A billable code also does not authorize an eye treatment, establish service eligibility or certify that an examination has occurred.
- The one exact saved Index route is Deficiency, deficient > ABCC6 > pseudoxanthoma elasticum. The neighboring ABCC6-GACI route is different, despite the shared gene term. This preserves the distinction between the documented phenotype and a broader research discussion about biological overlap. Navigation links do not establish that the reader has another disorder or authorize a code substitution. Keep the original route and descriptor alongside the actual clinical account, asking for clarification where needed rather than converting a possible skin or eye symptom into a molecular diagnosis.
- A classification page helps explain the label used in a record, but cannot replace the underlying diagnosis or determine a person's clinical status. The nonbillable parent and its terminal children have different navigation roles. Similar words and shared biological pathways do not establish equivalent diagnoses, the presence of complications or a treatment sequence. This addition keeps official descriptions, Index routes, inherited notes and related codes in their existing sections. It does not decide which code a clinician should assign or assert new medical approval.
- The selected disease reference describes how elastic-tissue mineralization can relate to skin changes, retinal abnormalities and vascular symptoms. Those possibilities can help frame questions for individualized clinical assessment, not assign findings to every reader. Ask which concerns are documented, who interprets eye or vascular findings and what a proposed assessment would clarify. The page supplies no retinal image, visual acuity, arterial test or stage of disease. It does not set a screening interval or require every reader to obtain the same investigations merely because several organ systems are described in general literature.
- The saved PXE leaf contains no cross-system service or diagnosis section and has empty direct related-test and related-procedure lists. Possible clinical relevance of eye or vascular expertise does not create a stored procedure mapping, prove a consultation or establish insurer coverage. The PTH association belongs to a different leaf and is not represented as an existing PXE link. An investigation should be explained in relation to the person's actual question and findings. This educational addition makes no laboratory, imaging or treatment order and no claim that an absent administrative link decides appropriateness.
- Related-code navigation and separately stored service associations answer different questions. A sibling link is not evidence of another diagnosis, and an article-derived service relationship is not a result or an agreed care plan. Original relationship direction, source and strength remain unchanged. Ask the responsible clinical team what a proposed investigation is intended to clarify, and the appropriate administrative team about current eligibility or coverage. This explanation does not represent every displayed link as a present clinical recommendation or a payment guarantee.
- Useful questions separate established findings from unresolved ones: what is the full diagnosis, how was it reached, which results have actually been interpreted and what question would an additional assessment answer? Bring the relevant clinical account and current instructions rather than an isolated code. Where two parts of a record appear inconsistent, ask the responsible team to reconcile them. The page does not silently repair a coding statement, supply a missing genotype or turn a general feature in a reference into an observed finding.
- This page does not choose a retinal medicine, dietary restriction, supplement, antithrombotic change or vascular intervention. The references provide disease context, not a personalized plan or a complete current treatment guideline. Ask which established concern a proposed action addresses and how the responsible team will assess it. Do not infer that every skin change requires an eye procedure or that a general mention of bleeding means a prescribed medicine should be stopped. No regimen, numerical target, promised visual outcome, fixed monitoring schedule or treatment transfer from GACI is provided.
- An individualized care plan should connect actual findings with the purpose of each proposed action and identify who coordinates the plan. A classification label, a mechanistic explanation or an administrative link cannot by itself choose an investigation or treatment. Discuss changes with the treating team rather than start or discontinue medicines, alter mineral intake or copy another code's care pathway. This education does not establish a therapy's suitability, research eligibility, insurance entitlement or availability, and supplies no substitute for diagnosis-specific instructions.
- Ask what follow-up has actually been agreed, who interprets results and how to raise a new concern. A page-ingestion date or source-update date is not a clinical monitoring schedule. A missing service association does not prove that an assessment is unnecessary, while a present association does not prove it is required. Follow-up needs the person's real clinical account. No fixed imaging interval, family-screening timetable, disease stage, developmental forecast or assurance that a condition is stable follows from this code.
- An online code page cannot assess a new acute illness or certify that symptoms are safe. Follow any individualized urgent-care instructions already supplied by the treating team, and seek appropriate local medical help for severe acute symptoms rather than waiting for a routine appointment or an online explanation. This is a general safety boundary, not a diagnosis of an emergency in every reader, a complete warning-sign checklist or a syndrome-specific threshold. Absence of a particular warning here cannot rule out a serious problem.
šKey distinctions
- These six entries share a classification branch, not one phenotype, genotype or care pathway. The exact leaf's gene and disease wording remains important. Biological overlap in research does not establish coexisting disease in every reader or authorize a code substitution. General features do not supply an individual's age, severity, family history, test results or prognosis.
- The selected references support qualitative education and explicitly limited source context, not a personal prescription or complete current management protocol. No numerical laboratory target, drug or supplement regimen, compulsory genetic panel, imaging schedule, surgery decision or experimental pathway treatment is established. Administrative associations do not create a test order or a coverage guarantee.
- The nonbillable E83.82 parent remains unchanged. Existing exclusions and conditional notes retain their own scope; a condition named as an example is not automatically present. Only E83.822 has a stored PTH service association. The literature neither copies it to other leaves nor removes any original note, relationship, source metadata or review-required flag.
- Related-code links identify classification neighbors and preserve the separate identities of ABCC6-GACI, ENPP1 phenotypes and CD73-deficiency arterial calcification. They do not establish a set of diagnoses in the reader. The stored Endocrinologist and General Physician entries remain intact and are not presented as an exhaustive clinical team. Original review-required flags, source year, exclusions, hierarchy and semantic payloads are unchanged. Possible disease manifestations in selected literature are not substituted for actual examination findings, and this addition does not certify that a clinician has reviewed the page or the individual case.
- References have distinct dates and roles: older patient education explains background, selected research describes studied observations, and a dated institutional announcement does not become a current treatment guideline. The source-access date records this review, not clinician signoff on the original page or the reader's record. Inaccessible works and search extracts are not substituted for readable source bodies. No claim of reviewing an entire paper, its figures, every later study or a complete contemporary clinical guideline is made by this addition.
- The original identity, URL, patient content, official descriptors, exclusions, hierarchy, Index routes, specialist and service links, metadata, review flags and semantic payloads remain intact. This literature supplements them rather than removing existing sections or creating a missing page. A correction to clinical documentation, source coding data, relationships or an existing enrichment would require a separate reviewed decision. Adding educational context does not authorize an overwrite, a diagnosis change, a new service mapping or a claim that care has been performed.
Code hierarchy
Where you may see this code
You may see this code in hospital records, discharge summaries, insurance claims, encounter documentation, referrals, or other healthcare billing and coding records.
Related specialists
Related codes
Sibling codes
Coding guidelines
Common synonyms
Frequently asked questions
About this content
This page is prepared by HealthAssure's clinical team using official coding standards from ICD-10. AI tools assist with drafting explanations, which are then reviewed and verified by healthcare professionals for accuracy. This content is for informational purposes and does not replace professional medical advice. Meet our team.