How To Get The Release Certificate Fingerprint

If the public key in the certificate reply matches the user's public key already stored with under alias, the old certificate chain is replaced with the new certificate chain in the reply. The old chain can only be replaced if a validkeypass, the password used to protect the private key of the entry, is supplied. If no password is provided, and the private key password is different from the keystore password, the user is prompted for it. If the reply is a PKCS#7 formatted certificate chain or a sequence of X.509 certificates, the chain is ordered with the user certificate first followed by zero or more CA certificates. If the chain ends with a self-signed root CA certificate and-trustcacerts option was specified, keytoolwill attempt to match it with any of the trusted certificates in the keystore or the "cacerts" keystore file. If the certificate is not found and -noprompt option is not specified, the information of the last certificate in the chain is printed out, and the user is prompted to verify it.

Be very careful to ensure the certificate is valid prior to importing it as a "trusted" certificate! -- see WARNING Regarding Importing Trusted Certificates. The user then has the option of aborting the import operation. If the -noprompt option is given, however, there will be no interaction with the user. The default template in NativeScript provides you with a predefined splash_screen.xml file with the NativeScript logo on a blue background and with sample app icons.

To modify that template and create your own launch screen using your own assets and design, you will need to access the files located under the app/App_Resources/Android folder. Let's look at the various files and folders in App_Resources/Android and then look at the specific steps you'll need to take to change them and configure your launch screen. Subsequent keytool commands must use this same alias to refer to the entity. When running or debugging your project from the IDE, Android Studio automatically signs your app with a debug certificate generated by the Android SDK tools.

The first time you run or debug your project in Android Studio, the IDE automatically creates the debug keystore and certificate in $HOME/. The only reason it is stored in a certificate is because this is the format understood by most tools, so the certificate in this case is only used as a "vehicle" to transport the root CA's public key. The "cacerts" keystore file ships with several VeriSign root CA certificates, so you probably won't need to import a VeriSign certificate as a trusted certificate in your keystore.

But if you request a signed certificate from a different CA, and a certificate authenticating that CA's public key hasn't been added to "cacerts", you will need to import a certificate from the CA as a "trusted certificate". In this case, a keystore entry with alias "mykey" is created, with a newly-generated key pair and a certificate that is valid for 90 days. This entry is placed in the keystore named ".keystore" in your home directory. (The keystore is created if it doesn't already exist.) You will be prompted for the distinguished name information, the keystore password, and the private key password. Keypass is a password used to protect the private key of the generated key pair. If no password is provided, the user is prompted for it.

If you press RETURN at the prompt, the key password is set to the same password as that used for the keystore.keypass must be at least 6 characters long. By default the gradle task will not generate fingerprints for release build variant. In most places you will only find how to generated certificate fingerprints for debug build variant but if you published your app in Google Play Store then the live version will be a release build.

In this case you need to generate certificate fingerprints for release build variant too. Public and Private keys form cryptographically matched pairs. It is not feasible to derive one from the other, yet what one encrypts only the matching other can decrypt. Website SSL security certificates provide the site's Public cryptographic key which is the public side of the server's secret Private cryptographic key which is never publicly disclosed. Only the certificate's public key can be used to encrypt data which the remote server can decrypt only using its matching private key. And that means that no matter how hard any SSL-intercepting Proxy Appliance may try to spoof and fake any other server's certificate, the certificate's public key MUST BE DIFFERENT.

When keys are first generated (see the -genkeypair command), the chain starts off containing a single element, a self-signed certificate. A self-signed certificate is one for which the issuer is the same as the subject . Whenever the-genkeypair command is called to generate a new public/private key pair, it also wraps the public key into a self-signed certificate. View it first (using thekeytool -printcert command, or thekeytool -importcert command without the-noprompt option), and make sure that the displayed certificate fingerprint match the expected ones.

You can call the person who sent the certificate, and compare the fingerprint that you see with the ones that they show . Only if the fingerprints are equal is it guaranteed that the certificate has not been replaced in transit with somebody else's (for example, an attacker's) certificate. If such an attack took place, and you did not check the certificate before you imported it, you would end up trusting anything the attacker has signed.

