You do not have permission to edit this page, for the following reasons:

This IP address has been blocked from editing Wikipedia.
This does not affect your ability to read Wikipedia pages.
Most people who see this message have done nothing wrong. Some kinds of blocks restrict editing from specific service providers or telecom companies in response to recent abuse or vandalism, and can sometimes affect other users who are unrelated to that abuse. Review the information below for assistance if you do not believe that you have done anything wrong.

The IP address or range 54.163.0.0/16 has been blocked (disabled) by ‪Blablubbs‬ for the following reason(s):

The IP address that you are currently using has been blocked because it is believed to be a web host provider or colocation provider. To prevent abuse, web hosts and colocation providers may be blocked from editing Wikipedia.
You will not be able to edit Wikipedia using a web host or colocation provider because it hides your IP address, much like a proxy or VPN.
We recommend that you attempt to use another connection to edit. For example, if you use a proxy or VPN to connect to the internet, turn it off when editing Wikipedia. If you edit using a mobile connection, try using a Wi-Fi connection, and vice versa. If you are using a corporate internet connection, switch to a different Wi-Fi network. If you have a Wikipedia account, please log in.
If you do not have any other way to edit Wikipedia, you will need to request an IP block exemption.

How to appeal if you are confident that your connection does not use a colocation provider's IP address:
If you are confident that you are not using a web host, you may appeal this block by adding the following text on your talk page: ((unblock|reason=Caught by a colocation web host block but this host or IP is not a web host. My IP address is _______. Place any further information here. ~~~~)). You must fill in the blank with your IP address for this block to be investigated. Your IP address can be determined here. Alternatively, if you wish to keep your IP address private you can use the unblock ticket request system. There are several reasons you might be editing using the IP address of a web host or colocation provider (such as if you are using VPN software or a business network); please use this method of appeal only if you think your IP address is in fact not a web host or colocation provider.

Administrators: The IP block exemption user right should only be applied to allow users to edit using web host in exceptional circumstances, and requests should usually be directed to the functionaries team via email. If you intend to give the IPBE user right, a CheckUser needs to take a look at the account. This can be requested most easily at SPI Quick Checkuser Requests. Unblocking an IP or IP range with this template is highly discouraged without at least contacting the blocking administrator.

This block will expire on 17:28, 10 March 2024.

Even when blocked, you will usually still be able to edit your user talk page, as well as email administrators and other editors.

For information on how to proceed, please read the FAQ for blocked users and the guideline on block appeals. The guide to appealing blocks may also be helpful.

Other useful links: Blocking policy · Help:I have been blocked
Your IP address is in a range that has been blocked on all Wikimedia Foundation wikis. The block was made by ‪Jon Kolbert‬. The reason given is Open proxy/Webhost: See the help page if you are affected .
- Start of block: 18:27, 12 November 2023
- Expiry of block: 18:27, 12 November 2028
Your current IP address is 54.163.179.242. The blocked range is 54.163.0.0/16. Please include all above details in any queries you make. If you believe you were blocked by mistake, you can find additional information and instructions in the No open proxies global policy. Otherwise, to discuss the block please post a request for review on Meta-Wiki. You could also send an email to the stewards VRT queue at stewards@wikimedia.org including all above details.

You can view and copy the source of this page:

((Short description|Medicated adhesive patch delivers medication into the skin))
((distinguish|Transdermal patch))
((More citations needed|date=May 2020))
((Use dmy dates|date=September 2017))
((Use American English|date=September 2017))
A '''dermal patch''' or '''skin patch''' is a [[medicated]] [[adhesive]] patch placed on [[human skin]] to deliver a medication into the skin. This is in contrast to a [[transdermal patch]], which delivers the medication through the skin and into the [[bloodstream]].