During development, you can sign your application with the default android.keystore certificate that was generated automatically for you when you installed the SDK. In this example we're going to use this default keystore. To generate the key hashes using this keystore follow the examples below.

After created the release keystore and and signed the .APK. You can display the release certificate fingerprint. The certificate information is located in the debug.keystore file.

You can find the keystore file with the other Android environment configuration files for your application. By default, configuration files live in the ~/.android directory of your development environment. Follow this tutorial for creating SHA1 fingerprint keytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android ... Production certificates work similarly to development certificates.

The private key stays at your side and is never sent to Apple. Your app is signed with the distribution certificate using your private key, so Apple can verify the origin of submissions in iTunes Connect using the public key you sent them. You can use this command to import entries from a different type of keystore. During the import, all new entries in the destination keystore will have the same alias names and protection passwords . If keytool has difficulties recover the private keys or secret keys from the source keystore, it will prompt you for a password. If it detects alias duplication, it will ask you for a new one, you can specify a new alias or simply allowkeytool to overwrite the existing one.

When the srcalias option is provided, the command imports the single entry identified by the alias to the destination keystore. If a destination alias is not provided withdestalias, then srcalias is used as the destination alias. If the source entry is protected by a password,srckeypass will be used to recover the entry.

Ifsrckeypass is not provided, then keytool will attempt to use srcstorepass to recover the entry. Ifsrcstorepass is either not provided or is incorrect, the user will be prompted for a password. The destination entry will be protected using destkeypass. If destkeypass is not provided, the destination entry will be protected with the source entry password. To display release certificate fingerprint, you need to create the release keystore and and sign the .APK once.

Open a terminal and run thekeytoolthe utility provided with Java to get the SHA-1 fingerprint of the certificate. You should get both the release and debug certificate fingerprints. Open a terminal and run the keytool utility provided with Java to get the SHA-1 fingerprint of the certificate. In debug mode, you sign your app with a debug certificate.

This certificate has a private key with a known password. At the bottom of the chain is the certificate issued by the CA authenticating the subject's public key. The next certificate in the chain is one that authenticates the CA's public key.

There is a built-in default implementation, provided by Oracle. It implements the keystore as a file, utilizing a proprietary keystore type named "JKS". It protects each private key with its individual password, and also protects the integrity of the entire keystore with a password. Currently, two command-line tools and a GUI-based tool named Policy Toolmake use of keystore implementations.

Since KeyStoreis publicly available, users can write additional security applications that use it. This creates a "trusted certificate" entry in the keystore, with the data from the file "ABCCA.cer", and assigns the alias "abc" to the entry. Keyalg specifies the algorithm to be used to generate the secret key, and keysize specifies the size of the key to be generated. Keypass is a password used to protect the secret key. If you press RETURN at the prompt, the key password is set to the same password as that used for the keystore. You must take care in using the correct certificate fingerprint to create your Android credentials.

You will need the SHA1 fingerprint of your signing certificate here. This is the p12 certificate you use to sign your application. Keystore is basically a place where the private keys for your app are kept. In simple words its a certificate generated by the user or a program, used for signing an Android app. To view the entries in a cacerts file, you can use the keytool utility provided with Sun J2SDK versions 1.4 or later. The following example uses the -list command to display the CA certificates in the cacerts file.

Setting up launch screens depends on the version of iOS you are targeting. In iOS 7 and lower, the approach for creating the launch screen is to use static image resources. The drawback of this method is that the app developer will have to provide many different images, each with different resolution for each iOS device. In iOS 8 and above, the approach is to create a LaunchScreen.storyboard, which is much more powerful in terms of customization and is easier to maintain. The Internet standard RFC 5280 has defined a profile on conforming X.509 certificates, which includes what values and value combinations are valid for certificate fields and extensions. Keytool has not enforced all these rules so it can generate certificates which do not conform to the standard, and these certificates might be rejected by JRE or other applications.

Users should make sure that they provide the correct options for-dname, -ext, etc. Basically, public key cryptography requires access to users' public keys. In a large-scale networked environment it is impossible to guarantee that prior relationships between communicating entities have been established or that a trusted repository exists with all used public keys.

Certificates were invented as a solution to this public key distribution problem. Now a Certification Authority can act as a trusted third party. CAs are entities that are trusted to sign certificates for other entities.

It is assumed that CAs will only create valid and reliable certificates, as they are bound by legal agreements. There are many public Certification Authorities, such as VeriSign, Thawte, Entrust, and so on. You can also run your own Certification Authority using products such as Microsoft Certificate Server or the Entrust CA product for your organization. If you don't explicitly specify a keystore type, the tools choose a keystore implementation based simply on the value of thekeystore.type property specified in the security properties file. More specifically, the application interfaces supplied by KeyStore are implemented in terms of a "Service Provider Interface" . That is, there is a corresponding abstract KeystoreSpiclass, also in the java.security package, which defines the Service Provider Interface methods that "providers" must implement.

Trusted certificate entries - each contains a single public key certificate belonging to another party. It is called a "trusted certificate" because the keystore owner trusts that the public key in the certificate indeed belongs to the identity identified by the "subject" of the certificate. The issuer of the certificate vouches for this, by signing the certificate. If the -keypass option is not provided at the command line, and the key password is different from the keystore password, the user is prompted for it. If the srcalias option is not provided, then all entries in the source keystore are imported into the destination keystore. Each destination entry will be stored under the alias from the source entry.

If the source entry is protected by a password, srcstorepass will be used to recover the entry. If srcstorepass is either not provided or is incorrect, the user will be prompted for a password. The destination entry will be protected with the source entry password.

If you already generated signed build for your app then you can skip keystore file creating part and jump to Step 1 and start creating keystore properties. Android apps are cryptographically signed by the developer. One you use to upload your artifacts to Google Play and the app signing We are currently investigating support for key rotation using app signing v3 for devices.

Expogooglesignin provides native Google authentication for standalone Expo apps or bare reservedClientId to your reversed client ID. iOS & the googleservices.json Android from your Firebase project settings page. At this point you can build your project and upload it to the App Store or the Google Play Store. Now add this SHA1 key to the google developers console in credentials tab and also change the build variants in android studio to release mode. This app signing certificate (SHA-1 or SHA-256) is the fingerprint of the signing certificate that will be used for the app internal sharing.

Insert this value while signing or private signing on Appdome. To use Appdome's signing or private signing with an app meant to be re-signed on Google Play, you need to extract the SHA-1 or SHA-256 fingerprint from the app signing certificate from your Google Play account. Android SDK tools automatically generate a debug certificate and use the certificate to sign your Android package kit when you build your application locally for debugging and testing. The debug certificate includes your debug fingerprint .

If you want to build an Android APK binary that can be distributed on the Play Store, you need to use keytool to generate the SHA-1 fingerprint for your signing certificate. To enhance their users' security and privacy, an ever increasing number of web sites are switching from traditional "HTTP" to the more secure "HTTPS" connections—like THIS web page. This type of secured connection is known as SSL or TLS ("Secure Sockets Layer" and "Transport Layer Security") two names for the same thing. What's significant is that the data sent back and forth over any HTTPS/SSL/TLS connection is encrypted by technology no one knows how to break.

What Is Overfill Volume

The safety and efficacy of romiplostim have been evaluated for up to 3 years of continuous treatment. In clinical trials, treatment with romiplostim resulted in dose-dependent increases in platelet count. Time to reach the maximum effect on platelet count is approximately days, and is independent of the dose. After a single subcutaneous dose of 1 to 10 mcg/kg romiplostim in ITP patients, the peak platelet count was 1.3 to 14.9 times greater than the baseline platelet count over a 2 to 3 weeks period and the response was variable among patients. The platelet counts of ITP patients who received 6 weekly doses of 1 or 3 mcg/kg of romiplostim were within the range of 50 to 450 × 109/L for most patients. Of the 271 patients who received romiplostim in ITP clinical trials, 55 (20%) were age 65 and over, and 27 (10%) were 75 and over.