== Popular uses ==
* Flector ([[diclofenac]] epolamine) patch is an [[NSAID]] topical patch for the treatment of acute pain due to minor strains, sprains, and contusions. It is also being used in the treatment of pain and inflammation for chronic conditions benefiting from NSAIDs, including [[fibromyalgia]] and [[arthritis]].
* [[Lidocaine]] patches, marketed as Lidoderm, relieve the peripheral [[pain]] of shingles (''[[herpes zoster]]''). It became commonly used off-label, for pain from acute injuries and chronic pain, although limited by its requirement to be removed for 12 hours, after 12 hours of use.
*Some experimental studies investigate the use of ceramic dermal patches for local antibiotic delivery to contaminated commercial skin graft patches,<ref>((Cite journal|last1=Sago|first1=Tetsu|last2=Mori|first2=Yoshio|last3=Takagi|first3=Hisato|last4=Iwata|first4=Hisashi|last5=Murase|first5=Katsutoshi|last6=Kawamura|first6=Yoshiaki|last7=Hirose|first7=Hajime|date=January 2003|title=Local treatment of Dacron patch graft contaminated with Staphylococcus aureus with antibiotic-releasing porous apatite ceramic: an experimental study in the rabbit|journal=Journal of Vascular Surgery|volume=37|issue=1|pages=169–174|doi=10.1067/mva.2003.105|issn=0741-5214|pmid=12514596|doi-access=free))</ref> and antibiotic dermal patches to deliver local antibiotic to the gum after dental surgery.<ref>((Cite journal|last1=Nair|first1=Sreeja C.|last2=Anoop|first2=K. R.|date=2012|title=Intraperiodontal pocket: An ideal route for local antimicrobial drug delivery|journal=Journal of Advanced Pharmaceutical Technology & Research|volume=3|issue=1|pages=9–15|doi=10.4103/2231-4040.93558|doi-broken-date=31 January 2024|doi-access=free|issn=2231-4040|pmc=3312733|pmid=22470888))</ref>