No overall differences in safety or efficacy have been observed between older and younger patients in the placebo-controlled studies. The preparation of medications for multiple doses (e.g., bulk preparation) ideally requires full sterile compounding of the product. Bags containing the manufacturer's base solution contain a variable amount of overfill, and specific concentrations of drugs can be prepared only by starting with an empty bag or other container.

Keep in mind that an error occurring early in the process (e.g., during medication reconstitution) may have an impact on the dose of medication received by multiple patients. Therefore, pharmacies that prepare IV medications intended for multiple doses should proactively evaluate their processes and take necessary precautions to mitigate identified risks. A significantly higher proportion of patients receiving romiplostim achieved a durable platelet response compared to patients receiving placebo in both studies. Following the first 4-weeks of study romiplostim maintained platelet counts ≥ 50 x 109/L in between 50% to 70% of patients during the 6 months treatment period in the placebo-controlled studies.

In the placebo group, 0% to 7% of patients were able achieve a platelet count response during the 6 months of treatment. Variables related to other processes with medication use can also affect the actual dose delivered to the patient. Further, nurses who recognize that overfill might be present in a pharmacy-prepared infusion bag or bottle have often misunderstood the "extra" solution as a pharmacy accommodation for the amount of drug lost in the tubing. Thus, the 20–25 mL of solution in pump tubing sets, which may account for a significant portion of the total dose, will not be received because the bag would not be completely infused. Variables related to other processes with medication use can also affect the actual dose delivered to the patient . Thus, the 20 to 25 mL of solution in pump tubing sets, which may account for a significant portion of the total dose, will not be received because the bag would not be completely infused.

A group purchasing organization contracted with a new compounding pharmacy to provide cyclophosphamide and gemcitabine solutions to hospitals. These drugs were used as part of regimens to treat various solid tumor malignancies, lymphoma, and leukemia in adults and children. A discrepancy in labeling on a gemcitabine preparation between the previous supplier and the new supplier led a hospital pharmacist to ask the compounding pharmacy for clarification. It then became apparent that there was a misunderstanding about how the compounded solutions were being used by the hospitals.

The new compounding pharmacy thought that each full bag of gemcitabine and cyclophosphamide contained a single dose to be administered to a single patient. However, the hospitals were using each bag as a multidose product, apportioning the medication from a single bag among several patients. Believing each bag was a single dose, the compounding pharmacy did not account for the volume of overfill in the bag when labeling the concentration of the prepared product. Although the full dose in each bag was listed on the label, the actual concentration of the drug in each bag was lower than stated due to overfill in the normal saline bags used to dilute the medication. The best estimate is that the average actual cyclophosphamide concentration was 10% lower than stated on the label, and the average actual gemcitabine concentration was 7% lower than stated on the label.

A group purchasing organization had recently contracted with a new compounding pharmacy to provide cyclophosphamide and gemcitabine solutions to hospitals. These drugs were used as part of regimens to treat various solid tumor malignancies, lymphoma, and leukemia in both adults and children. The new compounding pharmacy thought each full bag of gemcitabine and cyclophosphamide contained a single dose to be administered to a single patient.

While the full dose in each bag was listed on the label, the actual concentration of the drug in each bag was lower than stated due to overfill in the normal saline bags used to dilute the medication. Study S8 was a phase 3, long-term, single-arm, open-label, multicentre study conducted in 203 paediatric patients with ITP diagnosed for at least 6 months and who received at least 1 prior ITP therapy or were ineligible for other ITP therapies. Romiplostim was administered weekly by subcutaneous injection starting at a dose of 1 mcg/kg with weekly increments to a maximum dose of 10 mcg/kg to reach a target platelet count between 50 x 109/L and 200 x 109/L. The median age of the patients was 10 years and the median duration of treatment were 155.9 (range, 8.0 to 163.0) weeks.

With the first 3 practitioner-based methods, the total dose of the medication is known, but the concentration cannot be calculated accurately because the volume of overfill of the base solution is not exactly known but can only be estimated. The final container should not be labeled with a specific concentration per mL because of the unknowns. The pharmacist may or may not add more drug to offset the overfill volume. These bags should only be labeled with the total amount of drug in the container and the total estimated volume. Only with method 4 can the concentration be accurately calculated and added to the pharmacy label.

The prescribed medication is added to a manufacturer's base solution container, such as 0.9% sodium chloride, in an intravenous bag without concern for overfill. This is typically used for the admixture of intermittently administered solutions when the entire bag is intended to be infused to a single patient over a short time (e.g., 30 minutes). This is typically used for the admixture of intermittently administered solutions when the entire bag is intended to be infused to a single patient over a short time . This method may also be used to prepare medications administered via continuous infusion when the slight difference in per mL concentration may not be as important because the effect of the medication is being continuously monitored .

How To Calculate Overfill Volume Thus, the mL of solution in pump tubing sets, which may account for a significant portion of the total dose, will not be received because the bag would not be completely infused. The prescribed medication is added to a manufacturer's base solution container, such as 0.9% sodium chloride, in an IV bag without concern for overfill. During preparation of infusions, the 10% rule is used by some hospitals to determine whether fluid should be removed from the bulk solution container prior to the addition of the medication. The rule suggests that if the volume of the additive medication is more than 10% of the volume listed on the bulk solution container , the volume of the additive, and sometimes the volume of the overfill, will be removed.

Unless starting with an empty bag , the 10% rule is often applied to all admixtures except small-volume intermittent solutions such as antibiotics or other products with manufacturer-specified preparation procedures. Whatever method is chosen, it is critical to be consistent within your organization. The 10% rule is used by some hospitals during the preparation of infusions to determine whether fluid should be removed from the bulk solution container prior to the addition of the medication.

Unless starting with an empty bag , the 10% rule is often applied to all admixtures, except small volume intermittent solutions such as antibiotics or other products with manufacturer-specified preparation procedures. Unless starting with an empty bag , the 10% rule is often applied to all admixtures except small volume intermittent solutions such as antibiotics or other products with manufacturer-specified preparation procedures. Premix IVs offer distinct advantages over manual admixtures, including increased sterility assurance, quality control, bar code safety, extended shelf life, and can provide optimal bag sizes. After performing a comprehensive pharmacoeconomic analysis, an institution can realize the financial, objective, and subjective benefits of adding the premix product to the institution's formulary. Sterile manual admixture of IV infusions exists within pharmacy as conventionally manufactured products are not available for all medications.

The mean and median percentage of time with a platelet response (platelet count ≥ 50 x 109/L) within the first 6 months of initiation of romiplostim without rescue medication use for the past 4 weeks was 50.57% (37.01) and 50.0%, respectively. Rescue medications (i.e., corticosteroids, platelet transfusions, IVIG, azathioprine, anti-D immunoglobulin, and danazol) were permitted. B Overall platelet response is defined as achieving durable or transient platelet responses.

Transient platelet response was defined as weekly platelet count ≥ 50 x 109/L for 4 or more times during study weeks 2-25 but without durable platelet response. Patient may not have a weekly response within 8 weeks after receiving any rescue medicinal products. Based on an analysis of all adult ITP patients receiving romiplostim in 4 controlled and 5 uncontrolled clinical trials, the overall subject incidence of all adverse reactions for romiplostim-treated subjects was 91.5% (248/271). The mean duration of exposure to romiplostim in this study population was 50 weeks. In adult clinical studies of treatment with romiplostim in patients with MDS, cases of transient increases in blast cell counts were observed and cases of MDS disease progression to AML were reported. Of the cases of MDS disease progression to AML that were observed, patients with RAEB-1 classification of MDS at baseline were more likely to have disease progression to AML compared to lower risk MDS.

Health care organizations must develop standardized preparation methods appropriate for various clinical situations. When doing this, it is important to balance the benefits of process changes against additional risks that such changes may present. In particular, changes that increase the manipulation of products or the complexity of processes can pose new risks that outweigh the benefit of added dosing accuracy. There is no single, standard method appropriate for all infusions in all hospitals, particularly given the variability in environmental conditions, staff expertise, and technology among hospitals. However, consider the following points when designing processes in your hospital for admixture and sterile compounding. Health care organizations must develop standardized preparation methods that are appropriate for various clinical situations.