== Innovative biomaterials ==
=== Silks ===
==== Spider silk ====
===== Research =====
In 2016, a study from the University of Nottingham was published describing the first  synthetic [[spider silk]] that is functionally identical to naturally spun spider silk. Using non-natural methionine analog L-azidohomoalanine (L-Aha) and genetically modified E-Coli cells, self-assembling proteins under the conditions needed to create the filament were produced. These conditions had been researched years earlier by J. Johansson and co-workers studying the production of spider silk proteins. The proteins used in the study are a miniaturized version of the silk monomers found in nature that behave the same way; because of the modifications, they were able to express functionalized regions of the protein 4RepCT, which is a self-assembling recombinant dragline silk protein, derived from the nursery-web spider along the axis of the filament.<ref name=":0">((Cite journal|last1=Harvey|first1=David|last2=Bardelang|first2=Philip|last3=Goodacre|first3=Sara L.|last4=Cockayne|first4=Alan|last5=Thomas|first5=Neil R.|date=2016-12-28|title=Antibiotic Spider Silk: Site-Specific Functionalization of Recombinant Spider Silk Using "Click" Chemistry|journal=Advanced Materials|volume=29|issue=10|pages=1604245|doi=10.1002/adma.201604245|pmid=28028885|s2cid=22451798 |issn=0935-9648|url=http://eprints.nottingham.ac.uk/40954/))</ref>

===== Methods =====
Methods of functionalizing the 4RepCT protein have been successful, but not in the way of reliably producing a stable protein functionalization in biologic environments that can also be tuned and modified. Genetic fusion of functional peptide sequences to silk genes and chemical conjugation of functional molecules onto amino acid side chains are the only two methods currently known to achieve a functionalized 4RepCT protein with tunable functionality. The first approach has the advantage that post-translational manipulation of the silk is minimized. Unfortunately, genetic manipulation is challenging due to the high GC (guanine-cytosine) content of the gene which leads to transcription errors. This method also limits the prevalence of functional binding sites to a single ligand-binding site per 25 kDa 4RepCT silk protein. Large adaptor proteins such as antibodies can be used to display more binding sites, but it isn't considered a feasible solution. This method has been shown to produce 4RepCT proteins that have a higher cell adhesion than natural spidroin proteins and have varied antimicrobial properties. The second method, chemical modification of the silk proteins should result in the covalent attachment of several copies of a wide range of organic and organometallic ligands using robust or sensitive linkers depending on the application. The challenge with this method is it is difficult to make the modification of the 4RepCT protein site-specific. Specific site targeting requires the residues to also be modified to be accessible and chemically bioorthogonal to the rest of the silk protein. Cytosine residues are commonly used for this type of conjugation through a Michael addition, but they tend to undergo exchange reactions which makes them unstable for long durations in a biological environment. These two methods are rather outdated but have been useful in validating the fact that 4RepCT can be tuned in the important areas of cellular adhesion, antimicrobial potency, and the type of molecule or drug attached to it.<ref name=":0" />

Later azide functional groups were conjugated to the N-terminal of a dragline silk protein using EDC/NHS coupling, yielding glycopolymer-conjugated films with enhanced cell adhesion and DNA-silk chimeras with controllable micro-architectures. Armed with this, the researchers in this study investigated the incorporation of&nbsp;3 L-Aha residues into 4RepCT, yielding <math>4RepCT^{3Aha}</math>. The azide side chains of L-Aha allow highly specific and efficient site-specific conjugation to a lot different of functional molecules via Staudinger ligation with phosphine reagents, and Copper (I)-catalysed azide-alkyne cycloaddition ([[CuAAC]]) or Strain promoted azide-alkyne cycloaddition ([[Click chemistry|SPAAC]]) in click reactions.<ref name=":0" />

===== Preferred click reactions =====
CuAAC and SPAAC are both common click reactions which are often interchangeable in click chemistry. It is well known that intracellular Cu(I) is cytotoxic, which means CuAAC is not as common as SPAAC click reactions for research leading to in-vivo applications. The researchers for this study decided to use CuAAC, despite the purpose of this research to have in-vivo applications, for a few reasons. First, the likelihood for copper to be bound by the <math>4RepCT^{3Aha}
</math> protein is low due to the presence of only 2 glutamic acid residues and no histidine residues (two residues with a high affinity for Cu(I)). These residues are present in the thioredoxin; which is the solubilizing fusion partner conjugated to the 4RepCT protein during synthesis. However, this does not cause issues since the thioredoxin is removed in order to trigger the self-assembly reaction with thrombin which results in fiber formation. This removal of the Cu(I) laden thioredoxin removes virtually all copper from the silk structure. The researchers also, through a buffer containing EDTA and by utilizing THPTA (which stabilizes the copper ions), rinsed the fibers resulting in further removal of Cu(I) leaving a <0.1 % by weight trace of copper ions. Secondly, CuAAC outperforms SPAAC in click reactions where proteins with a high cytosine content, such as 4RepCT, are present. The SPAAC process, in the presence of proteins like 4RepCT, will often create ‘clicks’ in off-target sites resulting in the ligand conjugating to the wrong part of the protein and rendering the protein essentially useless. In order to maximize the number of functional sites along the fiber, CuAAC is preferred.<ref name=":0" /><ref>((Cite journal|last1=Li|first1=Shanshan|last2=Zhu|first2=He|last3=Wang|first3=Jiajia|last4=Wang|first4=Xiaomin|last5=Li|first5=Xu|last6=Ma|first6=Cheng|last7=Wen|first7=Liuqing|last8=Yu|first8=Bingchen|last9=Wang|first9=Yuehua|last10=Li|first10=Jing|last11=Wang|first11=Peng George|date=2016|title=Comparative analysis of Cu (I)-catalyzed alkyne-azide cycloaddition (CuAAC) and strain-promoted alkyne-azide cycloaddition (SPAAC) in O-GlcNAc proteomics|journal=Electrophoresis|language=en|volume=37|issue=11|pages=1431–1436|doi=10.1002/elps.201500491|issn=1522-2683|pmc=5967854|pmid=26853435))</ref>

===== Leading results =====
This study demonstrated the CuAAC mediated conjugation of <math>4RepCT^{3Aha}
</math> with two different fluorophores and the antibiotic levofloxacin, showcasing the potential of covalently functionalized recombinant spider silk proteins as biomaterials with enhanced properties. The researchers were able to successfully conjugate <math>4RepCT^{3Aha}
</math> with alkyne fluorophores, proving the protein can be functionalized through an azide group while conjugated to the axis of the silk fiber. Their results showed not only an intense uniform fluorescence along the fiber axis but also an intense uniform composite fluorescence when the fiber was decorated with two different fluorophores in a 1:1 ratio.<ref name=":0" />

To prove the functional azide group could be decorated with a clinically relevant molecule, the researchers attempted to decorate the fiber with glycidyl propargyl ether (an acid-labile linker) and bound Levofloxacin (a gram-positive targeting antibiotic) to it using an ester bond between the epoxide carboxylate groups respectively. They conducted an inhibition zone assay with the functionalized silk fibers against E. Coli NCTC 12242 bacteria where each factor level contained LB media. Their results showed a successful functionalization of the Levofloxacin decorated fiber which maintained an antibiotic persistence across a 3.5&nbsp;cm radius for 120 hours and a cell density ~50% of other factor levels (LB media only, unfunctionalized silk, and Levofloxacin doped silk) with p ≤ 0.01. A maximum sustained release of Levofloxacin from the fiber of 5 days was achieved.<ref name=":0" />

==== Dermal applications ====
===== Historical =====
Spider silk is one of the earliest known dermal patches. Primarily used for wound binding, the glycoprotein adhesive found on the capture spiral silk, as well as the protein structure of the fiber itself, has mild antibacterial properties. The silk, acting as a local antiseptic, reduced the rate of sepsis and chronic illness. The silk's viscoelastic properties and high tensile strength and toughness aided wound healing in a way similar to surgical tape.

===== Proposed =====
Despite its superiority to current methods of large-surface-area wound care—gauze wrapping, honey vinegar treatments, and systemic antibiotics—and popular dermal patch uses, spider silk has not found its way into clinical practice. Historically the main reason for this is the difficulty of farming, and harvesting the silk. Unlike silkworms, that spin silk for several easy-to-replicate conditions, spiders spin silk for specific purposes such as catching prey, difficult to replicate in laboratory conditions. In addition, spiders generally tend to be cannibalistic, so breeding sufficient numbers becomes difficult. Forced silking yields unsuitable silks. The most popular proposed use case for dermal applications are:

* Dermal patch for local drug delivery
* Local antibiotic wound dressings
* Local dermal reperfusion scaffolds
* Cutaneous mucosal adhesive for attaching non-adhesive local drug delivery devices

==== Silkworm silk ====
===== Research =====
Research shows [[Bombyx mori|silkworm]] silk does not possess any inherent antibiotic characteristics, bio-mimicking mechanical properties, and can cause fatal respiratory allergic reactions in some people.<ref>((Cite journal|last1=Jeong|first1=Kyoung Yong|last2=Han|first2=In-Soo|last3=Lee|first3=June Yong|last4=Park|first4=Kyung Hee|last5=Lee|first5=Jae-Hyun|last6=Park|first6=Jung-Won|date=May 2017|title=Role of tropomyosin in silkworm allergy|journal=Molecular Medicine Reports|volume=15|issue=5|pages=3264–3270|doi=10.3892/mmr.2017.6373|issn=1791-3004|pmid=28339033|doi-access=free))</ref>

A 2020 study found that recombinantly produced spider silk proteins self-assemble at the liquid-air interface of a standing solution, forming protein permeable, super strong and ultra flexible membranes. The unforced self-assembly creates a nanofibrilar membrane which supports cell growth. A confluent layer of human skin cells forms within three days, and would be suitable for direct delivery to a patient.<ref>((cite journal |last1=Gustafsson |first1=Linnea |last2=Panagiotis Tasiopoulos |first2=Christos |last3=Jansson |first3=Ronnie |last4=Kvick |first4=Mathias |last5=Duursma |first5=Thijs |last6=Gasser |first6=Thomas Christian |last7=van der Wijngaart |first7=Wouter |last8=Hedhammar |first8=My |title=Recombinant Spider Silk Forms Tough and Elastic Nanomembranes that are Protein-Permeable and Support Cell Attachment and Growth |journal=Advanced Functional Materials |date=Aug 16, 2020 |volume=30 |issue=40 |pages=2002982 |doi=10.1002/adfm.202002982 |doi-access=free ))</ref>

===== Dermal applications =====
As silkworm silk is potentially fatal to humans when in contact with vasculature, there is no approved dermal patch, or dermal patch-like, application for silkworm silk.((Dosage forms|state=expanded))

== References ==
((Reflist))

((Portal|Medicine))
((authority control))

[[Category:Dosage forms]]
[[Category:Drug delivery devices]]
[[Category:Pharmacokinetics]]

Pages transcluded onto the current version of this page (help):

Dermal patch (edit)
Template:0 (view source) (template editor protected)
Template:Ambox (view source) (template editor protected)
Template:Authority control (view source) (template editor protected)
Template:Cite journal (view source) (protected)
Template:DMCA (view source) (template editor protected)
Template:Dated maintenance category (view source) (template editor protected)
Template:Dated maintenance category (articles) (view source) (template editor protected)
Template:Distinguish (view source) (template editor protected)
Template:Dosage forms (edit)
Template:FULLROOTPAGENAME (view source) (template editor protected)
Template:Find sources mainspace (view source) (template editor protected)
Template:Hlist/styles.css (view source) (protected)
Template:Longitem (view source) (template editor protected)
Template:Main other (view source) (protected)
Template:More citations needed (view source) (template editor protected)
Template:Navbox (view source) (template editor protected)
Template:Ns has subpages (view source) (protected)
Template:Pagetype (view source) (protected)
Template:Plainlist/styles.css (view source) (protected)
Template:Portal (view source) (template editor protected)
Template:Reflist (view source) (protected)
Template:Reflist/styles.css (view source) (protected)
Template:Routes of administration, dosage forms (edit)
Template:SDcat (view source) (template editor protected)
Template:Short description (view source) (protected)
Template:Short description/lowercasecheck (view source) (protected)
Template:Ubl (view source) (template editor protected)
Template:Unbulleted list (view source) (template editor protected)
Template:Use American English (view source) (template editor protected)
Template:Use dmy dates (view source) (template editor protected)
Module:Arguments (view source) (protected)
Module:Authority control (view source) (template editor protected)
Module:Authority control/config (view source) (template editor protected)
Module:Category handler (view source) (protected)
Module:Category handler/blacklist (view source) (protected)
Module:Category handler/config (view source) (protected)
Module:Category handler/data (view source) (protected)
Module:Category handler/shared (view source) (protected)
Module:Check for unknown parameters (view source) (protected)
Module:Citation/CS1 (view source) (protected)
Module:Citation/CS1/COinS (view source) (protected)
Module:Citation/CS1/Configuration (view source) (protected)
Module:Citation/CS1/Date validation (view source) (protected)
Module:Citation/CS1/Identifiers (view source) (protected)
Module:Citation/CS1/Utilities (view source) (protected)
Module:Citation/CS1/Whitelist (view source) (protected)
Module:Citation/CS1/styles.css (view source) (protected)
Module:Disambiguation/templates (view source) (protected)
Module:Distinguish (view source) (template editor protected)
Module:Find sources (view source) (template editor protected)
Module:Find sources/config (view source) (template editor protected)
Module:Find sources/links (view source) (template editor protected)
Module:Find sources/templates/Find sources mainspace (view source) (template editor protected)
Module:Format link (view source) (template editor protected)
Module:Hatnote (view source) (template editor protected)
Module:Hatnote/styles.css (view source) (template editor protected)
Module:Hatnote list (view source) (template editor protected)
Module:List (view source) (protected)
Module:Message box (view source) (protected)
Module:Message box/ambox.css (view source) (protected)
Module:Message box/configuration (view source) (protected)
Module:Namespace detect/config (view source) (protected)
Module:Namespace detect/data (view source) (protected)
Module:Navbar (view source) (protected)
Module:Navbar/configuration (view source) (protected)
Module:Navbar/styles.css (view source) (protected)
Module:Navbox (view source) (template editor protected)
Module:Navbox/configuration (view source) (template editor protected)
Module:Navbox/styles.css (view source) (template editor protected)
Module:Ns has subpages (view source) (template editor protected)
Module:Pagetype (view source) (protected)
Module:Pagetype/config (view source) (protected)
Module:Pagetype/disambiguation (view source) (template editor protected)
Module:Pagetype/setindex (view source) (template editor protected)
Module:Pagetype/softredirect (view source) (template editor protected)
Module:Portal (view source) (template editor protected)
Module:Portal/images/m (view source) (template editor protected)
Module:Portal/styles.css (view source) (template editor protected)
Module:SDcat (view source) (template editor protected)
Module:String (view source) (protected)
Module:TableTools (view source) (protected)
Module:Unsubst (view source) (protected)
Module:Wikitext Parsing (view source) (template editor protected)
Module:Yesno (view source) (protected)

Return to Dermal patch.

Retrieved from "https://en.wikipedia.org/wiki/Dermal_patch"