Healthcare organizations must develop standardized preparation methods appropriate for various clinical situations. Twenty-one non-splenectomised and 18 splenectomised patients received on-study ITP medical treatments at the start of study. All (100%) splenectomised patients who were receiving romiplostim were able to reduce the dose by more than 25% or discontinue the concurrent ITP medical therapies by the end of the treatment period compared to 17% of placebo treated patients. C Number of weeks with platelet response is defined as number of weeks with platelet counts ≥ 50 x 109/L during study weeks 2-25. A subject's actual body weight at initiation of therapy should be used to calculate dose.

The once weekly dose of romiplostim should be increased by increments of 1 mcg/kg until the patient achieves a platelet count ≥ 50 x 109/L. Platelet counts should be assessed weekly until a stable platelet count (≥ 50 x 109/L for at least 4 weeks without dose adjustment) has been achieved. Platelet counts should be assessed monthly thereafter and appropriate dose adjustments made as per the dose adjustment table in order to maintain platelet counts within the recommended range. In practice, there are several different practitioner- and manufacturer-based preparation methods.

The preparation method used affects the total volume and concentration of the final product. In practice, there are several different practitioner-based and manufacturer-based preparation methods. This guidance clarifies FDA requirements and regulations pertaining to allowable excess volume in injectable vials and reinforces the importance of appropriate fill volumes and labeled vial fill sizes for injectable drug and biological products. Initial reconstitution of romiplostim with designated volumes of sterile water for injections results in a concentration of 500 mcg/mL in all vial sizes. If the calculated individual patient dose is less than 23 mcg (see section 4.2), an additional dilution step to 125 mcg/mL with preservative-free, sterile, sodium chloride 9 mg/mL (0.9%) solution for injection is required to ensure accurate volume .

Usually, there is a slight overfilling in small volume injectable drug products, especially for biological active ingredients, in order to guarantee the excess volume. In its actual FDA Guidance for Industry "Allowable Excess Volume and Labelled Vial Fill Size in Injectable Drug and Biological Products" finalised for 24 June 2015 the FDA clarifies its point of view and the corresponding requirements. The guidance for industry only refers to drugs in ampules or vials that are intended for injection. A volume of the base solution equal to the volume of the medication to be added to the container is withdrawn from the manufacturer's container, without concern about overfill. The medication is then added to the remaining volume in the container. This method is typically used when the volume of medication to be added is large relative to the size of the base solution container.

For example, before adding 150 mL of sodium bicarbonate from a syringe or vial to a 1,000-mL bag of dextrose 5%, a volume of 150 mL of the base solution is withdrawn from the bag and discarded. A medication for parenteral use is manufactured in large quantities to a specific concentration (eg, mg/mL). The required volume of this solution, in addition to the overfill containing the medication at the same concentration, is added to an empty parenteral container. This method is used for commonly manufactured premixed solutions approved by the US Food and Drug Administration . With this method, the medication concentration in the container at the time of manufacture is the same as the concentration on the label. However, the final product contains more volume than the label indicates due to overfill.

For example, an IV bag of gentamicin labeled as containing 80 mg/100 mL contains the labeled 80 mg and another 4 mg of the drug in the 5 mL of overfill. For example, before adding 150 mL of sodium bicarbonate from a syringe or vial to a 1,000 mL bag of dextrose 5%, a volume of 150 mL of the base solution is withdrawn from the bag and discarded. This guidance is being issued consistent with FDA's good guidance practices regulation (21 CFR 10.115). The guidance represents the current thinking of FDA on allowable excess fill volume and labeled vial fill size for injectable drug and biological products packaged in vials and ampules. It does not establish any rights for any person and is not binding on FDA or the public. You can use an alternative approach if it satisfies the requirements of the applicable statutes and regulations.

Pharmacokinetic data of romiplostim were collected from two studies in 21 paediatric subjects with ITP. In study S6 , romiplostim concentrations were available from 17 subjects at doses ranging from 1 to 10 mcg/kg. In Study S7 , intensive romiplostim concentrations were available from 4 subjects (2 at 7 mcg/kg and 2 at 9 mcg/kg). Serum concentrations of romiplostim in paediatrics with ITP were within the range observed in adult ITP subjects receiving the same dose range of romiplostim. Similar to adults with ITP, romiplostim pharmacokinetics are highly variable in paediatric subjects with ITP and are not reliable and predictive.

However, the data are insufficient to draw any meaningful conclusion relating to the impact of dose and age on the pharmacokinetics of romiplostim. D Rescue therapies defined as any therapy administered to raise platelet counts. Patients requiring rescue medicinal products were not considered for durable platelet response. Rescue therapies allowed in the study were IVIG, platelet transfusions, anti-D immunoglobulin, and corticosteroids.

In paediatric studies, the incidence of binding antibodies to romiplostim at any time was 9.6% (27/282). Of the 27 subjects, 2 subjects had pre-existing binding non-neutralising romiplostim antibodies at baseline. Additionally, 2.8% (8/282) developed neutralising antibodies to romiplostim.

A total of 3.9% (11/282) subjects had binding antibodies to TPO at any time during romiplostim treatment. Of these 11 subjects, 2 subjects had pre-existing binding non-neutralising antibodies to TPO. One subject (0.35%) had a weakly positive postbaseline result for neutralising antibodies against TPO while on study (consistently negative for anti-romiplostim antibodies) with a negative result at baseline. The subject showed a transient antibody response for neutralising antibodies against TPO, with a negative result at the subject's last timepoint tested within the study period. After reconstitution of the powder, Nplate solution for injection is administered subcutaneously. Caution should be used during preparation of Nplate in calculating the dose and reconstitution with the correct volume of sterile water for injection.

If the calculated individual patient dose is less than 23 mcg, dilution with preservative-free, sterile, sodium chloride 9 mg/mL (0.9%) solution for injection is required to ensure accurate dosing (see section 6.6). Special care should be taken to ensure that the appropriate volume of Nplate is withdrawn from the vial for subcutaneous administration – a syringe with graduations of 0.01 mL should be used. A volume of the base solution equal to the sum of the volume of the medication to be added to the container and the estimated volume of overfill is withdrawn from the manufacturer's container. Choose the most appropriate method of preparing each medication infusion according to whether or not the volume is critical.

Start by developing a list to identify medications and situations for which added accuracy in dose or concentration is needed and the level of accuracy required. This list will help determine which preparation method should be used for specific drugs. Also, obtain a list of overfill amounts of commonly used products from vendors for reference as necessary. Although a commercially available bag or bottle of parenteral solution may be labeled to contain 25, 50, 100, 250, 500, or 1,000 mL, the actual volume is larger because it contains overfill. The containers may be permeable to oxygen and experience a loss of water to some extent, depending on the storage conditions, specific contents, permeability of the container, and ratio of fluid volume to the container surface area. Thus, there is some variability in the targeted amount of overfill specified by each manufacturer in each bag, as well as variability in the contents of any bag at any point in time.

Despite this variability, vendors of solutions can provide customers with a targeted amount and range of overfill in each of their products. Nplate 500 micrograms powder for solution for injection should be reconstituted with 1.2 mL sterile water for injections, yielding a deliverable volume of 1 mL. An additional overfill is included in each vial to ensure that 500 mcg of romiplostim can be delivered .

Nplate 250 micrograms powder for solution for injection should be reconstituted with 0.72 mL sterile water for injections, yielding a deliverable volume of 0.5 mL. An additional overfill is included in each vial to ensure that 250 mcg of romiplostim can be delivered . Nplate 125 micrograms powder for solution for injection should be reconstituted with 0.44 mL sterile water for injections, yielding a deliverable volume of 0.25 mL. An additional overfill is included in each vial to ensure that 125 mcg of romiplostim can be delivered .